mcpbeat Sign in

DaedalMap Geography Tools (loc_id) MCP Server

answering

DaedalMap Geography Tools (loc_id) is answering right now. Last checked 11 min ago. It exposes 24 tools. Last commit 17 Sep 2026.

Resolve coordinates and geographic identifiers to loc_id, crosswalks, boundaries, and exports.

Uptime history 47 days of history · worst day 82%
47 days agonow
97.8%
Uptime 24h
89 of 91 checks
24
Tools
read from the server
284 ms
Response time
average over 24h
2
Stars
last commit 17 Sep 2026

What changed 88

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 9 August 2026. No other catalogue keeps this.

16 Sep 6 tool descriptions were rewritten estimate_conversion_job, read_geometry_catalog, resolve_deep_point and 3 more
16 Sep 5 tools changed the parameters they ask for estimate_conversion_job, identify_reference_system, read_geometry_catalog and 2 more
14 Sep 3 tools appeared resolve_deep_point, resolve_deep_points, resolve_points
14 Sep a tool description was rewritten resolve_point
14 Sep a tool changed the parameters it asks for resolve_point
14 Sep a tool changed version
13 Sep 5 tool descriptions were rewritten get_catalog, get_pack, get_tool_help and 2 more
13 Sep a tool changed the parameters it asks for resolve_point
11 Sep a tool appeared identify_dataset_geography
11 Sep a tool changed the parameters it asks for resolve_reference
and 63 more, back to 9 August 2026

DaedalMap Geography Tools (loc_id) does not always answer

