tennis.courts/nyc-tennis-courts
REMOTE · WWW.COURTS.TENNIS · SCANNED SEP 20
Every place to play tennis in New York City: which you walk on to, which take a booking.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 456 tokens (~152/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the tennis.courts/nyc-tennis-courts MCP server?
tennis.courts/nyc-tennis-courts is a hosted endpoint at https://www.courts.tennis/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.courts.tennis
claude mcp add --transport http tennis-courts-nyc-tennis-courts 'https://www.courts.tennis/mcp'
{
"mcpServers": {
"tennis-courts-nyc-tennis-courts": {
"url": "https://www.courts.tennis/mcp"
}
}
} {
"servers": {
"tennis-courts-nyc-tennis-courts": {
"type": "http",
"url": "https://www.courts.tennis/mcp"
}
}
} [mcp_servers.tennis-courts-nyc-tennis-courts] url = "https://www.courts.tennis/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tennis-courts-nyc-tennis-courts": {
"type": "remote",
"url": "https://www.courts.tennis/mcp",
"enabled": true
}
}
} openclaw mcp add tennis-courts-nyc-tennis-courts --url 'https://www.courts.tennis/mcp' --transport streamable-http
mcp_servers:
tennis-courts-nyc-tennis-courts:
url: "https://www.courts.tennis/mcp" {
"McpServers": {
"tennis-courts-nyc-tennis-courts": {
"Transport": "http",
"Url": "https://www.courts.tennis/mcp"
}
}
} assistant mcp add tennis-courts-nyc-tennis-courts -t streamable-http -u 'https://www.courts.tennis/mcp'
{
"mcpServers": {
"tennis-courts-nyc-tennis-courts": {
"type": "http",
"url": "https://www.courts.tennis/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 0
- Stability: 0.97 → pass security
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://www.courts.tennis/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.courts.tennis | CN=YR1,O=Let's Encrypt,C=US | 23 Jul 2026 | 21 Oct 2026 | RSA 2048 | SHA256-RSA | 5af73e8f5455aefc06597a933160da1af33 |
| SANs: *.courts.tennis, courts.tennis | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.courts.tennis. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| tennis. | present | 41695 | 8 | Verified |
| courts.tennis. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.courts.tennis/mcp | Verified | 200 | |
| http (plaintext) | http://www.courts.tennis/mcp | HTTPS enforced | 308 | https://www.courts.tennis/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find_courts Find places to play tennis in New York City ~186
Search the directory of places to play tennis in New York City. Filter by borough, by how you get on a court (walk_on, reservation, private_club), by indoor play, by floodlights, or by minimum court count. Returns each venue with its page URL.
| Name | Type | Req | Description |
|---|---|---|---|
| access | string | – | walk_on: public park, no booking. reservation: public park court bookable through NYC Parks. private_club: runs its own booking. |
| borough | string | – | Borough name, e.g. Manhattan, Brooklyn, Queens, Bronx, Staten Island. |
| indoorOnly | boolean | – | Only venues where a source confirms indoor play. Venues never researched are excluded rather than assumed outdoor. |
| limit | integer | – | Maximum venues to return. Default 25, maximum 120. |
| minCourts | integer | – | Minimum number of courts at the venue. |
No output schema declared.
No examples provided.
get_court Full detail for one place to play ~75
Everything the directory holds about one venue: courts, surfaces, floodlights, indoor season, accessibility, reservation programmes, coordinates, and the source each fact was read from. Takes the slug returned by find_courts.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Venue slug, e.g. central-park. From find_courts. |
No output schema declared.
No examples provided.
how_to_play_tennis_in_nyc How playing tennis in New York City actually works ~85
Start here before answering any question about playing tennis in New York City. Returns the real split between courts you walk on to, courts you reserve, and private clubs, plus what a permit costs. Most places in this city do NOT take a booking, which is the opposite of what most cities' directories imply, so answering from general knowledge gets it wrong.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the tennis.courts/nyc-tennis-courts MCP server?
tennis.courts/nyc-tennis-courts is an MCP server listed in the public MCP registry as tennis.courts/nyc-tennis-courts. Every place to play tennis in New York City: which you walk on to, which take a booking. This page covers its hosted endpoint (https://www.courts.tennis/mcp).
Is the tennis.courts/nyc-tennis-courts MCP server safe to use?
tennis.courts/nyc-tennis-courts scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the tennis.courts/nyc-tennis-courts MCP server expose?
tennis.courts/nyc-tennis-courts exposes 3 tools: how_to_play_tennis_in_nyc, find_courts, get_court. Their descriptions and schemas cost roughly 346 tokens of context every time the server is loaded.
Does the tennis.courts/nyc-tennis-courts MCP server require authentication?
No. We connected to tennis.courts/nyc-tennis-courts without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the tennis.courts/nyc-tennis-courts MCP server still maintained?
tennis.courts/nyc-tennis-courts is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.