DaedalMap Administrative Boundaries (loc_id to polygon)
MCP server · app.daedalmap.com · found in a public list · checked since 2026-11-12
Live, handshake completed · latest check
Retrieves administrative boundary shapes and compares places by loc_id.
Our summary of what its own text says it does: automated, not reviewed by a person (placement-ai/7). What this means
Placed in Map layers and GIS data: Query geospatial layers, features and boundaries from GIS servers and spatial catalogues (other datasets: search/reference/public-data/open-data-portals).
https://app.daedalmap.com/mcp/boundaries?registry=mcpregistry MCP endpoint (Streamable HTTP)The name is the registry's label, not ours. Not reviewed by a person. See 24 endpoints from daedalmap.com.
Our checks
An unpaid request daily, from eastern North AmericaLast 1 checks, oldest to newest; room for 29 more
1 passed, 0 failed, 29 not run.
Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.
Response times
| Window | Checks | Timeouts | Median | 90th | 95th | 99th | Fastest | Slowest |
|---|---|---|---|---|---|---|---|---|
| 24 hourssince 2026-11-12 | 1 | 0 | — | — | — | — | — | — |
| 7 dayssince 2026-11-12 | 1 | 0 | — | — | — | — | — | — |
| 30 dayssince 2026-11-12 | 1 | 0 | — | — | — | — | — | — |
Milliseconds, from eastern North America, timing the whole MCP handshake (initialize to the tools/list answer). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.
Details
Tools listed by the server
compare_geographiesget_catalogget_geographyget_loc_id_infoget_packget_shapeget_tool_help
- Tools
- 7
- This list since
- 2026-11-12
- First listed to us
- 2026-11-12
- List changes, 90 days
- 0
Names as the server reported them at our latest completed handshake (mcp-handshake/2); a listed tool is not a tested one. Definitions
Access
- Our latest check
- Nothing asked
- Stated
- not stated
- Payment model
- not known
- Currency
- not known
"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions
Interface it declares
- Protocol
- MCP 2025-06-18
- Capabilities
- promptsresourcestools
- Transports
- streamable-http
As its initialize reply stated it at our check on (mcp-handshake/2): a claim, not tested. Definitions
What it says about itself
- Where it works
- Worldwidefrom its tool list, read 2026-11-12
From the service's own text, put in short words by a small AI model and shown only where its own words support it (stated-facts/5): its claims, not checked by us. Anything not listed, it does not state. Definitions
Calls it declares
get_tool_help tool_name topic question → request_id error reason next_step warningsget_catalog catalog* → request_id error reason next_step warningsget_pack pack_id* → request_id error reason next_step warningsget_geography family_id scope_id year → request_id error reason next_step warningsget_loc_id_info loc_id loc_ids batch_id request_id → request_id batch_id ok error reasoncompare_geographies left_loc_id right_loc_id as_of left_as_of right_as_of include_successors items batch_id request_id → request_id batch_id ok error reasonget_shape loc_id loc_ids include_polygon batch_id request_id → request_id batch_id ok error reason
From the tool list it returned to our check (request-shape/2). * marks a required parameter; after → the fields it says it returns. What it declares, not that a call works.
Links
What it states about itself, from its registry entry or package:
- Website: www.daedalmap.com
- Repository: github.com/xyver/daedal-map
Pages we read:
- llms.txt: app.daedalmap.com/llms.txt, read
- README: raw.githubusercontent.com/xyver/daedal-map/HEAD/README.md, read
Its own links, from its llms.txt, under its own headings and names. These are its words, not ours:
Coverage
Links only (links/3): we follow none of them when showing this page, and a link is not a recommendation. How links are chosen.
Listing
In the capability tree: Maps, places and weather / Maps and geocoding / Map layers and GIS data (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/7, tree/3) on 2026-11-12. Wrong place? Tell us.
In the directory: meets our listing criteria (listing-criteria/6): ✓ says what it does; ✓ its latest check passed.
Recent probes
| When | Result | Time to headers |
|---|---|---|
cloudflare:EWR |
Live, handshake completed HTTP 200 | 472 ms |
What these figures do not show
- A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/2) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
- Listed in the Official MCP Registry; this data comes from the Official MCP Registry. Its listing's description is not republished.
- Limited evidence: monitored for under 1 day (less than 30).
Something wrong here?
Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.
Machine-readable: /api/v1/services/cand_329af961b2bf15c3