Skip to content

MCP servers › io.usefulapi › courtreserve

MCP server · registry snapshot 2026-11-03 · last tested 2026-11-03

io.usefulapi/courtreserve

CourtReserve MCP by usefulapi — the publisher's title

by usefulapi.io · domain (the registry's namespace rule)repository owner on GitHub: m190 (personal account)Source ↗Website ↗

Read club members, court availability, reservations, events, attendance and revenue reports. — the publisher's description

4 of 5 record checks metRead-only · tools listed 2026-11-03version 1.8.0JavaScriptstreamable HTTP23 tools

Summary

io.usefulapi/courtreserve is a remote MCP server listed in the official MCP registry at version 1.8.0, under the namespace of the domain usefulapi.io. Its linked repository is github.com/m190/usefulapi-mcp; GitHub reports its owner as m190, a personal account. On 2026-11-03 ProtocolProbe connected to it in read-only mode and read its inventory: 23 tools, 0 resources and 4 prompts.

Record checks

4 of 5 record checks met · 4 do not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not met: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 1 star (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Repository
public
Tools
23
Last tested
2026-11-03

Tool list size

10,073 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (23 tools). Counted with Anthropic's token counter on 2026-11-03, from the tool list we read on 2026-11-03. Median across 25,738 counted servers: 2,858 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-03 (courtreserve.usefulapi.io), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.8.0).

Add to your client

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-03
Mode
read-only (no tool calls)
Latest version
1.8.0, published 2026-11-03 (registry, as of the 2026-11-03 snapshot)
First listed version
2026-10-28 (earliest version still in the registry; older removed versions would be earlier)
Version history
12 versions listed, 2026-10-28 to 2026-11-03; 12 in the 90 days before the 2026-11-03 snapshot.
Most recent 12 versions
  • 1.8.0 · 2026-11-03
  • 1.7.1 · 2026-11-03
  • 1.7.0 · 2026-11-02
  • 1.6.0 · 2026-10-31
  • 1.5.0 · 2026-10-31
  • 1.4.0 · 2026-10-31
  • 1.3.0 · 2026-10-31
  • 1.2.2 · 2026-10-30
  • 1.2.1 · 2026-10-30
  • 1.2.0 · 2026-10-29
  • 1.1.0 · 2026-10-29
  • 1.0.0 · 2026-10-28
(versions still listed in the registry only)
Registry data
snapshot 2026-11-03
Package and repository
checked 2026-11-03
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 1.7.0 (published 2026-11-02) → 1.8.0 (published 2026-11-03), between the registry lists of 2026-11-02 and 2026-11-03.

The publisher published no GitHub release note for this version: its repository publishes no GitHub releases.

Source: the official MCP Registry list on 2026-11-02 and on 2026-11-03; release notes from the GitHub Releases API, checked 2026-11-03.

What it is

What does this server offer?

Observed inventory
23tools
0resources
4prompts

None of its 23 tools are described as changing anything. For 23 the reading was uncertain, so no mark is shown.

  • courtreserve_list_members

    “List the club's members (name, email, phone, membership type and status, start/end/next payment dates, family id).”

    Publisher declares: read-only yes · destructive no · open-world yes

    13 inputs
    • organization_member_idinteger“Only this member id.”
    • family_idinteger“Only the members of this family (organizationMemberFamilyId).”
    • emailstring“Exact email address (no partial matches).”
    • phone_numberstring“Phone number.”
    • created_fromstring“Only members created at or after this club-local date-time (with created_to: at most 30 days apart).”
    • created_tostring“Only members created at or before this club-local date-time.”
    • created_or_updated_fromstring“Only members created or changed at or after this club-local date-time (with the end: at most 31 days apart).”
    • created_or_updated_tostring“Only members created or changed at or before this club-local date-time.”
    • include_custom_fieldsboolean“Add the club's user-defined fields.”
    • include_ratingsboolean“Add skill ratings (DUPR, UTR and so on).”
    • include_marketing_consentboolean“Add current email/text opt-in and the consent history.”
    • pageinteger“Page number, from 1 (default 1).”
    • page_sizeinteger“Members per page, 1-200 (default 50).”
  • courtreserve_get_member_reservations

    “A member's upcoming (or dated) court bookings and event registrations: type, start/end, courts, event name and players.”

    Publisher declares: read-only yes · destructive no · open-world yes

    5 inputs
    • organization_member_idinteger“CourtReserve member id (courtreserve_list_members).”
    • external_idstring“The member's id in your own system (the member's External Id).”
    • start_datestring“Only reservations ending on or after this club-local date/time (default: now).”
    • end_datestring“Only reservations ending on or before this club-local date/time (default: open-ended).”
    • limitinteger“Most rows to return (default 100, max 500).”
  • courtreserve_list_families

    “List family accounts (family id, name, number, members and membership).”

    Publisher declares: read-only yes · destructive no · open-world yes

    2 inputs
    • family_idinteger“Only this family (organizationMemberFamilyId).”
    • limitinteger“Most rows to return (default 100, max 500).”
  • courtreserve_list_membership_types

    “The club's membership types (id, name, price, billing and status).”

    Publisher declares: read-only yes · destructive no · open-world yes

    2 inputs
    • membership_type_idinteger“Only this membership type id.”
    • limitinteger“Most rows to return (default 100, max 500).”
  • courtreserve_membership_report

    “The Membership report: one row per member or family membership with status, billing cadence, start/end, next payment and cancellation history.”

    Publisher declares: read-only yes · destructive no · open-world yes

    12 inputs
    • assignment_typestring“Only family or only individual memberships (default both).”
    • membership_type_idsarray“Only these membership type ids (courtreserve_list_membership_types).”
    • start_fromstring“Membership started on or after.”
    • start_tostring“Membership started on or before.”
    • end_fromstring“Membership ends on or after.”
    • end_tostring“Membership ends on or before.”
    • next_payment_fromstring“Next payment on or after.”
    • next_payment_tostring“Next payment on or before.”
    • canceled_fromstring“Canceled on or after.”
    • canceled_tostring“Canceled on or before.”
    • pageinteger“Page number, from 1 (default 1).”
    • page_sizeinteger“Rows per page, 1-500 (default 100).”
  • courtreserve_list_courts

    “The club's courts: id, label, court type and order.”

    Publisher declares: read-only yes · destructive no · open-world yes

    1 input
    • limitinteger“Most rows to return (default 100, max 500).”
  • courtreserve_list_reservation_types

    “The club's reservation types (court booking, lesson, court block and so on) with ids.”

    Publisher declares: read-only yes · destructive no · open-world yes

    1 input
    • limitinteger“Most rows to return (default 100, max 500).”
  • courtreserve_get_court_availability

    “Court availability: each court's operating hours and the time slots already booked, for one date or a date range of at most 31 days (time zone of the club in the reply).”

    Publisher declares: read-only yes · destructive no · open-world yes

    4 inputs
    • datestring“One date, yyyy-MM-dd.”
    • from_datestring“First date of a range, yyyy-MM-dd.”
    • to_datestring“Last date of the range, yyyy-MM-dd (at most 31 days after from_date).”
    • court_type_idinteger“Only courts of this type (see the court type in courtreserve_list_courts).”
  • courtreserve_list_reservations

    “Active court reservations for a reservation period (the dates played) or a created/updated period, at most 31 days each: type, courts, start/end, players with contact details and what they owe/paid.”

    Publisher declares: read-only yes · destructive no · open-world yes

    7 inputs
    • reservations_fromstring“Reservations starting on or after.”
    • reservations_tostring“Reservations starting on or before.”
    • created_or_updated_fromstring“Reservations created or changed on or after.”
    • created_or_updated_tostring“Reservations created or changed on or before.”
    • include_custom_fieldsboolean“Add user-defined fields.”
    • include_ratingsboolean“Add player ratings.”
    • limitinteger“Most rows to return (default 100, max 500).”
  • courtreserve_list_cancelled_reservations

    “Cancelled court reservations by the date they were cancelled or by the reservation period, at most 31 days each.”

    Publisher declares: read-only yes · destructive no · open-world yes

    5 inputs
    • cancelled_fromstring“Cancelled on or after.”
    • cancelled_tostring“Cancelled on or before.”
    • reservations_fromstring“Reservations starting on or after.”
    • reservations_tostring“Reservations starting on or before.”
    • limitinteger“Most rows to return (default 100, max 500).”
  • courtreserve_whos_here

    “Who is booked in a time window (for example today): member reservations and event registrations with the member, court and time, optionally including or only cancelled ones.”

    Publisher declares: read-only yes · destructive no · open-world yes

    5 inputs, 2 required
    • startstringrequired“Start of the window, club-local yyyy-MM-ddTHH:mm:ss.”
    • endstringrequired“End of the window, club-local yyyy-MM-ddTHH:mm:ss.”
    • include_cancelledboolean“Also return cancelled reservations.”
    • cancelled_onlyboolean“Only cancelled reservations (wins over include_cancelled).”
    • limitinteger“Most rows to return (default 100, max 500).”
  • courtreserve_court_utilization

    “Court utilization report (booked vs available time per time slot) for a period of at most 7 days, optionally for chosen courts, court types, event types, event tags or reservation types.”

    Publisher declares: read-only yes · destructive no · open-world yes

    7 inputs, 2 required
    • start_datestringrequired“First day of the period.”
    • end_datestringrequired“Last day of the period (at most 7 days after the first).”
    • court_idsarray“Only these court ids (courtreserve_list_courts).”
    • court_type_idsarray“Only these court type ids.”
    • event_tag_idsarray“Only these event tag ids.”
    • event_type_idsarray“Only these event category ids (courtreserve_list_event_categories).”
    • reservation_type_idsarray“Only these reservation type ids (courtreserve_list_reservation_types).”
Show 11 more tools
  • courtreserve_list_event_categories

    “Event categories (clinics, round robins, tournaments, open play...) with ids.”

    Publisher declares: read-only yes · destructive no · open-world yes

    3 inputs
    • category_idinteger“Only this category id.”
    • is_publicboolean“Only public (true) or only non-public (false) categories; omit for all.”
    • limitinteger“Most rows to return (default 100, max 500).”
  • courtreserve_list_events

    “Events on the club calendar between two dates: name, category, start/end, courts, instructors, capacity, registered and waitlist counts, price and rating limits.”

    Publisher declares: read-only yes · destructive no · open-world yes

    8 inputs
    • start_datestring“Events from this club-local date/time.”
    • end_datestring“Events up to this club-local date/time.”
    • category_idinteger“Only this event category (courtreserve_list_event_categories).”
    • statusstring“Event status (default Active).”
    • include_price_infoboolean“Add prices (default true).”
    • include_rating_restrictionsboolean“Add rating restrictions.”
    • include_tagsboolean“Add event tags.”
    • limitinteger“Most rows to return (default 100, max 500).”
  • courtreserve_list_event_registrations

    “Active registrations for events, clinics and lessons with the member, event and what was paid.”

    Publisher declares: read-only yes · destructive no · open-world yes

    7 inputs
    • event_fromstring“Events on or after.”
    • event_tostring“Events on or before.”
    • registered_fromstring“Registered on or after.”
    • registered_tostring“Registered on or before.”
    • include_courtsboolean“Add court information.”
    • include_partner_infoboolean“Add partner(s) for team events.”
    • limitinteger“Most rows to return (default 100, max 500).”
  • courtreserve_list_event_waitlist

    “People on event waitlists.”

    Publisher declares: read-only yes · destructive no · open-world yes

    7 inputs
    • event_fromstring“Events on or after.”
    • event_tostring“Events on or before.”
    • registered_fromstring“Registered on or after.”
    • registered_tostring“Registered on or before.”
    • include_courtsboolean“Add court information.”
    • include_partner_infoboolean“Add partner(s) for team events.”
    • limitinteger“Most rows to return (default 100, max 500).”
  • courtreserve_list_cancelled_event_registrations

    “Cancelled event registrations by cancellation date or by event date, at most 31 days each.”

    Publisher declares: read-only yes · destructive no · open-world yes

    5 inputs
    • cancelled_fromstring“Cancelled on or after.”
    • cancelled_tostring“Cancelled on or before.”
    • event_fromstring“Events on or after.”
    • event_tostring“Events on or before.”
    • limitinteger“Most rows to return (default 100, max 500).”
  • courtreserve_list_checkins

    “Check-in report: who checked in to court bookings and events, by check-in period or reservation period (at most 31 days each).”

    Publisher declares: read-only yes · destructive no · open-world yes

    7 inputs
    • checkin_fromstring“Checked in on or after.”
    • checkin_tostring“Checked in on or before.”
    • reservations_fromstring“Reservations starting on or after.”
    • reservations_tostring“Reservations starting on or before.”
    • include_court_bookingboolean“Include court bookings (default true).”
    • include_eventsboolean“Include events (default true).”
    • limitinteger“Most rows to return (default 100, max 500).”
  • courtreserve_list_transactions

    “Transactions (fees, membership fees, payments, refunds...) by transaction date or reservation date: id, type, date, subtotal, tax, total, unpaid amount, payment type, category and the member's name, …”

    Publisher declares: read-only yes · destructive no · open-world yes

    10 inputs
    • transaction_fromstring“Transactions on or after.”
    • transaction_tostring“Transactions on or before.”
    • reservation_fromstring“Reservations starting on or after.”
    • reservation_tostring“Reservations starting on or before.”
    • transaction_typesstring“Comma-separated transaction types, for example 'Fee,Membership Fee,Payment' (the vendor's own names).”
    • payment_typesstring“Comma-separated payment types, for example 'Cash,Credit Card,Balance'.”
    • only_paidboolean“Only paid transactions.”
    • only_unpaidboolean“Only unpaid transactions.”
    • include_promo_infoboolean“Add the promo codes each fee used.”
    • limitinteger“Most rows to return (default 100, max 500).”
  • courtreserve_sales_summary

    “Detailed sales summary for a payment period of at most 31 days: paid fees plus refunds by category and payment type.”

    Publisher declares: read-only yes · destructive no · open-world yes

    3 inputs, 2 required
    • payment_fromstringrequired“First day of the payment period.”
    • payment_tostringrequired“Last day of the payment period (at most 31 days after the first).”
    • include_promo_infoboolean“Add the promo codes each fee used.”
  • courtreserve_list_promo_codes

    “The club's promo codes: code, name, type, value, dates, limits and what they apply to.”

    Publisher declares: read-only yes · destructive no · open-world yes

    2 inputs
    • promo_code_idinteger“Only this promo code id.”
    • limitinteger“Most rows to return (default 100, max 500).”
  • courtreserve_list_leagues

    “The club's leagues, with their sessions (id and name) when include_sessions is true (default).”

    Publisher declares: read-only yes · destructive no · open-world yes

    4 inputs
    • league_idinteger“Only this league id.”
    • include_sessionsboolean“Add each league's sessions (default true).”
    • pageinteger“Page number, from 1 (default 1).”
    • page_sizeinteger“Leagues per page, 1-200 (default 100).”
  • courtreserve_list_league_sessions

    “League sessions, for one league or one session, optionally with their game days and registered players.”

    Publisher declares: read-only yes · destructive no · open-world yes

    6 inputs
    • league_idinteger“Only this league's sessions.”
    • session_idinteger“Only this session.”
    • include_game_daysboolean“Add each session's game days.”
    • include_playersboolean“Add each session's registered players (use with one session).”
    • pageinteger“Page number, from 1 (default 1).”
    • page_sizeinteger“Sessions per page, 1-200 (default 100).”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-03.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
100% of 126
Tools with a description
100% of 23
Typical description length
232 characters

The tool set

Counted from the listing

Tools
23
Size of the list
about 6,811 tokens for an agent to load (characters ÷ 4)
Naming
23 of 23 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 23 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-03 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://courtreserve.usefulapi.io/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "courtreserve": {
      "url": "https://courtreserve.usefulapi.io/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "courtreserve": {
      "type": "http",
      "url": "https://courtreserve.usefulapi.io/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"courtreserve","type":"http","url":"https://courtreserve.usefulapi.io/mcp"}'
Claude Code
claude mcp add --transport http courtreserve https://courtreserve.usefulapi.io/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "courtreserve": {
      "type": "streamableHttp",
      "url": "https://courtreserve.usefulapi.io/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "courtreserve": {
      "httpUrl": "https://courtreserve.usefulapi.io/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.courtreserve]
url = "https://courtreserve.usefulapi.io/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "courtreserve": {
      "url": "https://courtreserve.usefulapi.io/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://courtreserve.usefulapi.io/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint courtreserve.usefulapi.io/mcpSession openedmatchesour test · 2026-11-03
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-03
Repository github.com/m190/usefulapi-mcpOpens publiclymatchesapi.github.com · 2026-11-03

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.usefulapi · 748 servers
GitHub owner
a personal account (m190)
Repository
github.com/m190/usefulapi-mcp
Stars
1
Repository age
91–180 days
Last push
0–30 days ago
Archived
no
Security policy
none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-11-03; security policy read from GitHub · 2026-11-01.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Tool list changes

Our reads compared · no tool called

Hosted endpoint courtreserve.usefulapi.io/mcp

No change in the tool list across 6 reads (2026-10-29 to 2026-11-03; versions 1.0.0 to 1.8.0).

Compared from the tool lists our read-only connection recorded, separately for each hosted endpoint and each package: each tool's name, title, description, input schema and annotations (the order of keys and of tools is ignored). We see a list only when we read it: a change is shown between the two reads where we first saw it, and anything after 2026-11-03 is not known yet. No tool was called. How it is compared

Choosing

Record checks

Public records · not a safety rating

4 of 5 record checks met · 4 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 1 star (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-03 (security policy 2026-11-01). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about io.usefulapi/courtreserve

Answered from the data above

Who publishes io.usefulapi/courtreserve?

The registry ties the namespace io.usefulapi to the domain usefulapi.io; only its owner can publish under it. Its linked repository is github.com/m190/usefulapi-mcp; GitHub reports its owner as m190, a personal account. These are facts from the registry and GitHub, not a rating.

Is io.usefulapi/courtreserve safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does io.usefulapi/courtreserve need an API key or sign-in?

It opened a session without any credential on 2026-11-03. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.usefulapi/courtreserve been security tested?

Partly. 3 of the 16 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. ProtocolProbe publishes no security verdict for a named server.

Does io.usefulapi/courtreserve publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of io.usefulapi/courtreserve?

In github.com/m190/usefulapi-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (we call no server's tools)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-03
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: not run · nothing to check it against
  13. Fake assistant turns: not run · an error was returned
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: exercised

3 exercised13 not run (reason given)2 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 3
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 13
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server returned an error when its prompts were read.not run · an error was returned
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 2
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-11-03, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 298 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 23 tools, 0 resources, 4 prompts.
  4. 1,759 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added in the weekly update
listed 2026-11-03; not classified yet
Pricing modelAI-classified
pending: added in the weekly update
the website is not read yet
Programming language
api.github.com · 2026-11-03
Hosting type
registry · 2026-11-03
MCP capability
prompts, tools
our test · 2026-11-03
Transport
streamable HTTP
registry · 2026-11-03
Required credentials
none declared
registry · 2026-11-03 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-03
Lifecycle status
registry · 2026-11-03
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
owner: a personal account · repository age: 91–180 days · stars: 0–9
api.github.com · 2026-11-03
Maintenance
api.github.com · 2026-11-03
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-03

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.usefulapi/courtreserve: MCP server record.” Data checked 2026-11-03. https://protocolprobe.com/mcp/servers/io.usefulapi/courtreserve

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 4 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.usefulapi/courtreserve)](https://protocolprobe.com/mcp/servers/io.usefulapi/courtreserve)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology