Connect DaedalMap Administrative Boundaries (loc_id to polygon) and your agent gets 11 tools, among them check_geometry, compare_geographies, create_geometry_export. It answers at https://app.daedalmap.com/mcp/boundaries over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 9 of 10 times since 4 September 2026; the last check, on 18 October 2026, succeeded.
Retrieve loc_id boundary metadata, polygons, scopes, comparisons, and bounded exports.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
check_geometry | Fast shape-only preflight for one loc_id or a bounded loc_id list. Reports whether each exact identity has reusable geometry and its geometry vintage; it does not resolve points or explain identity relationships. Use before get_geometry or Inputs: loc_id, loc_ids, batch_id, request_id |
compare_geographies | Detailed relationship tool for two geographic identities. Returns temporal validity, N-way successor context, topology, geodesic intersection area, and directional overlap shares when approved geometry exists. Use this after a compact point Inputs: left_loc_id, right_loc_id, as_of, left_as_of, right_as_of, include_successors |
create_geometry_export | Creates a synchronous v0 geometry export from exact loc_ids or one strict scope as real GeoJSON, gzipped GeoJSON, or zipped GeoJSON. Hosted service default: 250 selected loc_ids, sized around a 10-20 second response budget and configurable Inputs: quote_id, loc_id, loc_ids, scope, format, output_name |
estimate_geometry_package | Dry-run estimate for a selected geometry export: exact loc_id count, shape/vintage availability, bytes, delivery mode, citation requirements, and charge units. This estimates an export artifact, not a canonical DaedalMap geometry release bu Inputs: loc_id, loc_ids, scope, format, output_name, include_polygon |
get_catalog | Free discovery. Returns the list of live agent-ready data packs available on DaedalMap. |
get_geometry | Shape retrieval for exact loc_ids, including loc_ids from any level of a resolve_point chain. Returns geometry metadata, vintage, centroid, bounding box, and optional GeoJSON polygon. It does not explain hierarchy or crosswalks; use loc_id_ Inputs: loc_id, loc_ids, include_polygon, batch_id, request_id |
get_job_status | Retrieves a completed bounded v0 geometry export or conversion job by job_id. The current public contract creates completed inline jobs only; durable queued jobs and downloadable artifact links remain a future Custom Data Builder capability Inputs: job_id, request_id |
get_pack | Free discovery. Returns detailed metadata, coverage, freshness, preferred canonical tool guidance, and first-query examples for one pack. Call this before querying a new pack so you can see time shape, coverage limits, and the paste-ready f Inputs: pack_id |
get_tool_help | Free blind-caller guidance for one tool visible on this MCP facade. Returns when to use it, what it refuses, a working example, effective access limits, important outputs, provenance fields, recommended next calls, and the shared natural-la Inputs: tool_name |
loc_id_info | The drill-down tool for loc_ids returned by resolve_point and other geography calls. Pass one loc_id, or pass the point result's stack loc_ids together, to retrieve metadata, strict stored parentage, shape status, vintage/lifecycle fields, Inputs: loc_id, loc_ids, include_hierarchy, include_references, systems, iso3 |
resolve_loc_id_scope | Strict hierarchy traversal. Given one stored parent loc_id and target admin level, returns descendants from that coherent parent chain. This is not the mixed-vintage latest-per-depth point resolver and must not bridge release seams. Use it Inputs: parent_loc_id, admin_level, scope, bbox, limit, offset |
Every block below points at https://app.daedalmap.com/mcp/boundaries. Pick your client and copy.
claude mcp add --transport http daedalmap-administrative-boundar https://app.daedalmap.com/mcp/boundaries
{
"mcpServers": {
"daedalmap-administrative-boundar": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://app.daedalmap.com/mcp/boundaries"]
}
}
}{
"mcpServers": {
"daedalmap-administrative-boundar": {
"url": "https://app.daedalmap.com/mcp/boundaries"
}
}
}{
"servers": {
"daedalmap-administrative-boundar": {
"type": "http",
"url": "https://app.daedalmap.com/mcp/boundaries"
}
}
}{
"context_servers": {
"daedalmap-administrative-boundar": {
"url": "https://app.daedalmap.com/mcp/boundaries"
}
}
}{
"mcpServers": {
"daedalmap-administrative-boundar": {
"serverUrl": "https://app.daedalmap.com/mcp/boundaries"
}
}
}{
"mcpServers": {
"daedalmap-administrative-boundar": {
"url": "https://app.daedalmap.com/mcp/boundaries"
}
}
}name: DaedalMap Administrative Boundaries (loc_id to polygon)
version: 0.0.1
schema: v1
mcpServers:
- name: DaedalMap Administrative Boundaries (loc_id to polygon)
type: streamable-http
url: https://app.daedalmap.com/mcp/boundaries{
"mcpServers": {
"daedalmap-administrative-boundar": {
"httpUrl": "https://app.daedalmap.com/mcp/boundaries"
}
}
}{
"mcpServers": {
"daedalmap-administrative-boundar": {
"type": "http",
"url": "https://app.daedalmap.com/mcp/boundaries"
}
}
}{
"mcpServers": {
"daedalmap-administrative-boundar": {
"url": "https://app.daedalmap.com/mcp/boundaries"
}
}
}goose://extension?url=https%3A%2F%2Fapp.daedalmap.com%2Fmcp%2Fboundaries&type=streamable_http&id=daedalmap-administrative-boundar&name=DaedalMap%20Administrative%20Boundaries%20%28loc_id%20to%20polygon%29
It answered our last check on 18 October 2026 in 347 ms. Over 10 checks since 4 September 2026 it answered 9. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by daedalmap.com and served from app.daedalmap.com, the vendor's own domain: https://app.daedalmap.com/mcp/boundaries.
11, as returned by the server's own tools/list on 31 August 2026: check_geometry, compare_geographies, create_geometry_export, estimate_geometry_package, get_catalog, get_geometry, get_job_status, get_pack, and 3 more.
It answered our last check on 18 October 2026 in 347 ms. Over 10 checks since 4 September 2026 it answered 9.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://app.daedalmap.com/mcp/boundaries. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.daedalmap. Endpoint host: app.daedalmap.com. ARD identifier: urn:air:com.daedalmap:mcp:boundaries.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.