# CourtWatch Agent API (remote · courtwatch.tech)

Pickleball and padel club demand data: query venues, markets and rollups, plus public pages. No key.

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

## Components

- remote · `courtwatch.tech`: 70/100 (this document), [markdown](https://verifymcp.io/servers/tech-courtwatch-agent-api/api-agent.md), [page](https://verifymcp.io/servers/tech-courtwatch-agent-api/api-agent)

## Channel facts

- Endpoint: `https://courtwatch.tech/api/agent`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.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-11-21.

- **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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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 913 tokens (~228/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 89% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 CourtWatch Agent API MCP server?

CourtWatch Agent API is a hosted endpoint at https://courtwatch.tech/api/agent, 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 tech-courtwatch-agent-api 'https://courtwatch.tech/api/agent'
```

### Cursor

```json
{
  "mcpServers": {
    "tech-courtwatch-agent-api": {
      "url": "https://courtwatch.tech/api/agent"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tech-courtwatch-agent-api": {
      "type": "http",
      "url": "https://courtwatch.tech/api/agent"
    }
  }
}
```

### Codex

```toml
[mcp_servers.tech-courtwatch-agent-api]
url = "https://courtwatch.tech/api/agent"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tech-courtwatch-agent-api": {
      "type": "remote",
      "url": "https://courtwatch.tech/api/agent",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tech-courtwatch-agent-api --url 'https://courtwatch.tech/api/agent' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tech-courtwatch-agent-api:
    url: "https://courtwatch.tech/api/agent"
```

### Netclaw

```json
{
  "McpServers": {
    "tech-courtwatch-agent-api": {
      "Transport": "http",
      "Url": "https://courtwatch.tech/api/agent"
    }
  }
}
```

### Vellum

```bash
assistant mcp add tech-courtwatch-agent-api -t streamable-http -u 'https://courtwatch.tech/api/agent'
```

### Other

```json
{
  "mcpServers": {
    "tech-courtwatch-agent-api": {
      "type": "http",
      "url": "https://courtwatch.tech/api/agent"
    }
  }
}
```

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-11-21 (score 70, +1)

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

### 2026-11-18 (score 69, +1)

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

### 2026-11-16 (score 68, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “data” rewrote its description, which is the text the model reads
- [cosmetic] “data” reworded the description of “endpoint”

### 2026-11-15 (score 67, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “data” rewrote its description, which is the text the model reads
- [cosmetic] “data” reworded the description of “params”

### 2026-11-14 (score 67, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “data” rewrote its description, which is the text the model reads
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “data” reworded the description of “endpoint”

### 2026-11-13 (score 66)

First indexed and scored.

## MCP tools (4)

### `about` (~42 tokens)

About CourtWatch data

What CourtWatch (https://courtwatch.tech) measures at pickleball and padel clubs, its plans, free sample day and every document id, plus its sister sites.

### `search` (~176 tokens)

Search CourtWatch

Ask a question in plain language. Returns the most relevant passages from CourtWatch's public pages, each with its canonical URL to cite, plus its free sample day. Set site to all to search every Fron Research site.

Input parameters:

- `intent` (string): Optional but helpful: why you are asking and for whom, in a sentence (e.g. "sizing the NYC sauna market for an investor memo"). It does not change the results; it tells Fron Research which data to pu…
- `maxResults` (integer)
- `query` (string, required): The question.
- `site` (string): Optional: defaults to courtwatch. all, heatcheck, bowlingdata, trampolineparkdata, golfsimdata, courtwatch or fronresearch.

### `fetch` (~75 tokens)

Read a document or sample day

Read one document by id (from search or about). sample/<site> returns that site's free example day as rows, CC BY 4.0.

Input parameters:

- `id` (string, required): Document id, e.g. heatcheck/methodology or sample/heatcheck.
- `offset` (integer): Continue a long document from nextOffset.

### `data` (~411 tokens)

Query venue and market data

Structured rows from the Consumer Recreation Demand API (https://api.fronresearch.com/v1): markets, venues, bookable slots and a utilization and a revenue estimate per venue, market or day. Without a key every query reads one free sample day for every venue, whatever dates are asked (the response's tier, free_day and range say what was read); a caller that connects to https://fronresearch.com/api/agent with "Authorization: Bearer <key>" reads the history its plan covers (a site's own /api/agent does not forward keys). Start with endpoint index (the sample day and endpoints), then markets or venues to get ids, then demand. Fields, filters and how to get a key: https://fronresearch.com/data/history/

Input parameters:

- `endpoint` (string, required): index: the sample day, tier and endpoints. markets, venues: lists (filters: market, brand, venue_type, activity). venue: one venue with its products and resources (needs venue_id). demand: the data,…
- `params` (object): Query parameters as the Consumer Recreation Demand API names them, e.g. {"group_by": "market", "from": "2026-11-05", "to": "2026-11-05"}. limit (1-1000) and cursor (from next_cursor) page through lis…
- `venue_id` (string): For endpoint venue: a venue_id from venues.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/tech-courtwatch-agent-api/api-agent#diagnostics

## Score history

- 2026-11-21: 70
- 2026-11-20: 69
- 2026-11-19: 69
- 2026-11-18: 69
- 2026-11-17: 68
- 2026-11-16: 68
- 2026-11-15: 67
- 2026-11-14: 67
- 2026-11-13: 66

## Common questions

### What is the CourtWatch Agent API MCP server?

CourtWatch Agent API is an MCP server listed in the public MCP registry as tech.courtwatch/agent-api. Pickleball and padel club demand data: query venues, markets and rollups, plus public pages. No key. This page covers its hosted endpoint (https://courtwatch.tech/api/agent).

### Is the CourtWatch Agent API MCP server safe to use?

CourtWatch Agent API 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 CourtWatch Agent API MCP server expose?

CourtWatch Agent API exposes 4 tools: about, search, fetch, data. Their descriptions and schemas cost roughly 704 tokens of context every time the server is loaded.

### Does the CourtWatch Agent API MCP server require authentication?

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

### Is the CourtWatch Agent API MCP server still maintained?

CourtWatch Agent API is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the CourtWatch Agent API MCP server?

VerifyMCP ran 13 checks on CourtWatch Agent API, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://courtwatch.tech/api/agent
- Website: https://courtwatch.tech/
- Changelog RSS feed: https://verifymcp.io/servers/tech-courtwatch-agent-api/api-agent.xml
- Changelog JSON feed: https://verifymcp.io/servers/tech-courtwatch-agent-api/api-agent/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/tech-courtwatch-agent-api/api-agent.json
- HTML version of this page: https://verifymcp.io/servers/tech-courtwatch-agent-api/api-agent
