mcpbeat Sign in

Earthquake MCP Server

answering

Earthquake MCP Server is answering right now. Last checked 1 min ago. 778 installs a week from npm. It exposes 4 tools. Last commit 28 Oct 2026.

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

Installs per day peak 366 · avg 57 · +105% w/w
a month agotoday
Uptime history 91 days of history · worst day 0%
91 days agonow
100.0%
Uptime 24h
92 of 92 checks
4
Tools
read from the server
576 ms
Response time
average over 24h
778
Installs / week
npm and PyPI

What changed 38

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 18 August 2026. No other catalogue keeps this.

28 Oct 3 tool descriptions were rewritten earthquake_get_event, earthquake_get_feed, earthquake_search_events
28 Oct 3 tools changed the parameters they ask for earthquake_get_event, earthquake_get_feed, earthquake_search_events
28 Oct a tool changed version
24 Oct 3 tool descriptions were rewritten earthquake_count_events, earthquake_get_event, earthquake_search_events
24 Oct 3 tools changed the parameters they ask for earthquake_count_events, earthquake_get_event, earthquake_search_events
24 Oct a tool changed version
18 Oct 2 tools appeared earthquake_count_events, earthquake_search_events
18 Oct 2 tool descriptions were rewritten earthquake_get_event, earthquake_get_feed
18 Oct 2 tools disappeared earthquake_count, earthquake_search
18 Oct a tool changed the parameters it asks for earthquake_get_event
and 17 more, back to 18 August 2026

Tools have disappeared from this server

A tool that vanishes takes a piece of your agent with it, and the change arrives silently. Watch this server and every such change lands in your inbox.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

run in your terminal
claude mcp add earthquake-mcp-server --transport http https://earthquake.caseyjhand.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://earthquake.caseyjhand.com/mcp
~/.codex/config.toml
[mcp_servers.earthquake-mcp-server]
url = "https://earthquake.caseyjhand.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "earthquake-mcp-server": {
      "url": "https://earthquake.caseyjhand.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "earthquake-mcp-server": {
      "type": "http",
      "url": "https://earthquake.caseyjhand.com/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

earthquake
earthquake_count_events
Count matches without event records, or size an earthquake_search_events query. Omitting start_time uses 30 days; pass explicit bounds for historical periods. queryEcho reports applied filters/window; ignoredFilters names unsupported EMSC inputs. Circle and independently optional box edges intersect. Both catalogs include non-tectonic events; event_type="earthquake" excludes them on USGS. exceeds_limit marks the 20,000-event single-request threshold, not a retrieval ceiling: search supports offset paging beyond it. max_allowed is 20,000 for USGS, null for EMSC.
earthquake_get_event
Fetch one earthquake by event ID: a USGS ID, or an EMSC ID (an origin date and seven-digit sequence, e.g. "20190706_0000043"). Returns the same normalized event a search result carries. For a USGS event it adds 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, the moment-tensor focal mechanism, landslide and liquefaction alerts, origin quality (azimuthal gap, station count, location uncertainty, depth type), and finite-fault rupture dimensions. Product groups are omitted when no projected field is available — a small automatic event typically carries only origin quality, while a large reviewed one has most of it. Opt into more with include: alternative origin solutions, magnitude solutions, phase arrivals, or the USGS aftershock forecast; a requested group that is not returned is listed in unavailable_includes. EMSC publishes none of these products, so an EMSC event has no detail and lists every requested group as not_published. Event IDs appear in the "id" field of earthquake_get_feed and earthquake_search_events results; a USGS event's associated_ids are also accepted.
earthquake_get_feed
Fetch 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 magnitude, felt reports, and PAGER impact estimates. "hour" returns 0–10 events typically; "month" can exceed 10,000 for the "all" tier, so results are returned a page at a time: count is the page size, totalCount the whole feed, and nextCursor the input for the following page. Each page returns limit events (default 15, at most 1,000), fewer only on the last page. The cursor is opaque and must be passed back verbatim — unlike earthquake_search_events, these feeds retain the first-read generation for up to 15 minutes, subject to capacity eviction and restart. An expired cursor requires a fresh first read. For historical or filtered queries, use earthquake_search_events instead.
earthquake_search_events
Search USGS or independent global EMSC seismic catalogs by time, magnitude, depth, area and source-specific filters. Both include non-tectonic events; event_type="earthquake" excludes them on USGS. Circle and independently optional box edges intersect. Unsupported EMSC filters appear in ignoredFilters. Size queries with earthquake_count_events. Returns limit events per call (at most 1,000), fewer only on the last page. Continue with offset=nextOffset and unchanged filters/order. totalCount is the full match total when known; countUnavailable marks a failed count lookup, so the total is unknown. Paging can retrieve matches beyond 20,000.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

earthquake_count
removed 18 Oct 2026
earthquake_search
removed 18 Oct 2026

Endpoints

URLTransportStateLatencyChecked
https://earthquake.caseyjhand.com/mcp streamable-http answering 509 ms 1 min ago

Alternatives to Earthquake MCP Server

same job, measured the same way
Usgs Earthquakes MCP
by mrfentmen

USGS earthquake feeds and queries.

54 installs/wk local only
Usgs MCP
by mrfentmen

USGS earthquakes: latest quakes and queries by magnitude, count and start time.

553 installs/wk local only
U
USGS Earthquakes
by olyport

Real-time earthquake events from the US Geological Survey

3 tools answering
Agent Data Tools: Everyday data
by nutshell2000

18 tools: weather, time zones, sun and moon, earthquakes, countries. 25 free calls.

18 tools answering
Crustdata
by mhimed-crustdata

Real-time B2B data for agents: search and enrich 1B+ people and 200M+ company profiles.

answering
Mode VC AI Chart Lab: 38 Empirical AI & Venture Charts
by modevc

Search and retrieve time-series data across 38 empirical AI adoption and venture research charts.

3 tools answering
Earthscope Fdsn
by pipeworx-io

FDSN seismic web services MCP — seismometer metadata, data holdings and regional earthquake…

370 installs/wk 47 tools answering
Usgs Earthquakes
by pipeworx-io

USGS Earthquake Catalog MCP (FDSNWS event API).

198 installs/wk 47 tools answering

Earthquake MCP Server — questions

Answers built from our own checks of this server.

What can Earthquake MCP Server do?
It exposes 4 tools, read directly from the server on our last check. Among them: earthquake_count_events, earthquake_get_event, earthquake_get_feed, earthquake_search_events. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Earthquake MCP Server working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 576 ms. The bar chart above shows every period we have measured.
Did Earthquake MCP Server ever remove tools?
Yes. earthquake_count, earthquake_search are no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.
How do I connect Earthquake MCP Server?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Earthquake MCP Server need an API key?
No. Earthquake MCP Server completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Earthquake MCP Server?
It answers our handshake in 576 ms on average, which is faster than 20% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Earthquake MCP Server?
The npm package @cyanheads/earthquake-mcp-server was installed 778 times in the last week. Week over week that is +105%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Earthquake MCP Server open source?
The code is open source: it is published under the Apache-2.0 licence, written in TypeScript, 3 stars on GitHub and 3 open issues. The licence covers the code in the repository, not the hosted service at earthquake.caseyjhand.com, which runs on its operator's own terms.