CourtlyGo MCP server
com.courtlygo/courtscourtlygo.comstreamable-httpv0.2.0Scanned
Tennis, pickleball and padel courts from OpenStreetMap: surface, lighting, access, fee. Read-only.
3 tools: 3 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the CourtlyGo MCP server can do
The CourtlyGo MCP server is published by courtlygo.com, a domain the MCP Registry verified. It has 3 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
1 tool brings in text other people can write (get_court).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 12, 2026, version 0.2.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Only reads 3Show 3 read-only tools
get_courtGet the details of one court venue by its id from search_courts: courts per sport, surface, lighting, access, fee, website, opening hours, OpenStreetMap links, source, data date an…Reads text others writeNo findings
Why it is in this group
- The name "get_court" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "get" and "website": it reads web pages, which anyone can write.
Description, as the server wrote it Get the details of one court venue by its id from search_courts: courts per sport, surface, lighting, access, fee, website, opening hours, OpenStreetMap links, source, data date and caveats.
Annotations the server declares
- title: Get court details
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_coverageList the covered cities and metro areas with the number of venues in each, grouped by country.No findings
Why it is in this group
- The name "list_coverage" says "list": a word for reading.
Description, as the server wrote it List the covered cities and metro areas with the number of venues in each, grouped by country. It does not list courts: to find courts, call search_courts with city=<a name from this list>. Pass 'country' (e.g. 'Spain') to list one country; 'detail'=true adds per-city counts by sport (larger answer). The counts are mapped venues, not a quality measure.
Annotations the server declares
- title: List coverage
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
search_courtsSearch mapped tennis, pickleball and padel courts in a covered city or metro area, or around a point.No findings
Why it is in this group
- The name "search_courts" says "search": a word for reading.
Description, as the server wrote it Search mapped tennis, pickleball and padel courts in a covered city or metro area, or around a point. Pass 'city' (e.g. 'Austin, TX', 'Lisbon', 'Los Angeles area'; add 'country' if the name is ambiguous) or 'lat'+'lon' (+'radius_km'). Optional filters: sport, setting (outdoor or indoor), lit, open_to_public, free (mapped as no fee), min_courts. Each result is a venue with the number of courts ('courts' is the total at the venue, 'matched_sport_courts' the number for the requested sport), lighting, surface, access, the nearest park or street ('near'), a map link and the source. Results list courts open to the public first and clubs last; check each result's open_to_public, access_note and 'near'. 'unknown' means not mapped. If fewer than 3 courts match and others were left out only because a property is unmapped, they are added and marked 'matched_unknown'. If no court of the requested sport is mapped, the nearest tennis courts are returned in 'alternatives' (tennis, not the sport asked for). A place that is not covered returns an error; list_coverage shows the covered places. Mapped facts only: no bookings or live availability. Data comes from OpenStreetMap (ODbL), is often incomplete, and every answer carries the data date and attribution.
Annotations the server declares
- title: Search courts
- 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.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:36 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools3 changed.~3 changedView diff
- Changed:get_courtOnly readsdescriptionannotations
- Changed:list_coverageOnly readsdescriptioninputSchemaannotations
- Changed:search_courtsOnly readsdescriptioninputSchemaannotations
Install
Pinned to version 0.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http courts https://courtlygo.com/mcpclaude mcp add --transport http courts https://courtlygo.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__courts__search_courts",
"mcp__courts__get_court",
"mcp__courts__list_coverage"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as courts. Review it before you use it.
Capability tags behind 1 rule
- mcp__courts__get_court untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.courtlygo/courts/verify?hash=203e9bdb66009eb7e5bc425ac0e11b50217ca63cb4bf9c6134c3864929b4c915" | jq -e '.changed == false'Pinned hash 203e9bdb6600, from Nov 12, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.courtlygo/courts/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.courtlygo/courts)Source: MCP Registry. Synced Oct 21, 2026, 17:53 UTC.
CourtlyGo MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the CourtlyGo MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the CourtlyGo MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the CourtlyGo MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the CourtlyGo MCP server have?
- 3 tools: 3 read. search_courts, get_court and list_coverage.
Does the CourtlyGo MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the CourtlyGo MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the CourtlyGo MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Oct 31, 2026. Every change is on this page and in its Atom feed.