Over the last week it answered 96.4% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add geocoding --transport http https://app.daedalmap.com/mcp/geography
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "geocoding": {
      "url": "https://app.daedalmap.com/mcp/geography"
    }
  }
}
~/.codex/config.toml
[mcp_servers.geocoding]
url = "https://app.daedalmap.com/mcp/geography"
.cursor/mcp.json
{
  "mcpServers": {
    "geocoding": {
      "url": "https://app.daedalmap.com/mcp/geography"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "geocoding": {
      "url": "https://app.daedalmap.com/mcp/geography"
    }
  }
}

Available tools 24

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

resolve
resolve_deep_point
Second-pass resolution for one WGS84 coordinate. Supply a shallow_loc_id returned by resolve_point and one canonical family from read_geometry_catalog. family defaults to administrative; shape-backed families use direct bbox-to-exact-shape lookup without crosswalks. For multiple coordinates use resolve_deep_points. Current catalog: The same geography tools work worldwide across a cataloged baseline of 252 geographic entities, reaching up to Admin 2. Where additional country releases are available, the same calls automatically return deeper administrative tiers or maintained reference families. Additional detail is currently available for Australia, Brazil, Canada, France, Germany, Mexico, United Kingdom, United States.
resolve_deep_points
Bulk second-pass resolution for one family. Supply a bounded WGS84 point array, one shared shallow_loc_id scope, and one canonical family. family defaults to administrative; other shape-backed families use direct bbox candidates followed by exact containment without crosswalks. Current catalog: The same geography tools work worldwide across a cataloged baseline of 252 geographic entities, reaching up to Admin 2. Where additional country releases are available, the same calls automatically return deeper administrative tiers or maintained reference families. Additional detail is currently available for Australia, Brazil, Canada, France, Germany, Mexico, United Kingdom, United States.
resolve_loc_id_scope
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.
resolve_point
Compact first-pass reverse geocoding for one WGS84 coordinate. Returns an administrative loc_id chain through Admin 3 without opening deep partitions or side-family shape banks. Use its deepest shallow loc_id with resolve_deep_point for Admin 4-6 or one explicit family. For multiple coordinates use resolve_points. Current catalog: The same geography tools work worldwide across a cataloged baseline of 252 geographic entities, reaching up to Admin 2. Where additional country releases are available, the same calls automatically return deeper administrative tiers or maintained reference families. Additional detail is currently available for Australia, Brazil, Canada, France, Germany, Mexico, United Kingdom, United States.
resolve_points
Bulk first-pass reverse geocoding through Admin 3. Accepts a bounded cross-country WGS84 point array and never opens deep partitions or side-family shape banks. Group results by shallow scope before calling resolve_deep_points once per scope and family. Current catalog: The same geography tools work worldwide across a cataloged baseline of 252 geographic entities, reaching up to Admin 2. Where additional country releases are available, the same calls automatically return deeper administrative tiers or maintained reference families. Additional detail is currently available for Australia, Brazil, Canada, France, Germany, Mexico, United Kingdom, United States.
resolve_reference
Free geography utility. Converts one value, or a bounded list of values, from an external or adjacent geographic reference system into the DaedalMap loc_id universe. Examples: from_system='zip' value='00601'; from_system='nws_fire' value='AKZ317'; from_system='admin_boundary' value='Fairfax County'. Returns ranked loc_id matches with bridge vintage, overlap weights, and provenance where applicable. Historical references are returned as requested; an evidenced successor is a separate optional question and is never substituted automatically. No payment required.
geometry
check_geometry
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.
create_geometry_export
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.
get_geometry
Shape retrieval for exact loc_ids, including loc_ids from any level of a resolve_point chain. Returns the requested geometry metadata, vintage, centroid, bounding box, and optional GeoJSON polygon. Historical geometry is returned first; an evidenced successor appears only as a separate question and is never substituted or fetched automatically. It does not explain hierarchy or crosswalks; use loc_id_info for those details. Prefer bbox/centroid unless exact rendering or clipping requires the polygon. No payment required.
read_geometry_catalog
Free geography discovery. Reads the published DaedalMap geometry catalog projection by default, excluding staged and candidate work. Use view='capabilities' with country_scope to learn the country's available_family_ids; a requested family may validly return no point overlap because family coverage can be partial. Use focused inventory views for banks, crosswalk products, and named objects. A local loopback MCP may set read_wip=true for internal review. No payment required. Current catalog: The same geography tools work worldwide across a cataloged baseline of 252 geographic entities, reaching up to Admin 2. Where additional country releases are available, the same calls automatically return deeper administrative tiers or maintained reference families. Additional detail is currently available for Australia, Brazil, Canada, France, Germany, Mexico, United Kingdom, United States.
estimate
estimate_conversion_job
Free dry-run quote for uploaded or pasted user data conversion. Checks a fixed representative sample of up to 32 supplied rows through the real conversion resolver, then estimates total resolvable rows, output bytes, errors, and charge units. row_count is the full dataset size and is not replaced by the sample size. Conversion execution validates every submitted row and reports structured failures for unmatched keys.
estimate_geometry_package
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.
identify
identify_dataset_geography
Free dataset-orchestration utility. Accepts bounded samples from plausible scalar columns and determines which column contains geography, then identifies its maintained reference system, country, and administrative level. The caller performs only structural parsing and sampling; it must not assign geographic meaning in advance. Returns up to three reviewable bindings at 60% confidence or better, plus a coordinate fallback when present; only an unambiguous result at 80% or better is recommended automatically. No geometry is loaded and no full dataset is retained. No payment required.
identify_reference_system
Free geography utility. Checks a bounded sample of identifiers plus optional dataset/column context against maintained reference indexes and geometry banks. LLM clients must extract identifier values from the user's natural-language request and pass them as strings; do not put the prose question in the arguments, and preserve leading zeros. Use it when a caller is unsure which system or level their keys belong to. It returns one to three interpretations with confidence and preserves ambiguity until the user confirms one by retrying with expected.system. A caller who already knows the system can provide expected on the first call and receive a verified geography_binding directly. It does not convert the full dataset or return polygons. No payment required.
catalog
get_catalog
List the current catalog-published data packs and their access lanes. Start here, then call get_pack for one selected pack.
compare
compare_geographies
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.
conversion
create_conversion_job
Creates a synchronous v0 user-data conversion job with preserved scalar fields and JSON rows, CSV, JSON Lines, or Parquet output. Hosted service default: 7,500 rows, tuned around a 10-20 second response budget. A direct local-runtime loopback caller has no service item cap; local machine resources are the boundary. Identifier deduplication keeps repeated geography keys efficient.
convert
convert_reference
Free geography utility. Converts one reference, or a bounded list of references, from one geographic reference system into another by resolving through DaedalMap loc_id: X -> loc_id -> Y. Use this for workflows like ZIP/ZCTA to NWS fire zones, NWS zone to counties, county to overlapping ZCTAs, or any future catalog-backed crosswalk. No payment required.
how
how_geometry_works
Free starting guide for the DaedalMap geography/geometry MCP. Call this first to learn the durable loc_id, administrative-spine, reference-family, discovery, point-lookup, and bounded-shape concepts. Then read the live geometry catalog for country-specific depths, families, and query guidance, and use get_tool_help for one exact tool. Current catalog: The same geography tools work worldwide across a cataloged baseline of 252 geographic entities, reaching up to Admin 2. Where additional country releases are available, the same calls automatically return deeper administrative tiers or maintained reference families. Additional detail is currently available for Australia, Brazil, Canada, France, Germany, Mexico, United Kingdom, United States.
job
get_job_status
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.
loc
loc_id_info
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.
pack
get_pack
Describe one catalog-published pack, including sources, metrics, coverage, freshness, access, and a first query. Call this before querying an unfamiliar pack.
reference
list_reference_systems
Free geography utility. Reads the canonical crosswalk registry and lists published, callable geographic reference systems, direct crosswalk artifacts, row counts, vintages, target levels, and source license metadata. Pass country_scope whenever the country is known. Call this first to learn whether ZIP/ZCTA, postal, census, electoral, watershed, health, tribal, marine, or other identifiers can be exchanged through loc_id. Public calls never expose WIP or relationship-only records. No payment required.
tool
get_tool_help
Describe one tool visible on this facade, including its input contract, access limits, refusals, example, outputs, and recommended next calls.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

admin_to_sidechain
removed 8 Aug 2026
get_boundary
removed 8 Aug 2026
loc_id_hierarchy
removed 8 Aug 2026
loc_id_references
removed 8 Aug 2026
sidechain_to_admin
removed 8 Aug 2026

Endpoints

URLTransportStateLatencyChecked
https://app.daedalmap.com/mcp/geography streamable-http answering 301 ms 11 min ago

Alternatives to DaedalMap Geography Tools (loc_id)

same job, measured the same way
DaedalMap Reverse Geocoding (coordinates to loc_id)
by daedalmap

Convert WGS84 coordinates to the latest available administrative loc_id chain.

7 tools answering
I
Geepers MCP
by geepers4242

Resolve Geepers physical handles to exact coordinates + navigation for AI agents.

44 installs/wk local only
Opencage Geocoding
by mcparmory

Convert addresses to coordinates and reverse-geocode locations worldwide

246 installs/wk local only
Inpoly
by dadev-inpoly

Resolve coordinates against delivery and coverage polygons (geofences).

answering
Apogeoapi MCP
by apogeoapi

Geographic data API: 250+ countries, 150K+ cities, IP geolocation, 161 live FX rates.

55 installs/wk local only
Bamwor MCP Server
by bamwor-dev

World geographic data for AI agents: 261 countries, 5.2M cities, rankings, and 9 indexes.

35 installs/wk local only
Geodistance
by pipeworx-io

Geographic coordinate math MCP.

39 tools answering
Basin
by getbasin

Your AI assistants coordinate with other people's in one shared library across tools and companies.

answering

DaedalMap Geography Tools (loc_id) — questions

Answers built from our own checks of this server.

What can DaedalMap Geography Tools (loc_id) do?
It exposes 24 tools, read directly from the server on our last check. Among them: check_geometry, compare_geographies, convert_reference, create_conversion_job, create_geometry_export, estimate_conversion_job and 18 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is DaedalMap Geography Tools (loc_id) mostly used for?
Its tools cluster around resolve, geometry and estimate. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is DaedalMap Geography Tools (loc_id) working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 89 of 91 checks got a reply (97.8%), average response time 284 ms. The bar chart above shows every period we have measured.
Did DaedalMap Geography Tools (loc_id) ever remove tools?
Yes. admin_to_sidechain, get_boundary, loc_id_hierarchy, loc_id_references and 1 more are no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.
How do I connect DaedalMap Geography Tools (loc_id)?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does DaedalMap Geography Tools (loc_id) need an API key?
No. DaedalMap Geography Tools (loc_id) completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 24 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is DaedalMap Geography Tools (loc_id)?
It answers our handshake in 284 ms on average, which is faster than 52% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is DaedalMap Geography Tools (loc_id) open source?
Yes — it is published under the MIT licence, written in Python and 2 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.