mcp-registry/com.thecastlemap/castles · v1.1.0
Also listed as awesome/flightmussy/castlemap-mcp, glama/flightmussy/castlemap-mcp
As of 2026-10-19 05:25 UTC, the Thecastlemap Castles MCP server is up with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 7 minutes.
Castles, fortresses, palaces and ruins worldwide: search, nearby, fame ranking, statistics. CC0.
Claude Code
claude mcp add --transport http thecastlemap-castles-mcp-server https://thecastlemap.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"thecastlemap-castles-mcp-server": {
"type": "http",
"url": "https://thecastlemap.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
7 of 7 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
4 parameter(s) across 2 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
Handshake + tools/list takes ~1,987 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 2 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.thecastlemap%2Fcastles/fixes
{
"name": "castles_near",
"description": "List landmarks within a radius of a WGS84 coordinate, nearest first, each with distance_km. Radius defaults to 100 km (max 2,000). For \"castles near <place>\", geocode the place yourself, then call this with its latitude/longitude.",
"inputSchema": {
"type": "object",
"required": [
"latitude",
"longitude"
],
"properties": {
"limit": {
"type": "integer",
"maximum": 50,
"minimum": 1,
"description": "Max results (default 10)"
},
"category": {
"enum": [
"castle",
"fortress",
"palace",
"ruin"
],
"type": "string"
},
"latitude": {
"type": "number",
"maximum": 90,
"minimum": -90
},
"longitude": {
"type": "number",
"maximum": 180,
"minimum": -180
},
"radius_km": {
"type": "number",
"maximum": 2000,
"minimum": 1,
"description": "Search radius in km (default 100)"
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Find castles near a point"
}{
"name": "get_castle",
"description": "Fetch one landmark’s full record by slug (preferred, e.g. \"palace-of-versailles\") or exact name: coordinates, founding year and century, worldwide fame rank, photo URL with photographer credit and licence, Wikipedia link and its readership signals (Wikidata sitelinks, Wikipedia pageviews over the last 60 days summed across its largest language editions). Unsure of the slug? Call search_castles first.",
"inputSchema": {
"type": "object",
"required": [
"castle"
],
"properties": {
"castle": {
"type": "string",
"description": "Slug (preferred, e.g. \"himeji-castle\") or exact name"
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Get one castle in full"
}{
"name": "get_statistics",
"description": "Headline statistics computed live from the atlas: totals by type, top countries, busiest founding century, oldest landmarks, geographic extremes and the most famous entry. The source for claims like \"which country has the most castles\" or \"when were castles built\"; the full write-up lives at thecastlemap.com/statistics/.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": true
},
"title": "Atlas statistics"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.thecastlemap/castles"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.thecastlemap/castles"}) over MCP.
search_castles ~249 tokenscastles_near ~207 tokenstop_castles ~175 tokensget_castle ~170 tokensget_statistics ~116 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.thecastlemap%2Fcastles?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.thecastlemap%2Fcastles?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.thecastlemap%2Fcastles.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.thecastlemap%2Fcastles.svg :target: https://glimind.com/server/mcp-registry%2Fcom.thecastlemap%2Fcastles?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:6b115db29c4331fb…, first seen 2026-10-17, included at leaf 14223 of 25,026. Version history · verify what your client received.
Compare: most reliable search servers · most reliable retrieval servers · most reliable data servers · most reliable knowledge servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-19 05:25 UTC, the Thecastlemap Castles MCP server is up with a Glimind reliability score of 86/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 7 minutes.
Thecastlemap Castles MCP server advertises 7 tools, including castles_near, get_castle, get_statistics, list_countries, random_castle.
Point your MCP client at this streamable-http endpoint: https://thecastlemap.com/mcp
Glimind scanned all 7 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.