io.github.cyanheads/earthquake-mcp-server
https://earthquake.caseyjhand.com/mcpSearch USGS and EMSC seismic data — real-time feeds, event queries, and earthquake counts.
What we measured
Over the last 30 days we probed this MCP server 30 times on 30 days; it answered 30 (100%). Median response 275 ms, 95th percentile 328 ms.
When we called tools/list it returned 4 tools, including earthquake_get_feed, earthquake_search_events, earthquake_get_event, over MCP protocol revision 2025-11-25.
Among the 53,642 reachable MCP servers in our snapshot of 2026-11-13 01:12 UTC, it is faster than 58% and higher on readiness than 80%.
From agent-tools.cloud's own probes, last checked 2026-11-12. How we measure
Tools (4)
As returned by the server's own tools/list when we called it.
- 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…
- 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_typ…
- 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…
- 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. q…
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. For x402 and A2A listings it contributes up to 15 of the 100 quality points; for MCP listings it is shown for reference only. Search order and leaderboards use the separate quality grade (here A, 96.1/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 25/25 | Endpoint answers the MCP initialize handshake (306 ms). |
| Protocol revision | 8/10 | Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 30/30 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 4 tool(s) with descriptions. |
| Verified identity | 7/10 | Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time). |
| Freshness + modern flags | 2/5 | seen within 30 days. |
| Auth declaration | 0/5 | How to authenticate is not stated. |
Compared with peers
Against 53,642 reachable MCP servers in our daily snapshot (2026-11-13 01:12 UTC). Display only; it does not change search order.
- Readiness
- Higher than 80% of peers
- This listing 86 · peer median 81
- Latency
- Faster than 58% of peers
- This listing 271 ms · peer median 349 ms
Where it loses the most points, and how to win them back
- Auth declaration −5
— State how to authenticate (an auth scheme, or that none is needed).
Now: How to authenticate is not stated.
- Verified identity −3
— Claim the listing and prove control of its domain.
Now: Namespace verified by the official MCP Registry (GitHub or DNS proof at publish time).
- Freshness + modern flags −3
— Keep the listing current in the registry or source it comes from.
Now: seen within 30 days.
Adoption signals
Public signals from outside this directory, shown for context. They do not change search order or grades.
Listed in
Directories this entry was found in.
How to connect
https://earthquake.caseyjhand.com/mcpcurl -X POST https://earthquake.caseyjhand.com/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'