Mmcp.market

DaedalMap Administrative Boundaries (loc_id to polygon) MCP server

by daedalmap.com·com.daedalmap/boundaries·v1.2.0
No reviews yet

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

D45/100grade D
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
D45/100

not scanned yet

Adoption
Growing

2 stars

Reviews

Write one

Nobody has reviewed DaedalMap Administrative Boundaries (loc_id to polygon) yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

DaedalMap Administrative Boundaries (loc_id to polygon) tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Not scanned yet. New registry listings are scanned within a day of import.

Install directly

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

DaedalMap Administrative Boundaries (loc_id to polygon): common questions

Is DaedalMap Administrative Boundaries (loc_id to polygon) MCP server safe?
Not recommended: it is graded D (45/100). Read the DaedalMap Administrative Boundaries (loc_id to polygon) safety report
How do I install DaedalMap Administrative Boundaries (loc_id to polygon)?
It runs remotely at app.daedalmap.com. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.
Does DaedalMap Administrative Boundaries (loc_id to polygon) need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is DaedalMap Administrative Boundaries (loc_id to polygon) maintained?
The last commit was 8 days ago (2026-09-20). The latest release is v1.2.0.
Is DaedalMap Administrative Boundaries (loc_id to polygon) up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.

More from daedalmap.com →