# CourtlyGo (remote · courtlygo.com)

Tennis, pickleball and padel courts from OpenStreetMap: surface, lighting, access, fee. Read-only.

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `courtlygo.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/com-courtlygo-courts/courtlygo.md), [page](https://verifymcp.io/servers/com-courtlygo-courts/courtlygo)

## Channel facts

- Endpoint: `https://courtlygo.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.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-10-18.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 58/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 674 tokens (~224/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**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 93% 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**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the CourtlyGo MCP server?

CourtlyGo is a hosted endpoint at https://courtlygo.com/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 com-courtlygo-courts 'https://courtlygo.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-courtlygo-courts": {
      "url": "https://courtlygo.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-courtlygo-courts": {
      "type": "http",
      "url": "https://courtlygo.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-courtlygo-courts]
url = "https://courtlygo.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-courtlygo-courts --url 'https://courtlygo.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-courtlygo-courts:
    url: "https://courtlygo.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-courtlygo-courts": {
      "Transport": "http",
      "Url": "https://courtlygo.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-courtlygo-courts -t streamable-http -u 'https://courtlygo.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-courtlygo-courts": {
      "type": "http",
      "url": "https://courtlygo.com/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-10-18 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-17 (score 69, 0)

- [cosmetic] “search_courts” dropped the optional parameter “include_private”

### 2026-10-16 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-15 (score 68, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-14 (score 68)

First indexed and scored.

## MCP tools (3)

### `search_courts` (~528 tokens)

Search courts

Search tennis, padel and pickleball courts in a covered city, metro area or around a point. Use 'city' (e.g. 'Austin, TX', 'Long Beach', 'Tbilisi' or 'Los Angeles area'; 'country' if the name is ambiguous) or 'lat'+'lon'+'radius_km'. Results are venues (courts within 70 m are merged) with number of courts, surface, lighting, access, fee, address or the park/street nearby, and the source of each record. Filters are strict: a court passes only if the property is explicitly mapped; set match_unknown=true to also include courts where it is unknown. Data comes from OpenStreetMap (ODbL) and is often incomplete; every answer carries the data date and attribution.

Input parameters:

- `city` (string): A covered city, e.g. 'Austin, TX', 'Long Beach' or 'Tbilisi', or a whole metro area, e.g. 'Los Angeles area' (all of Los Angeles and Orange counties) or 'New York area'. See list_coverage.
- `country` (string): Country name or ISO code, e.g. 'Georgia', 'GE', 'US'. Use it when the same city name exists in several countries; with lat/lon it limits the search to that country. Distances are in miles for the US…
- `free` (boolean): Only courts mapped as free of charge (fee=no).
- `lat` (number): Latitude of the search point (use with lon).
- `limit` (integer)
- `lit` (boolean): Only courts with lighting.
- `lon` (number): Longitude of the search point (use with lat).
- `match_unknown` (boolean): Also return courts where a filtered property is not mapped (unknown).
- `min_courts` (integer): Minimum number of courts at the venue.
- `offset` (integer): Skip this many results (paging).
- `open_to_public` (boolean): Only courts anyone can use: access is public, or free of charge, or inside a park. Clubs (access_status club), private and likely private courts are excluded.
- `radius_km` (number): Search radius around lat/lon, km.
- `setting` (string): 'outdoor' = open-air courts; 'indoor' = indoor or covered.
- `sport` (string): Sport: tennis, padel or pickleball. Omit for any.

### `get_court` (~64 tokens)

Get court details

Get full details of one court venue by id (from search_courts): courts per sport, surface, access, OpenStreetMap links, source, data date and caveats.

Input parameters:

- `id` (string, required): Venue id, e.g. 'way-123456'.

### `list_coverage` (~28 tokens)

List coverage

List the covered cities with the number of venues per sport, the data date and the attribution.

## Diagnostics

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

## Score history

- 2026-10-18: 70
- 2026-10-17: 69
- 2026-10-16: 69
- 2026-10-15: 68
- 2026-10-14: 68

## Common questions

### What is the CourtlyGo MCP server?

CourtlyGo is an MCP server listed in the public MCP registry as com.courtlygo/courts. Tennis, pickleball and padel courts from OpenStreetMap: surface, lighting, access, fee. Read-only. This page covers its hosted endpoint (https://courtlygo.com/mcp).

### Is the CourtlyGo MCP server safe to use?

CourtlyGo scores 70 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 CourtlyGo MCP server expose?

CourtlyGo exposes 3 tools: search_courts, get_court, list_coverage. Their descriptions and schemas cost roughly 620 tokens of context every time the server is loaded.

### Does the CourtlyGo MCP server require authentication?

No. We connected to CourtlyGo without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the CourtlyGo MCP server still maintained?

CourtlyGo is still listed as active in the MCP registry. We last reached this channel on 18 October 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://courtlygo.com/mcp
- Website: https://courtlygo.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-courtlygo-courts/courtlygo.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-courtlygo-courts/courtlygo.json
- HTML version of this page: https://verifymcp.io/servers/com-courtlygo-courts/courtlygo