Categories › Knowledge & Everyday › Maps, travel & weather
Inspect loc_id boundaries, retrieve bounded shapes, and compare places and coverage.
Remote server: your requests and data go to app.daedalmap.com. Claude Code: claude mcp add --transport http daedalmap-administrative-boundaries-loc- https://app.daedalmap.com/mcp/boundaries?registry=mcpregistry · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
get_tool_help — Describe one tool visible on this facade, including its exact contract, or return a bounded workflow overview for one supported topic.get_catalog — Choose data or geometry to list published pack IDs or family and scope IDs. The response includes a complete catalog download URL. Use get_pget_pack — Narrow one data pack before get_data. With only pack_id, lists the pack's sources and their coverage. Add source_id to list that source's meget_geography — Inspect one published geometry family across scopes or one scope across families. Returns coverage and known editions from catalog metadata get_loc_id_info — Look up one known loc_id or a small batch in the selected reference graph. Return its identity and directly recorded loc_id connections, witcompare_geographies — Compare two known loc_ids using selected reference-graph identity and direct relationship evidence. Verified Admin ancestry can prove contaiget_shape — Shape lookup for exact existing loc_ids only. The default returns shape availability, centroid, and bounding box; include_polygon=true adds Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.