DaedalMap Earthquake Data
Connect your coding agent to structured historical earthquake events and counts when you build hazard maps, alerts, or resilience features.
Overview
DaedalMap Earthquakes is a Build-phase MCP server for structured historical earthquake events and counts on DaedalMap geography.
What is this MCP server?
- Historical earthquake event data with structured filters
- Paid MCP access for earthquake counts and event rows via x402 USDC on Base
- Country and region lookups tied to DaedalMap loc_id geography
- Per-row pricing with 100 base rows included and documented price cap
- Streamable-http remote at app.daedalmap.com/mcp/earthquakes
- Pricing model per_row, network Base, currency USDC, payment_protocol x402
- per_row_usd 0.0001, base_price_usd 0.01, base_rows_included 100, max_price_usd 0.5
- Registry categories: hazard, geospatial, data
What problem does it solve?
Building earthquake-aware features without a consistent agent-accessible event API forces brittle scrapers and inconsistent country filters.
Who is it for?
Indie devs shipping seismic dashboards, preparedness apps, or research copilots who want metered MCP access to historical earthquake tables.
Skip if: Real-time USGS-style alerting pipelines that need sub-minute feeds rather than DaedalMap historical structured retrieval.
What do I get? / Deliverables
Once the earthquakes MCP remote is registered, your agent can fetch filtered historical event rows and counts with loc_id-aligned geography.
- Filtered historical earthquake event datasets via MCP tool calls
- Earthquake count queries for dashboards and agent summaries
- Geography-scoped results using DaedalMap loc_id conventions
Recommended MCP Servers
Journey fit
Earthquake MCP tools are installed while wiring backend and agent data paths, not as a substitute for production monitoring on Operate. Integrations is the right shelf because the server exposes paid row retrieval and filters through a remote MCP endpoint during development.
How it compares
Specialized earthquake data MCP lane, not a general-purpose mapping SDK or offline CSV skill.
Common Questions / FAQ
Who is com.daedalmap/earthquakes for?
Solo builders and small teams using MCP agents to add historical earthquake datasets to apps, maps, or internal analytics.
When should I use com.daedalmap/earthquakes?
Use it during Build integrations when you need filtered earthquake history and counts and want pricing scoped to earthquake rows only.
How do I add com.daedalmap/earthquakes to my agent?
Configure https://app.daedalmap.com/mcp/earthquakes as a streamable-http MCP remote, then enable x402 USDC on Base for paid row retrieval beyond included rows.