# tennis.courts/nyc-tennis-courts (remote · www.courts.tennis)

Every place to play tennis in New York City: which you walk on to, which take a booking.

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `www.courts.tennis`: 79/100 (this document), [markdown](https://verifymcp.io/servers/tennis-courts-nyc-tennis-courts/www.md), [page](https://verifymcp.io/servers/tennis-courts-nyc-tennis-courts/www)

## Channel facts

- Endpoint: `https://www.courts.tennis/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http tennis-courts-nyc-tennis-courts 'https://www.courts.tennis/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "tennis-courts-nyc-tennis-courts": {
      "url": "https://www.courts.tennis/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tennis-courts-nyc-tennis-courts": {
      "type": "http",
      "url": "https://www.courts.tennis/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.tennis-courts-nyc-tennis-courts]
url = "https://www.courts.tennis/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tennis-courts-nyc-tennis-courts": {
      "type": "remote",
      "url": "https://www.courts.tennis/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tennis-courts-nyc-tennis-courts --url 'https://www.courts.tennis/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tennis-courts-nyc-tennis-courts:
    url: "https://www.courts.tennis/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "tennis-courts-nyc-tennis-courts": {
      "Transport": "http",
      "Url": "https://www.courts.tennis/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add tennis-courts-nyc-tennis-courts -t streamable-http -u 'https://www.courts.tennis/mcp'
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 79, 0)

- [security] Stability: 0.97 → pass

### 2026-09-19 (score 79, +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.

### 2026-09-17 (score 78, +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.

### 2026-09-15 (score 77, +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.

### 2026-09-12 (score 76, +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.

### 2026-09-10 (score 75, +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.

### 2026-09-08 (score 74, +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.

### 2026-09-06 (score 73, +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.

## MCP tools (3)

### `how_to_play_tennis_in_nyc` (~85 tokens)

How playing tennis in New York City actually works

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.

### `find_courts` (~186 tokens)

Find places to play tennis in New York City

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.

Input parameters:

- `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.

### `get_court` (~75 tokens)

Full detail for one place to play

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.

Input parameters:

- `slug` (string, required): Venue slug, e.g. central-park. From find_courts.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/tennis-courts-nyc-tennis-courts/www#diagnostics

## Score history

- 2026-09-21: 79
- 2026-09-20: 79
- 2026-09-19: 79
- 2026-09-18: 78
- 2026-09-17: 78
- 2026-09-16: 77
- 2026-09-15: 77
- 2026-09-14: 76
- 2026-09-13: 76
- 2026-09-12: 76
- 2026-09-11: 75
- 2026-09-10: 75
- 2026-09-09: 74
- 2026-09-08: 74
- 2026-09-07: 73
- 2026-09-06: 73
- 2026-09-05: 72
- 2026-09-04: 72
- 2026-09-03: 71
- 2026-09-02: 71
- 2026-09-01: 71
- 2026-08-31: 70
- 2026-08-30: 70
- 2026-08-29: 69
- 2026-08-28: 69
- 2026-08-27: 68
- 2026-08-26: 68
- 2026-08-25: 66
- 2026-08-24: 65
- 2026-08-23: 65

## Common questions

### 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 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://www.courts.tennis/mcp
- Website: https://www.courts.tennis/
- Changelog RSS feed: https://verifymcp.io/servers/tennis-courts-nyc-tennis-courts/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/tennis-courts-nyc-tennis-courts/www.json
- HTML version of this page: https://verifymcp.io/servers/tennis-courts-nyc-tennis-courts/www