tennis.courts/nyc-tennis-courts
REMOTE · WWW.COURTS.TENNIS
Where to play tennis in New York, London, Paris and more cities: walk on, book or join. Sourced.
Available components
Last scanned (3 hours ago)
Scores higher than 85% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Maps and Location
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability58
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1814 tokens (~453/item across 4 items; 4 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 Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
- 5 Nov 26 −1
- Stability: pass → 0.97 functional
- 14 Oct 26 0
- Server version: 2.18.0 → 2.18.1 functional
- “find_courts” reworded the description of “access” cosmetic
- 10 Oct 26 −2
- The server rewrote its instructions, which are the text every model session reads security
- Tool “find_courts” rewrote its description, which is the text the model reads security
- Tool “list_cities” rewrote its description, which is the text the model reads security
- Schema quality: 277 → 446 ▼ functional
- Server version: 2.2.0 → 2.18.0 functional
- “find_courts” reworded the description of “area” cosmetic
- “find_courts” reworded the description of “city” cosmetic
- “get_court” reworded the description of “city” cosmetic
- 3 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “find_courts” rewrote its description, which is the text the model reads security
- Tool “list_cities” rewrote its description, which is the text the model reads security
- Schema quality: 240 → 277 ▼ functional
- Server version: 2.0.0 → 2.1.0 functional
- “find_courts” reworded the description of “access” cosmetic
- “find_courts” reworded the description of “area” cosmetic
- “find_courts” reworded the description of “city” cosmetic
- “get_court” reworded the description of “city” cosmetic
- 2 Oct 26 85
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “find_courts” rewrote its description, which is the text the model reads security
- Tool “get_court” rewrote its description, which is the text the model reads security
- Tool “how_to_play_tennis_in_nyc” rewrote its description, which is the text the model reads security
- Schema quality: 152 → 240 ▼ functional
- Server version: 1.0.0 → 2.0.0 functional
- New tool “list_cities” functional
- “find_courts” added an optional parameter “area” cosmetic
- “find_courts” added an optional parameter “city” cosmetic
- “find_courts” added an optional parameter “name” cosmetic
- “find_courts” added an optional parameter “nearLatitude” cosmetic
- “find_courts” added an optional parameter “nearLongitude” cosmetic
- “get_court” added an optional parameter “city” cosmetic
- “find_courts” reworded the description of “access” cosmetic
- “find_courts” reworded the description of “borough” cosmetic
- “find_courts” reworded the description of “indoorOnly” cosmetic
- “find_courts” reworded the description of “limit” cosmetic
- “find_courts” reworded the description of “minCourts” cosmetic
- Tool “find_courts” changed its title: Find places to play tennis in New York City → Find places to play tennis in one city cosmetic
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 20 Sept 26 0
- Stability: 0.97 → pass security
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 5 Nov 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=YR2,O=Let's Encrypt,C=US | 25 Sept 2026 | 24 Dec 2026 | RSA 2048 | SHA256-RSA | 6a793a7ddda80771e931cf3f72efd626823 |
| SANs: *.courts.tennis, courts.tennis | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| 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 one city ~807
Search one city's places to play tennis: New York City, Melbourne, London, Paris, Toronto, Washington DC, Madrid, Miami, Sydney, Palm Springs, Adelaide, Cincinnati, Tokyo, Los Angeles, Rome, Houston, Dallas, Chicago, Hong Kong, Montreal, Austin, Boston, Atlanta, Dubai, San Francisco, Seattle, Denver, Orlando, Singapore, Philadelphia, San Diego, Las Vegas, Phoenix, Charlotte, Brisbane, Tampa, Auckland, Dublin, Nice, Minneapolis, Birmingham, Barcelona, Berlin, Osaka, Seoul, Perth, Manchester, Edinburgh, Vienna or Vancouver. Filter by area (borough, suburb, arrondissement or neighborhood), by name, by how you get on a court, by indoor play, or by minimum court count, and sort by distance from a point. Returns each venue with its page URL. There is no floodlights filter: the records are too sparse to filter on without hiding real lit courts.
| Name | Type | Req | Description |
|---|---|---|---|
| access | string | – | How you get on a court. New York: walk_on (public park, no booking), reservation (public park court bookable through NYC Parks), private_club (runs its own booking). Every other city: walk_on, book (… |
| area | string | – | Borough (New York, London), suburb (Melbourne, Sydney), arrondissement (Paris) or the neighborhood the city itself puts the venue in (Toronto, Atlanta, Washington DC), exactly as the directory names… |
| borough | string | – | Same as area. Kept for callers written when the directory was New York only. |
| city | string | – | Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome, houston, dallas, chicago, ho… |
| indoorOnly | boolean | – | Only venues where a source confirms indoor or covered courts, which may be some courts, or winter only: read indoorOrCovered on each. Venues never researched are excluded rather than assumed outdoor. |
| limit | integer | – | Maximum venues to return. Default 25, maximum 150. |
| minCourts | integer | – | Minimum number of courts at the venue. Venues whose court count is not sourced are left out when this is set. |
| name | string | – | Part of a venue's name, e.g. "central park". Case and accents are ignored. |
| nearLatitude | number | – | With nearLongitude: sort by distance from this point, nearest first. |
| nearLongitude | number | – | With nearLatitude: sort by distance from this point, nearest first. |
No output schema declared.
No examples provided.
get_court Full detail for one place to play ~298
Everything the directory holds about one venue: how you get on a court, booking route, price, courts, surfaces, floodlights, hours, indoor play, coordinates, and the source each fact was read from, with the date it was read. Takes the slug returned by find_courts, and its city.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | Which city, one of: nyc, melbourne, london, paris, toronto, washington-dc, madrid, miami, sydney, palm-springs-california, adelaide, cincinnati, tokyo, los-angeles, rome, houston, dallas, chicago, ho… |
| 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
Call this 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.
list_cities The cities this directory covers, and how you get on a court in each ~206
Start here for any question about where to play tennis in New York City, Melbourne, London, Paris, Toronto, Washington DC, Madrid, Miami, Sydney, Palm Springs, Adelaide, Cincinnati, Tokyo, Los Angeles, Rome, Houston, Dallas, Chicago, Hong Kong, Montreal, Austin, Boston, Atlanta, Dubai, San Francisco, Seattle, Denver, Orlando, Singapore, Philadelphia, San Diego, Las Vegas, Phoenix, Charlotte, Brisbane, Tampa, Auckland, Dublin, Nice, Minneapolis, Birmingham, Barcelona, Berlin, Osaka, Seoul, Perth, Manchester, Edinburgh, Vienna or Vancouver. Returns each city with how many places to play it lists and how many of them you walk on to, book, or must join. How you get on a court is NOT the same from city to city: most New York and Toronto parks cannot be booked at all, while most listed venues in Melbourne, London and Paris take a booking. Answering from general knowledge gets it wrong.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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'
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. Where to play tennis in New York, London, Paris and more cities: walk on, book or join. Sourced. 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 82 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 4 tools: list_cities, how_to_play_tennis_in_nyc, find_courts, get_court. Their descriptions and schemas cost roughly 1,396 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.