Skip to content

tennis.courts/nyc-tennis-courts

by courts.tennis · remote · no sign-in to list tools · v2.18.0 · published by tennis.courts

Where to play tennis in New York, London, Paris and more cities: walk on, book or join. Sourced.

Changes · 2

4 tools: 2 change things and 2 only read.

Scanned Oct 21, 2026

2 checks matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The server marks "list_cities" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "list_cities" says "list": a word for reading.

    What this check looks for
  • The server marks "how_to_play_tennis_in_nyc" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.

    What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

4 tools

Changes things 2Claude Code: ask
  • how_to_play_tennis_in_nycCall this before answering any question about playing tennis in New York City.1 finding

    Why it is in this group

    • The description's first verb is "call": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "how_to_play_tennis_in_nyc" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "call": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_citiesStart 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…1 finding

    Why it is in this group

    • The name "list_cities" says "list": a word for reading.
    • The description's first verb is "start": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "list_cities" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "list_cities" says "list": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 2Claude Code: allow
  • find_courtsSearch 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 Ange…No findings

    Why it is in this group

    • The name "find_courts" says "find": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_courtEverything 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 fa…No findings

    Why it is in this group

    • The name "get_court" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 2.18.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__nyc-tennis-courts__find_courts",
      "mcp__nyc-tennis-courts__get_court"
    ],
    "ask": [
      "mcp__nyc-tennis-courts__list_cities",
      "mcp__nyc-tennis-courts__how_to_play_tennis_in_nyc"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as nyc-tennis-courts. Review it before you use it.