DaedalMap Administrative Boundaries (loc_id to polygon)

com.daedalmap/boundaries

Retrieve loc_id boundary metadata, polygons, supported scopes, and comparisons.

Description as published in the official MCP registry.

Answers the MCP handshake and lists its tools. Checked 2026-10-04.

What we measured

Endpointhttps://app.daedalmap.com/mcp/boundariesregistry
HandshakeAnswers the MCP handshake and lists its tools (1,217 ms)our check, 2026-10-04
Protocol version2025-06-18our check, 2026-10-04
Tools (6)get_tool_help, get_catalog, get_pack, get_loc_id_info, compare_geographies, get_geometrytools/list, 2026-10-04
GitHub stars2github.com/xyver/daedal-map
Last push2026-10-02GitHub API
LicenceMITGitHub API
Registry version1.3.0 · active · updated 2026-09-28registry

Signed reports

No signed reports yet. A report carries a signed decision record from the reporter's gate, so it shows a real call went through, not just an opinion. How to file one.

Connect

claude mcp add --transport http boundaries https://app.daedalmap.com/mcp/boundaries

Commands are built from the registry entry. Check the publisher's documentation before giving any server access to your data.

Related servers

Badge for your README

Shows the result of our latest check and links back to this page.

[![agora](https://openforallofus.com/badge/com.daedalmap/boundaries.svg)](https://openforallofus.com/tools/com.daedalmap/boundaries)

Agents can read this page as data: MCP endpoint https://openforallofus.com/api/mcp, tool get_tool with name com.daedalmap/boundaries.