
DaedalMap MCP server
Which servers in the official MCP registry are DaedalMap's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-19
- Registry namecom.daedalmap/boundariesverified in the MCP registry
The registry name sits under daedalmap.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-19
- Tools7
- Server calls itselfcom.daedalmap/boundaries
- Server version1.3.2
- Protocol version2025-06-18
On 2026-10-19 the server answered initialize and tools/list without a sign-in. First answer in 124 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 3 of the 7 days it takes to judge reliability.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
- Use2 GitHub stars
- Answeredmeasuring3 of the 7 daily checks it takes to print a share
- Median first answer152 ms
- Space in an agent's context≈ 1,699 tokensthe definitions of all its tools (7), which an agent carries on every turn
- Tool definitionsA · 98 of 100
- Typed results7 of 7 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 1 of 7
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
get_tool_helpDescribe one tool visible on this facade, including its exact contract, or return a bounded workflow overview for one supported topic.
get_catalogChoose data or geometry to list published pack IDs or family and scope IDs. The response includes a complete catalog download URL. Use get_pack for data or get_geography for geometry. Current catalog: The same geography tools work…
get_packInspect one exact data pack ID for its metrics, time coverage, and query metadata before get_data.
get_geographyInspect one published geometry family across scopes or one scope across families. Returns coverage and known editions from catalog metadata only. Optional year selects the latest admitted edition no later than that year when the selected…
get_loc_id_infoLook up one known loc_id or a small batch in the selected reference graph. Return its identity and directly recorded loc_id connections, with family, direction, and relationship evidence. Each ID returns at most 50 connections and an…
compare_geographiesCompare two known loc_ids using selected reference-graph identity and direct relationship evidence. Verified Admin ancestry can prove containment; a typed graph edge can prove only the relation it declares. An explicit negative edge…
get_shapeShape lookup for exact existing loc_ids only. The default returns shape availability, centroid, and bounding box; include_polygon=true adds GeoJSON coordinates. Obtain any descendant IDs before this call. Historical geometry is returned…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"boundaries": {
"type": "http",
"url": "https://app.daedalmap.com/mcp/boundaries"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http daedalmap https://app.daedalmap.com/mcp/boundariesclaude.ai, ChatGPT and other clients: add https://app.daedalmap.com/mcp/boundaries as a custom connector in the settings.
- com.daedalmap/county-mapanswers, 14 toolsverified in the MCP registry
- com.daedalmap/earthquakesanswers, 5 toolsverified in the MCP registry
- com.daedalmap/floodsnot asked yetverified in the MCP registry
- com.daedalmap/geocodingnot asked yetverified in the MCP registry
- com.daedalmap/hurricanesnot asked yetverified in the MCP registry
- com.daedalmap/reverse-geocodingnot asked yetverified in the MCP registry
- com.daedalmap/tornadoesnot asked yetverified in the MCP registry
- com.daedalmap/tsunamisnot asked yetverified in the MCP registry
- com.daedalmap/un_sdgnot asked yetverified in the MCP registry
- com.daedalmap/volcanoesnot asked yetverified in the MCP registry
- com.daedalmap/wildfiresnot asked yetverified in the MCP registry
- com.daedalmap/world_factbooknot asked yetverified in the MCP registry
- com.daedalmap/world-development-indicatorsnot asked yetverified in the MCP registry
OpenAPI spec
178 paths, read 2026-10-19. Open the spec ↗
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.