DaedalMap Administrative Boundaries (loc_id to polygon)

Name: DaedalMap Administrative Boundaries (loc_id to polygon)
Author: com.daedalmap

MCP serverMCP

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

Until 2026-09-27 this record combined several servers published from one repository. The others now have records of their own: DaedalMap Historical FX Rates, DaedalMap Tsunami Data, DaedalMap Volcanic Activity, DaedalMap Disaster and Geospatial Data, DaedalMap Distributed Manufacturing Locations, DaedalMap Earthquake Data, DaedalMap Population Estimates, DaedalMap UN Sustainable Development Goals, DaedalMap Wildfire Events, DaedalMap World Development Indicators, DaedalMap CIA World Factbook, DaedalMap Flood Events, DaedalMap Geography Tools (loc_id), DaedalMap Hurricane and Tropical Cyclone Data, DaedalMap Reverse Geocoding (coordinates to loc_id), DaedalMap Tornado Events. Checks from before that date include them.

by com.daedalmaprepository ↗homepage ↗v1.3.2

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"daedalmap-administrative-boundaries-loc-id-to-po","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability156/159 checks ok

when	check	result	http	latency	detail
5 h ago	mcp initialize	ok	200	99 ms	server com.daedalmap/boundaries 1.3.2 · protocol 2025-06-18 · 7 tools
12 h ago	mcp initialize	ok	200	100 ms	server com.daedalmap/boundaries 1.3.2 · protocol 2025-06-18 · 7 tools
20 h ago	mcp initialize	ok	200	113 ms	server com.daedalmap/boundaries 1.3.2 · protocol 2025-06-18 · 7 tools
27 h ago	mcp initialize	ok	200	103 ms	server com.daedalmap/boundaries 1.3.2 · protocol 2025-06-18 · 7 tools
34 h ago	mcp initialize	ok	200	125 ms	server com.daedalmap/boundaries 1.3.2 · protocol 2025-06-18 · 7 tools
2 d ago	mcp initialize	ok	200	102 ms	server com.daedalmap/boundaries 1.3.2 · protocol 2025-06-18 · 7 tools
2 d ago	mcp initialize	ok	200	102 ms	server com.daedalmap/boundaries 1.3.2 · protocol 2025-06-18 · 7 tools
2 d ago	mcp initialize	ok	200	117 ms	server com.daedalmap/boundaries 1.3.2 · protocol 2025-06-18 · 7 tools
3 d ago	mcp initialize	ok	200	141 ms	server com.daedalmap/boundaries 1.3.2 · protocol 2025-06-18 · 7 tools
3 d ago	mcp initialize	ok	200	159 ms	server com.daedalmap/boundaries 1.3.2 · protocol 2025-06-18 · 7 tools

Tools observed via MCP handshake

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_pack for data or get_
get_pack — Inspect one exact data pack ID for its metrics, time coverage, and query metadata before get_data.
get_geography — Inspect one published geometry family across scopes or one scope across families. Returns coverage and known editions from catalog metadata only. Optional year
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, with family, direction,
compare_geographies — Compare two known loc_ids using selected reference-graph identity and direct relationship evidence. Verified Admin ancestry can prove containment; a typed graph
get_shape — Shape lookup for exact existing loc_ids only. The default returns shape availability, centroid, and bounding box; include_polygon=true adds GeoJSON coordinates.

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registrycom.daedalmap/boundaries

first seen 2 mo ago · fetched 23 h agoopen ↗

Field history (12 recent events)

20 d ago · declared · version → "1.3.2"
26 d ago · declared · version → "1.3.0"
1 mo ago · declared · description → "Retrieve loc_id boundary metadata, polygons, supported scopes, and comparisons."
1 mo ago · declared · summary → "Retrieve loc_id boundary metadata, polygons, supported scopes, and comparisons."
1 mo ago · declared · version → "1.2.0"
1 mo ago · declared · description → "Retrieve loc_id boundary metadata, polygons, scopes, comparisons, and bounded exports."
1 mo ago · declared · name → "DaedalMap Administrative Boundaries (loc_id to polygon)"
1 mo ago · declared · version → "1.0.4"
1 mo ago · declared · summary → "Retrieve loc_id boundary metadata, polygons, scopes, comparisons, and bounded exports."
1 mo ago · declared · summary → "World Bank World Development Indicators: curated country-year economy, health, education and more."
1 mo ago · declared · description → "World Bank World Development Indicators: curated country-year economy, health, education and more."
1 mo ago · declared · version → "1.0.1"

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from