Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

DaedalMap Administrative Boundaries (loc_id to polygon)

REMOTE · APP.DAEDALMAP.COM · SCANNED SEP 20

Retrieve loc_id boundary metadata, polygons, scopes, comparisons, and bounded exports.

0 this week 80 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability81
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2617 tokens (~153/item across 17 items; 11 tools + 6 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 88% of tool parameters carry a description.Partial
  • Structured output schemas are declared (27% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the DaedalMap Administrative Boundaries (loc_id to polygon) MCP server?

DaedalMap Administrative Boundaries (loc_id to polygon) is a hosted endpoint at https://app.daedalmap.com/mcp/boundaries, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · app.daedalmap.com

# add to Claude Code
claude mcp add --transport http com-daedalmap-boundaries 'https://app.daedalmap.com/mcp/boundaries'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-daedalmap-boundaries": {
      "url": "https://app.daedalmap.com/mcp/boundaries"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-daedalmap-boundaries": {
      "type": "http",
      "url": "https://app.daedalmap.com/mcp/boundaries"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-daedalmap-boundaries]
url = "https://app.daedalmap.com/mcp/boundaries"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-daedalmap-boundaries": {
      "type": "remote",
      "url": "https://app.daedalmap.com/mcp/boundaries",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-daedalmap-boundaries --url 'https://app.daedalmap.com/mcp/boundaries' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-daedalmap-boundaries:
    url: "https://app.daedalmap.com/mcp/boundaries"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-daedalmap-boundaries": {
      "Transport": "http",
      "Url": "https://app.daedalmap.com/mcp/boundaries"
    }
  }
}
# add to Vellum
assistant mcp add com-daedalmap-boundaries -t streamable-http -u 'https://app.daedalmap.com/mcp/boundaries'
// mcp.json
{
  "mcpServers": {
    "com-daedalmap-boundaries": {
      "type": "http",
      "url": "https://app.daedalmap.com/mcp/boundaries"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_geometry” rewrote its description, which is the text the model reads security
    • “get_geometry” added an optional parameter “detail” cosmetic
    • “get_pack” added an optional parameter “detail” cosmetic
  • 17 Sept 26 +7
    • Judged manipulation: unverified → pass security
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: unverified → excellent functional
  • 16 Sept 26 −7
    • Judged manipulation: pass → unverified security
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: excellent → unverified functional
  • 14 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_catalog” rewrote its description, which is the text the model reads security
    • Tool “get_pack” rewrote its description, which is the text the model reads security
    • Tool “get_tool_help” rewrote its description, which is the text the model reads security
    • Tool “get_catalog” now declares an output schema functional
    • Tool “get_pack” now declares an output schema functional
    • Tool “get_tool_help” now declares an output schema functional
    • First check of Tool coverage: 27 functional
  • 13 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 7 Sept 26 +4
    • Stability: fail → pass security
  • 6 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 5 Sept 26 −4
    • Stability: pass → fail security
    • Tool “check_geometry” rewrote its description, which is the text the model reads security
    • Tool “get_geometry” rewrote its description, which is the text the model reads security
    • Tool “loc_id_info” rewrote its description, which is the text the model reads security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Probed https://app.daedalmap.com/mcp/boundaries

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=app.daedalmap.com CN=YR2,O=Let's Encrypt,C=US 17 Sept 2026 16 Dec 2026 RSA 2048 SHA256-RSA 51023d45112daf6159a4fae4a177632589f
SANs: app.daedalmap.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of app.daedalmap.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
daedalmap.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), microphone=(), camera=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://app.daedalmap.com/mcp/boundaries Verified 200
http (plaintext) http://app.daedalmap.com/mcp/boundaries HTTPS enforced 301 https://app.daedalmap.com/mcp/boundaries
MCP tools · 11 exposed · ~1,906 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_geometry ~157

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. Historical geometry remains the primary result; an evidenced current successor is only an explicit follow-up choice. It does not resolve points or explain other identity relationships. Use before get_geometry or an export. No payment required.

NameTypeReqDescription
batch_idstringOptional caller-supplied batch id for tracing.
loc_idstringDaedalMap loc_id to check for available geometry.
loc_idsarrayDaedalMap loc_ids to check for available geometry. Default public cap is deployment-configurable.
request_idstringOptional caller-supplied request id for tracing.

No output schema declared.

No examples provided.

compare_geographies ~254

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 lookup when the caller asks whether two tiers/releases really contain or overlap one another. A point-chain seam is not proof of strict parentage. Use resolve_reference first for names or outside identifiers. No payment required.

NameTypeReqDescription
as_ofstringISO date or year applied to both identities.
batch_idstringOptional caller-supplied batch id for tracing.
include_successorsbooleanInclude direct successors and present-day descendants for maintained historical identities. Default true.
itemsarrayBounded geography pairs to compare in one call.
left_as_ofstringOptional ISO date or year for the left identity; overrides as_of.
left_loc_idstringFirst DaedalMap loc_id.
request_idstringOptional caller-supplied request id for tracing.
right_as_ofstringOptional ISO date or year for the right identity; overrides as_of.
right_loc_idstringSecond DaedalMap loc_id.

No output schema declared.

No examples provided.

create_geometry_export ~192

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 by deployment. A direct local-runtime loopback caller has no service item cap. Use estimate_geometry_package or get_tool_help for the effective access lane.

NameTypeReqDescription
formatstring
include_polygonboolean
loc_idstring
loc_idsarraySelected loc_ids. The default synchronous limit is 250; larger calls return a typed operational-limit response.
output_namestring
quote_idstringQuote id returned by estimate_geometry_package, when available.
request_idstringOptional caller-supplied request id for tracing.
scopeobject

No output schema declared.

No examples provided.

estimate_geometry_package ~162

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 bundle.

NameTypeReqDescription
formatstringImplemented delivery format. Unsupported format names are rejected rather than silently returning another representation.
include_polygonbooleanEstimate full shapes when true; metadata-only when false.
loc_idstringSingle loc_id to package.
loc_idsarrayExplicit loc_ids to package.
output_namestringOptional safe base filename for the export.
request_idstringOptional caller-supplied request id for tracing.
scopeobject

No output schema declared.

No examples provided.

get_catalog ~33

List the current catalog-published data packs and their access lanes. Start here, then call get_pack for one selected pack.

Input schema present but exposes no named parameters.

NameTypeReqDescription
catalog_versionstring
clarificationobject
errorobject
generated_atstring|null
guidanceobject
next_stepobject
pack_countinteger
packsarray
provenanceobject
reasonstring
request_idstring|null
tool_familiesarray
warningsarray

No examples provided.

get_geometry ~252

Shape retrieval for exact loc_ids. The default lite response returns shape availability, family, vintage, centroid, and bounding box. Set detail='full' for the attached identity metadata block and include_polygon=true only when exact coordinates are needed. It does not explain hierarchy or crosswalks; use loc_id_info for those details. Historical geometry is returned first and successors are never substituted automatically. No payment required.

NameTypeReqDescription
batch_idstringOptional caller-supplied batch id for tracing.
detailstringLite returns shape metadata, bbox, and centroid. Full also includes the attached location-info block.
include_polygonbooleanWhen true, include the full GeoJSON geometry. Default false.
loc_idstringDaedalMap loc_id, such as USA-CA-037, USA-Z-00601, USA-NWSFZ-AKZ317, EEZ-USA, or IHO1953-240001002.
loc_idsarrayDaedalMap loc_ids to fetch in one call. Default public cap is deployment-configurable and lower when include_polygon is true.
request_idstringOptional caller-supplied request id for tracing.

No output schema declared.

No examples provided.

get_job_status ~85

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.

NameTypeReqDescription
job_idstringyesJob id returned by create_geometry_export or create_conversion_job.
request_idstringOptional caller-supplied request id for tracing.

No output schema declared.

No examples provided.

get_pack ~90

Describe one catalog-published pack, including sources, metrics, coverage, freshness, access, and a first query. Call this before querying an unfamiliar pack.

NameTypeReqDescription
detailstringUse lite for normal discovery. Use full only for one selected pack when its complete public metadata is required.
pack_idstringyesPack identifier from get_catalog. Newly catalog-admitted packs require no MCP schema change.
NameTypeReqDescription
clarificationobject
errorobject
guidanceobject
material_policyobject
next_stepobject
pack_idstring
provenanceobject
reasonstring
request_idstring|null
sourcesarray
warningsarray

No examples provided.

get_tool_help ~51

Describe one tool visible on this facade, including its input contract, access limits, refusals, example, outputs, and recommended next calls.

NameTypeReqDescription
tool_namestringyesExact tool name from tools/list.
NameTypeReqDescription
accessobject
clarificationobject
errorobject
examplesarray
guidanceobject
important_output_fieldsarray
input_schemaobject
next_stepobject
okboolean
provenanceobject
purposestring
reasonstring
recommended_next_callsarray
request_idstring|null
titlestring|null
tool_namestring
warningsarray

No examples provided.

loc_id_info ~423

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, and child counts. Historical records are returned as requested; when an evidenced successor exists, supersession separately asks whether the caller wants it and never substitutes or fetches it automatically. Set include_hierarchy for the strict same-release ancestor chain and include_references for external or side-chain crosswalks. This is where detailed chain explanation belongs; resolve_point intentionally stays compact. For exact polygons use get_geometry, and for overlap or successor analysis use compare_geographies. No payment required.

NameTypeReqDescription
batch_idstringOptional caller-supplied batch id for tracing.
include_hierarchybooleanWhen true, include strict stored parent and ancestor data. This never invents a parent edge across mixed releases. Default false.
include_referencesbooleanWhen true, include known external or side-chain references attached to each loc_id. Default false.
iso3stringOptional country hint for crosswalk artifacts. Defaults to the loc_id country when possible.
limit_per_systemintegerMaximum overlap references to return per bridge/system. Default 10.
loc_idstringDaedalMap loc_id, e.g. 'USA-CA'.
loc_idsarrayDaedalMap loc_ids to inspect together, including every loc_id from a resolve_point stack. Default public cap is deployment-configurable.
min_sharenumberOptional minimum target-area share for reverse overlap references.
request_idstringOptional caller-supplied request id for tracing.
systemsarrayOptional reference systems to include when include_references is true, such as zcta, nws_fire, overlay_tribal, or overlay_nws_public_zone.
target_admin_levelAdmin level for crosswalk-backed reverse reference lookup. Inferred when omitted.

No output schema declared.

No examples provided.

resolve_loc_id_scope ~207

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 before shape exports such as every county in a selected parent scope. No natural-language decoding is performed.

NameTypeReqDescription
admin_levelTarget level, such as admin_2, 2, county, or state.
bboxOptional minLon,minLat,maxLon,maxLat filter.
count_onlybooleanWhen true, return counts without loc_id rows.
limitintegerMaximum rows to return inline. Counts are returned even when rows are truncated.
offsetintegerOffset for preview paging.
parent_loc_idstringParent DaedalMap loc_id, such as USA or CAN-BC.
request_idstringOptional caller-supplied request id for tracing.
scopeobject

No output schema declared.

No examples provided.

Common questions

What is the DaedalMap Administrative Boundaries (loc_id to polygon) MCP server?

DaedalMap Administrative Boundaries (loc_id to polygon) is an MCP server listed in the public MCP registry as com.daedalmap/boundaries. Retrieve loc_id boundary metadata, polygons, scopes, comparisons, and bounded exports. This page covers its hosted endpoint (https://app.daedalmap.com/mcp/boundaries).

Is the DaedalMap Administrative Boundaries (loc_id to polygon) MCP server safe to use?

DaedalMap Administrative Boundaries (loc_id to polygon) scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the DaedalMap Administrative Boundaries (loc_id to polygon) MCP server expose?

DaedalMap Administrative Boundaries (loc_id to polygon) exposes 11 tools: get_tool_help, get_catalog, get_pack, loc_id_info, check_geometry, and 6 more. Their descriptions and schemas cost roughly 1,906 tokens of context every time the server is loaded.

Does the DaedalMap Administrative Boundaries (loc_id to polygon) MCP server require authentication?

No. We connected to DaedalMap Administrative Boundaries (loc_id to polygon) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the DaedalMap Administrative Boundaries (loc_id to polygon) MCP server still maintained?

DaedalMap Administrative Boundaries (loc_id to polygon) is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.