DaedalMap Disaster and Geospatial Data

Name: DaedalMap Disaster and Geospatial Data
Author: com.daedalmap

MCP serverMCP

Geospatial MCP server for earthquake, tsunami, volcano, disaster, and FX data queries.

Listed on its own since 2026-09-27. Until then it was part of daedalmap-administrative-boundaries-loc-id-to-po, where its earlier checks remain.

by com.daedalmaprepository ↗homepage ↗v1.0.1

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-disaster-and-geospatial-data","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 availability45/47 checks ok

when	check	result	http	latency	detail
4 h ago	mcp initialize	ok	200	101 ms	server com.daedalmap/county-map 0.4.0 · protocol 2025-06-18 · 13 tools
10 h ago	mcp initialize	ok	200	101 ms	server com.daedalmap/county-map 0.4.0 · protocol 2025-06-18 · 13 tools
16 h ago	mcp initialize	ok	200	101 ms	server com.daedalmap/county-map 0.4.0 · protocol 2025-06-18 · 13 tools
23 h ago	mcp initialize	ok	200	173 ms	server com.daedalmap/county-map 0.4.0 · protocol 2025-06-18 · 13 tools
29 h ago	mcp initialize	ok	200	100 ms	server com.daedalmap/county-map 0.4.0 · protocol 2025-06-18 · 13 tools
35 h ago	mcp initialize	ok	200	109 ms	server com.daedalmap/county-map 0.4.0 · protocol 2025-06-18 · 13 tools
2 d ago	mcp initialize	ok	200	108 ms	server com.daedalmap/county-map 0.4.0 · protocol 2025-06-18 · 13 tools
2 d ago	mcp initialize	ok	200	210 ms	server com.daedalmap/county-map 0.4.0 · protocol 2025-06-18 · 13 tools
2 d ago	mcp initialize	ok	200	109 ms	server com.daedalmap/county-map 0.4.0 · protocol 2025-06-18 · 13 tools
3 d ago	mcp initialize	ok	200	102 ms	server com.daedalmap/county-map 0.4.0 · protocol 2025-06-18 · 13 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 — Discover data packs or geometry families progressively: lite selection, full metric/query inventory, or a raw catalog download URL. Choose one result and call g
get_pack — Inspect one selected data pack or geometry family progressively: lite starter contract, full MCP query metadata, or a raw metadata download URL. Use its next_st
get_event — Retrieve one exact disaster event and explicitly requested relationships, affected places, native observations, or geometry. Use get_data to obtain the stable e
resolve_point — Compact first-pass reverse geocoding for one WGS84 coordinate or a bounded point array. Returns the deepest available administrative loc_id chain: the global ba
resolve_deep_point — Second-pass resolution for one WGS84 coordinate or a bounded point array. Supply one shared shallow_loc_id returned by resolve_point and one canonical family fr
get_loc_id_info — Known-place navigation and enrichment tool: use only when you already have one canonical loc_id or a bounded loc_ids array. It returns identity, strict stored p
identify_dataset_geography — Multi-column dataset classifier: use when you do not yet know which column or latitude/longitude pair represents geography. Pass bounded samples from several na
identify_reference_system — Single-column code-system classifier: use after an identifier column has already been selected, or to inspect one bounded set of like geography codes. Pass only
convert_reference — The single geographic reference converter. Converts one reference, or a bounded list, through DaedalMap loc_id: X -> loc_id -> Y. Omit to_system to enter the lo
compare_geographies — Compare two geographic identities for the public guarantees implemented today: containment/common ancestry and temporal validity for the requested vintages. The
get_geometry — Shape availability and bounded coordinate retrieval only: use when you already have exact loc_ids, or one administrative parent_loc_id plus target admin_level.
get_data — Retrieve rows from one selected published data pack using exact metrics, loc_id-based region filters, time/metric filters, sorting, and a row limit. Disaster ev

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/county-map

first seen 1 mo ago · fetched 20 h agoopen ↗

Field history (7 recent events)

13 d ago · declared · summary → "Geospatial MCP server for earthquake, tsunami, volcano, disaster, and FX data queries."
13 d ago · declared · description → "Geospatial MCP server for earthquake, tsunami, volcano, disaster, and FX data queries."
13 d ago · declared · publisherName → "com.daedalmap"
13 d ago · declared · homepageUrl → "https://www.daedalmap.com"
13 d ago · declared · repoUrl → "https://github.com/xyver/daedal-map"
13 d ago · declared · version → "1.0.1"
13 d ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from