mcp-registry/com.detourmap/places · v1.0.0
As of 2026-10-27 01:41 UTC, the Detourmap Places MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 8 minutes.
Places worth a detour, from Wikidata: search, nearby lookup, fame rankings, stats. No key, CC0.
Point your MCP client at this streamable-http endpoint: https://detourmap.com/mcp
8 of 8 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 →
2 parameter(s) across 1 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 →
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. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.detourmap%2Fplaces/fixes
{
"name": "get_place",
"description": "Fetch one place’s full record by slug (preferred, e.g. \"neuschwanstein-castle\") or exact name: coordinates, founding year, worldwide fame rank and tier, short description, photo URL, Wikipedia and Wikidata links, and a deep link that opens it on the map. Unsure of the slug? Call search_places first.",
"inputSchema": {
"type": "object",
"required": [
"place"
],
"properties": {
"place": {
"type": "string",
"description": "Slug (preferred, e.g. \"colosseum\") or exact name"
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Get one place in full"
}{
"name": "get_statistics",
"description": "Headline statistics computed live from the atlas: totals by kind, top countries, fame-tier sizes, dated-entry stats, geographic extremes and the most famous place. The source for aggregate claims like \"how many castles are on Detourmap\" or \"which country has the most notable places\".",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": true
},
"title": "Atlas statistics"
}{
"name": "list_countries",
"description": "Every country in the atlas with its place count, most first — answers \"which country has the most notable places\". Countries with eight or more places include a browsable index page URL.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": true
},
"title": "Countries with place counts"
}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.detourmap/places"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.detourmap/places"}) over MCP.
places_near ~251 tokenssearch_places ~241 tokenstop_places ~186 tokensrandom_place ~146 tokensget_place ~139 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.detourmap%2Fplaces?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.detourmap%2Fplaces?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.detourmap%2Fplaces.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.detourmap%2Fplaces.svg :target: https://glimind.com/server/mcp-registry%2Fcom.detourmap%2Fplaces?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:1d5a361ac6685cde…, first seen 2026-10-17, included at leaf 10498 of 76,654. Version history · verify what your client received.
Compare: most reliable search servers · most reliable knowledge servers · most reliable other 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-27 01:41 UTC, the Detourmap Places MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 8 minutes.
Detourmap Places MCP server advertises 8 tools, including get_place, get_statistics, list_countries, list_kinds, places_near.
Point your MCP client at this streamable-http endpoint: https://detourmap.com/mcp
Glimind scanned all 8 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.