Earthquake Mcp Server
Wire USGS and EMSC earthquake feeds into your agent so you can query events, counts, and real-time seismic data while building geo or alert apps.
Overview
Earthquake MCP is a Build-phase MCP server that lets agents search USGS and EMSC seismic data, including real-time feeds, events, and counts.
What is this MCP server?
- Queries USGS and EMSC seismic catalogs from one MCP server
- Supports real-time feeds plus historical event search and counts
- stdio (Bun/npm) and streamable-http remote at earthquake.caseyjhand.com
- Optional local streamable-http transport on localhost:3010 per package manifest
- MCP_LOG_LEVEL env for debug during feed integration work
- Package version 0.1.9
- npm @cyanheads/earthquake-mcp-server
- Remote https://earthquake.caseyjhand.com/mcp
Community signal: 1 GitHub stars.
What problem does it solve?
You keep re-fetching USGS and EMSC APIs manually when prototyping maps, bots, or datasets in chat.
Who is it for?
Builders adding seismic data to agents, internal tools, or content products who want dual-source USGS/EMSC access in one server.
Skip if: Official emergency alerting, life-safety early warning, or compliance-critical disaster systems that need certified providers and SLAs.
What do I get? / Deliverables
Your agent returns structured earthquake queries and counts through MCP tools while you code the app around them.
- Agent-driven earthquake event queries, feed reads, and count summaries
- Configured stdio or HTTP MCP transport to cyanheads earthquake server
Recommended MCP Servers
Journey fit
Builders adopt this during Build when they need authoritative seismic APIs inside the agent loop rather than hand-curling USGS endpoints. Integrations is the right shelf because the server is a thin MCP bridge to external earthquake data providers, not a full research methodology skill.
How it compares
Public seismic data MCP bridge, not a hosted alerting platform or GIS desktop suite.
Common Questions / FAQ
Who is Earthquake MCP for?
Developers and solo founders building geo apps, research tools, or dashboards who want USGS and EMSC data callable from Claude Code, Cursor, or similar agents.
When should I use Earthquake MCP?
During Build integrations when you need live or historical quake lists, counts, or feed exploration without leaving the agent session.
How do I add Earthquake MCP to my agent?
Add @cyanheads/earthquake-mcp-server to MCP settings with Bun stdio start:stdio, or configure the streamable-http URL from the server manifest.