io.github.cyanheads/earthquake-mcp-server

io.github.cyanheads/earthquake-mcp-server · v0.3.8 · other

io.github.cyanheads/earthquake-mcp-server is healthy: it completed an MCP handshake in 2505 ms and exposes 4 tools.

Search USGS and EMSC seismic data — real-time feeds, event queries, and earthquake counts.

Endpoint: https://earthquake.caseyjhand.com/mcp (streamable-http)

Repository · JSON · Add to my inventory

Facts

Users (last 30 days)0
HandshakeHealthy
Auth neededNone
Tool count4
Latency2505 ms
Last checked (UTC)2026-10-15T03:20:54.307Z

Health history

Checked (UTC)StatusLatencyError
2026-10-15T03:20:54.307ZHealthy2505

Tools (4)

earthquake_get_feedFetch a USGS pre-computed real-time earthquake feed by magnitude tier and time window. These feeds are CDN-cached by USGS and faster and more available than the query API — use them for "what's happening now" queries. "all" includes microseisms (M<1); "significant" is a USGS curation based on magnit
earthquake_searchSearch earthquakes by time range, magnitude, depth, location radius, PAGER alert level, or felt reports. Supports USGS (global, richer metadata: PAGER, DYFI, ShakeMap) and EMSC, an independent global catalog operated by the European-Mediterranean Seismological Centre. For location-based queries, pro
earthquake_get_eventFetch detail for a specific earthquake by USGS event ID. Returns the same normalized event a search result carries, plus a projection of the analysis products only the single-event response holds: PAGER impact alert and report link, ShakeMap peak intensity and ground motion, DYFI felt-report totals,
earthquake_countCount earthquakes matching filters without fetching full records. Use for statistical queries ("how many M5+ earthquakes in 2025?") or to gauge result size before calling earthquake_search. Omitting start_time counts only the last 30 days, so pass an explicit range for any period-specific question;