CourtWatch Agent API
REMOTE · COURTWATCH.TECH
Pickleball and padel club demand data: query venues, markets and rollups, plus public pages. No key.
Available components
Last scanned (18 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Data and Analytics
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 Security74
- 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. 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 89% of tool parameters carry a description.Partial
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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +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.
- 18 Nov 26 +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.
- 16 Nov 26 +1
- 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 security
- “data” reworded the description of “endpoint” cosmetic
- 15 Nov 26 0
- 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 security
- “data” reworded the description of “params” cosmetic
- 14 Nov 26 +1
- 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 security
- Stability: unverified → 0.03 ▲ functional
- “data” reworded the description of “endpoint” cosmetic
- 13 Nov 26 66
First indexed and scored.
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 21 Nov 2026 · Probed https://courtwatch.tech/api/agent
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=courtwatch.tech | CN=WE1,O=Google Trust Services,C=US | 9 Nov 2026 | 7 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 119bc196814ef7b913eb3873cee15ca4 |
| SANs: courtwatch.tech | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of courtwatch.tech. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| tech. | DS published | 2185 | 13 | Verified |
| courtwatch.tech. | No DS | 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 |
|---|---|
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://courtwatch.tech/api/agent | Verified | 200 | |
| http (plaintext) | http://courtwatch.tech/api/agent | HTTPS enforced | 301 | https://courtwatch.tech/api/agent |
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 →
about About CourtWatch data ~42
What CourtWatch (https://courtwatch.tech) measures at pickleball and padel clubs, its plans, free sample day and every document id, plus its sister sites.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
data Query venue and market data ~411
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/
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint | string | yes | 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. |
No output schema declared.
No examples provided.
fetch Read a document or sample day ~75
Read one document by id (from search or about). sample/<site> returns that site's free example day as rows, CC BY 4.0.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Document id, e.g. heatcheck/methodology or sample/heatcheck. |
| offset | integer | – | Continue a long document from nextOffset. |
No output schema declared.
No examples provided.
search Search CourtWatch ~176
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The question. |
| site | string | – | Optional: defaults to courtwatch. all, heatcheck, bowlingdata, trampolineparkdata, golfsimdata, courtwatch or fronresearch. |
No output schema declared.
No examples provided.
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.
remote · courtwatch.tech
claude mcp add --transport http tech-courtwatch-agent-api 'https://courtwatch.tech/api/agent'
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.