DaedalMap Administrative Boundaries (loc_id to polygon)
com-daedalmap-boundaries declares 7 capabilities across 7 tools, with 1 critical issue.
Issues
7 of 7 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.
7 of 7 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.
7 of 7 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.
7 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
get_tool_help | read |
declared |
get_catalog | read |
declared |
get_pack | read |
declared |
get_geography | read |
declared |
get_loc_id_info | read |
declared |
compare_geographies | read |
declared |
get_shape | read |
declared |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-11 | 11 | tools/list on https://app.daedalmap.com/mcp/boundaries, published in the official MCP registry as com.daedalmap/boundaries 1.3.2 |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.