earthquake-mcp-server
Search USGS and EMSC seismic data for real-time feeds, event queries, and earthquake counts via MCP.
README
<div align="center"> <h1>@cyanheads/earthquake-mcp-server</h1> <p><b>Search USGS and EMSC seismic data — real-time feeds, event queries, and earthquake counts via MCP. STDIO or Streamable HTTP.</b> <div>4 Tools • 2 Resources</div> </p> </div>
<div align="center">
</div>
<div align="center">
</div>
<div align="center">
Public Hosted Server: https://earthquake.caseyjhand.com/mcp
</div>
Tools
4 tools for querying global earthquake data from USGS and EMSC:
| Tool | Description |
|---|---|
earthquake_get_feed |
Fetch a USGS pre-computed real-time earthquake feed by magnitude tier and time window |
earthquake_search |
Search earthquakes by time range, magnitude, depth, location radius, PAGER alert level, or felt reports |
earthquake_count |
Count earthquakes matching filters without fetching full records |
earthquake_get_event |
Fetch complete detail for a specific earthquake by USGS event ID |
earthquake_get_feed
Fetch a USGS pre-computed real-time earthquake feed by magnitude tier and time window.
- CDN-cached by USGS — faster and more available than the FDSN query API
- Five magnitude tiers:
all(microseisms),1.0,2.5,4.5, andsignificant(USGS-curated by magnitude, felt reports, and PAGER impact) - Four time windows:
hour,day,week,month - Returns event list with counts and the source feed URL
- Paged with an opaque
cursor:limitbounds a page (default 100, max 1000),totalCountreports the whole feed, andnextCursorretrieves the rest — the broad tiers run past 10,000 events formonth - The cursor is opaque because these feeds have no upstream paging parameter and USGS regenerates them about once a minute; a numeric offset across two calls would skip or repeat events
- Best for real-time "what's happening now" queries; use
earthquake_searchfor historical or filtered queries
earthquake_search
Search earthquakes by time range, magnitude, depth, location radius, PAGER alert level, or felt reports.
- Dual-source: USGS (global, richer metadata) or EMSC (an independent global catalog from the European-Mediterranean Seismological Centre, for cross-verification anywhere)
- Full FDSN ComCat query API parameters: time range, magnitude, depth, location radius
- USGS-specific filters: PAGER alert level (
green/yellow/orange/red), DYFI felt reports count, significance score, event type - Every event carries its upstream
event_type— USGS spells it out (earthquake,quarry blast,explosion,ice quake), EMSC publishes a code (keknown earthquake,ueunknown event) — and theevent_typefilter narrows to one of them on USGS - Location-based queries: provide
latitude,longitude, andradius_kmtogether - Sort by time (newest first) or magnitude (largest first), ascending or descending
- One call returns at most 20,000 events; page beyond that with
offset, forwarded straight to the upstream FDSNoffsetparameter on both sources offsetcounts from 1, matching both upstream APIs — a capped result carriestotalCountand thenextOffsetto pass on the following call- Use
earthquake_countfirst to gauge result size - USGS-specific filters are not supported by EMSC — when
source=emscthey are dropped and named inignoredFilters, so an unconstrained result set is never mistaken for a filtered one
earthquake_count
Count earthquakes matching filters without fetching full records.
- Lightweight alternative to
earthquake_searchfor statistical queries ("how many M5+ events in 2025?") - Same filter surface as
earthquake_search: time, magnitude, depth, location radius, PAGER, DYFI, significance, event type - A radius over a mining region counts quarry blasts alongside earthquakes — pass
event_type="earthquake"on USGS to exclude them - Returns
exceeds_limitflag when count exceeds 20,000 — signals a full search needs paging - Echoes the effective query back as
queryEcho, including the resolved time window — omittingstart_timecounts only the last 30 days - USGS returns the
max_allowedcap (20,000); EMSC count endpoint does not expose this field (max_allowedwill be null) - USGS-specific filters are dropped and named in
ignoredFilterswhensource=emsc, the same as onearthquake_search
earthquake_get_event
Fetch complete detail for a specific earthquake by USGS event ID.
- Returns the normalized event a search result already carries, plus
detail— a projection of the analysis products only the single-event response holds detailgroups: PAGER alert and report link, ShakeMap peak MMI/PGA/PGV and intensity map, DYFI response count and max CDI, moment-tensor scalar moment and nodal planes, landslide and liquefaction alerts, origin quality (azimuthal gap, station count, location and depth uncertainty), finite-fault rupture length and width- A group is omitted when USGS produced no such product — a small automatic event usually has none, a large reviewed one has most of them
- Event IDs appear in the
idfield ofearthquake_get_feedandearthquake_searchresults (e.g.us6000sznj,hv74966427) - USGS-only — EMSC events have no per-event detail endpoint
Resources
| Type | URI pattern | Description |
|---|---|---|
| Resource | earthquake://feed/{magnitude_tier}/{time_window} |
USGS real-time earthquake feed as injectable context — returns the whole feed, so use the earthquake_get_feed tool for the broad tiers |
| Resource | earthquake://event/{event_id} |
Full USGS earthquake event detail by ID as injectable context, including the same detail product projection as earthquake_get_event |
Features
Built on @cyanheads/mcp-ts-core:
- Declarative tool definitions — single file per tool, framework handles registration and validation
- Unified error handling across all tools
- Pluggable auth (
none,jwt,oauth) - Swappable storage backends:
in-memory,filesystem,Supabase,Cloudflare KV/R2/D1 - Structured logging with optional OpenTelemetry tracing
- Runs locally (stdio/HTTP) or on Cloudflare Workers from the same codebase
Earthquake-specific:
- Two independent global data sources: USGS ComCat (full metadata) and EMSC SeismicPortal (an independent catalog from the European-Mediterranean Seismological Centre, with no PAGER/DYFI/ShakeMap metadata and station coverage densest around Europe and the Mediterranean)
- USGS real-time GeoJSON feeds (CDN-cached, fast availability) plus FDSN event query API
- EMSC FDSN-WS event and count endpoints
- No API key required — both USGS and EMSC are fully public
Agent-friendly output:
- Source attribution on every response (
usgs/emsc) so agents can reason about data provenance exceeds_limitflag on count responses surfaces truncation risk before a full search- Fields a source does not publish come back
null, never as a fabricated zero —tsunamiandstatusare null on EMSC events, and the rendered text says "not published by source" rather than "no tsunami" or "reviewed" source_catalogandauthcarry provenance (which catalog and which authoritative agency produced a solution) so agents can weigh two sources against each other- USGS-only filters dropped for an EMSC query are named in
ignoredFilterson bothearthquake_searchandearthquake_count - An upstream rejection surfaces the service's own explanation (the offending parameter and its accepted format) in the error message, not just a status code; when the service explains nothing, the error says so under its own reason rather than passing the raw upstream body through
event_typetravels with every event, so a quarry blast or explosion is never silently read as an earthquake
Getting started
Public Hosted Instance
A public instance is available at https://earthquake.caseyjhand.com/mcp — no installation required. Point any MCP client at it via Streamable HTTP:
{
"mcpServers": {
"earthquake-mcp-server": {
"type": "streamable-http",
"url": "https://earthquake.caseyjhand.com/mcp"
}
}
}
Self-Hosted / Local
Add the following to your MCP client configuration file.
{
"mcpServers": {
"earthquake-mcp-server": {
"type": "stdio",
"command": "bunx",
"args": ["@cyanheads/earthquake-mcp-server@latest"],
"env": {
"MCP_TRANSPORT_TYPE": "stdio",
"MCP_LOG_LEVEL": "info"
}
}
}
}
Or with npx (no Bun required):
{
"mcpServers": {
"earthquake-mcp-server": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@cyanheads/earthquake-mcp-server@latest"],
"env": {
"MCP_TRANSPORT_TYPE": "stdio",
"MCP_LOG_LEVEL": "info"
}
}
}
}
Or with Docker:
{
"mcpServers": {
"earthquake-mcp-server": {
"type": "stdio",
"command": "docker",
"args": ["run", "-i", "--rm", "-e", "MCP_TRANSPORT_TYPE=stdio", "ghcr.io/cyanheads/earthquake-mcp-server:latest"]
}
}
}
For Streamable HTTP, set the transport and start the server:
MCP_TRANSPORT_TYPE=http MCP_HTTP_PORT=3010 bun run start:http
# Server listens at http://localhost:3010/mcp
Prerequisites
- Bun v1.3.0 or higher.
- No API keys required — USGS and EMSC data is fully public.
Installation
- Clone the repository:
git clone https://github.com/cyanheads/earthquake-mcp-server.git
- Navigate into the directory:
cd earthquake-mcp-server
- Install dependencies:
bun install
Configuration
All configuration is validated at startup via Zod schemas in src/config/server-config.ts. Key environment variables:
| Variable | Description | Default |
|---|---|---|
MCP_TRANSPORT_TYPE |
Transport: stdio or http |
stdio |
MCP_HTTP_PORT |
HTTP server port | 3010 |
MCP_HTTP_ENDPOINT_PATH |
HTTP endpoint path where the MCP server is mounted | /mcp |
MCP_PUBLIC_URL |
Public origin override for TLS-terminating reverse-proxy deployments | none |
MCP_AUTH_MODE |
Authentication: none, jwt, or oauth |
none |
MCP_LOG_LEVEL |
Log level (debug, info, warning, error, etc.) |
info |
MCP_GC_PRESSURE_INTERVAL_MS |
Opt-in Bun-only forced-GC pressure loop (ms). Try 60000 if heap growth is observed under sustained HTTP load. |
0 (disabled) |
LOGS_DIR |
Directory for log files (Node.js only) | <project-root>/logs |
STORAGE_PROVIDER_TYPE |
Storage backend: in-memory, filesystem, supabase, cloudflare-kv/r2/d1 |
in-memory |
USGS_BASE_URL |
USGS API base URL. Override for testing or mirroring. | https://earthquake.usgs.gov |
EMSC_BASE_URL |
EMSC API base URL. Override for testing or mirroring. | https://www.seismicportal.eu |
DEFAULT_LIMIT |
Default result limit for earthquake_search |
100 |
REQUEST_TIMEOUT_MS |
HTTP timeout in milliseconds for upstream API calls | 10000 |
OTEL_ENABLED |
Enable OpenTelemetry | false |
Running the server
Local development
-
Build and run the production version:
# One-time build bun run rebuild # Run the built server bun run start:http # or bun run start:stdio -
Run checks and tests:
bun run devcheck # Lints, formats, type-checks, and more bun run test # Runs the test suite
Project structure
| Directory | Purpose |
|---|---|
src/mcp-server/tools |
Tool definitions (*.tool.ts). Four tools across USGS and EMSC. |
src/mcp-server/resources |
Resource definitions. Feed and event resources. |
src/services/usgs |
USGS ComCat service — GeoJSON feed fetcher and FDSN query API client. |
src/services/emsc |
EMSC SeismicPortal service — FDSN event search and count endpoints. |
src/config |
Server-specific environment variable parsing and validation with Zod. |
tests/ |
Unit and integration tests, mirroring the src/ structure. |
Development guide
See CLAUDE.md for development guidelines and architectural rules. The short version:
- Handlers throw, framework catches — no
try/catchin tool logic - Use
ctx.logfor logging,ctx.statefor storage - Register new tools and resources in the
createApp()arrays
Contributing
Issues and pull requests are welcome. Run checks and tests before submitting:
bun run devcheck
bun run test
License
This project is licensed under the Apache 2.0 License. See the LICENSE file for details.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.