mcpbeat

DaedalMap Geocoding and Reverse Geocoding (loc_id) MCP Server

com.daedalmap/geocoding
answering

DaedalMap Geocoding and Reverse Geocoding (loc_id) is answering right now. Last checked 6 min ago. It exposes 13 tools. Last commit 4 Aug 2026.

Reverse geocode latitude/longitude to loc_id; resolve loc_ids to boundaries, centroids, hierarchy.

Uptime history 40 hours of history · worst hour 50%
40 hours agonow
95.6%
Uptime 24h
87 of 91 checks
13
Tools
read from the server
374 ms
Response time
average over 24h
2
Stars
last commit 4 Aug 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 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 13

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

loc
loc_id_hierarchy
Free geography utility. Returns the administrative hierarchy around a DaedalMap loc_id: its parent and full ancestor chain up to the country, plus a summary of its children by level. Use this to walk up or down the loc_id spine and clip to any administrative level. No payment required.
loc_id_info
Free geography utility. Returns descriptive metadata for a DaedalMap loc_id: name, admin level, parent, centroid, bounding box, and child counts by level. No payment required.
loc_id_references
Free geography utility. Returns known external or adjacent references for a DaedalMap loc_id, including local/geometry ids and catalog-backed side-chain overlaps such as ZCTAs, tribal areas, NWS public zones, and NWS fire weather zones. Use this when you already have a loc_id and need its equivalent or overlapping identifiers in other systems. No payment required.
resolve
resolve_point
Free geography utility (reverse geocoding). Converts a latitude/longitude into the DaedalMap loc_id administrative chain - the deepest available level plus its parents - so you can join any spatial data to the same loc_id spine the data packs use. Returns the matched country, the deepest resolved loc_id, and the full admin-level stack so you can clip to any level. No payment required.
resolve_reference
Free geography utility. Converts a value 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. No payment required.
admin
admin_to_sidechain
Compatibility geography utility. Prefer loc_id_references or convert_reference for new workflows. Converts a canonical administrative loc_id to overlapping side-chain shapes such as Census ZCTAs, tribal areas, NWS public forecast zones, or NWS fire weather zones using measured polygon overlap. No payment required.
boundary
get_boundary
Free geography utility. Returns the geographic extent of a DaedalMap loc_id: its bounding box and centroid by default, and the full boundary polygon when include_polygon is true. Use the bbox to clip or index your own grid/raster data against DaedalMap administrative areas; request the polygon only when you need the exact perimeter (it can be large). No payment required.
catalog
get_catalog
Free discovery. Returns the list of live agent-ready data packs available on DaedalMap.
convert
convert_reference
Free geography utility. Converts 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 reference bridge. No payment required.
geometry
get_geometry
Free geography utility. Returns reusable geometry metadata for a DaedalMap loc_id: name, family, admin level, centroid, bounding box, and optional full GeoJSON polygon. Prefer bbox/centroid unless you need exact rendering or clipping. No payment required.
pack
get_pack
Free discovery. Returns detailed metadata, coverage, freshness, preferred canonical tool guidance, and first-query examples for one pack. Call this before querying a new pack so you can see time shape, coverage limits, and the paste-ready first query.
reference
list_reference_systems
Free geography utility. Lists the currently exchangeable geographic reference systems in DaedalMap, including catalog-backed geometry families, bridge artifacts, row counts, vintages, target levels, and source license metadata. Call this first when you need to know whether ZIP/ZCTA, NWS zones, tribal areas, marine ids, NUTS-style regional ids, or other systems can be exchanged through loc_id. No payment required.
sidechain
sidechain_to_admin
Compatibility geography utility. Prefer resolve_reference for new workflows. Converts a side-chain geometry such as a Census ZCTA, tribal area, NWS public forecast zone, or NWS fire weather zone to a target administrative level using measured polygon overlap. No payment required.

Endpoints

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

DaedalMap Geocoding and Reverse Geocoding (loc_id) — questions

Answers built from our own checks of this server.

What can DaedalMap Geocoding and Reverse Geocoding (loc_id) do?
It exposes 13 tools, read directly from the server on our last check. Among them: admin_to_sidechain, convert_reference, get_boundary, get_catalog, get_geometry, get_pack and 7 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 Geocoding and Reverse Geocoding (loc_id) mostly used for?
Its tools cluster around loc and resolve. 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 Geocoding and Reverse Geocoding (loc_id) working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 87 of 91 checks got a reply (95.6%), average response time 374 ms. The bar chart above shows every period we have measured.
How do I connect DaedalMap Geocoding and Reverse Geocoding (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 Geocoding and Reverse Geocoding (loc_id) need an API key?
No. DaedalMap Geocoding and Reverse Geocoding (loc_id) completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 13 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is DaedalMap Geocoding and Reverse Geocoding (loc_id)?
It answers our handshake in 374 ms on average, which is faster than 37% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is DaedalMap Geocoding and Reverse Geocoding (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.