io.github.cyanheads/earthquake-mcp-server
NPM · @CYANHEADS/EARTHQUAKE-MCP-SERVER · 2 COMPONENTS · SCANNED SEP 21
Search USGS and EMSC seismic data — real-time feeds, event queries, and earthquake counts.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 16 of 49 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3177 tokens (~794/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the io.github.cyanheads/earthquake-mcp-server server?
io.github.cyanheads/earthquake-mcp-server runs locally as an npm package, launched with npx -y @cyanheads/earthquake-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @cyanheads/earthquake-mcp-server
claude mcp add cyanheads-earthquake-mcp-server -- npx -y @cyanheads/earthquake-mcp-server
{
"mcpServers": {
"cyanheads-earthquake-mcp-server": {
"command": "npx",
"args": [
"-y",
"@cyanheads/earthquake-mcp-server"
]
}
}
} {
"servers": {
"cyanheads-earthquake-mcp-server": {
"command": "npx",
"args": [
"-y",
"@cyanheads/earthquake-mcp-server"
]
}
}
} codex mcp add cyanheads-earthquake-mcp-server -- npx -y @cyanheads/earthquake-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cyanheads-earthquake-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@cyanheads/earthquake-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add cyanheads-earthquake-mcp-server --command npx --arg -y --arg @cyanheads/earthquake-mcp-server
mcp_servers:
cyanheads-earthquake-mcp-server:
command: "npx"
args: ["-y", "@cyanheads/earthquake-mcp-server"] {
"McpServers": {
"cyanheads-earthquake-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@cyanheads/earthquake-mcp-server"
]
}
}
} assistant mcp add cyanheads-earthquake-mcp-server -t stdio -c npx -a -y @cyanheads/earthquake-mcp-server
{
"mcpServers": {
"cyanheads-earthquake-mcp-server": {
"command": "npx",
"args": [
"-y",
"@cyanheads/earthquake-mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −4
- Tool safety: pass → unverified ▼ security
- Stability: 0.80 → unverified ▼ security
- Schema quality: 155 → 794 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 0.3.5 → 0.3.6 functional
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 +1
- Stability: 0.97 → pass security
- 15 Sept 26 +1
- Known CVEs: partial → pass ▲ security
- Dependency health: partial → 0.86 functional
- 14 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 13 Sept 26 −11
- Malware scan: pass → unverified ▼ security
- Known CVEs: pass → partial ▼ security
- Schema quality: 794 → 155 ▲ functional
- Dependency health: 0.86 → partial functional
- Package version: 0.3.4 → 0.3.5 functional
- 12 Sept 26 −3
- Stability: pass → 0.83 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Analysed npm/@cyanheads/earthquake-mcp-server@0.3.6
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 49 packages
| Packages resolved | 49 |
|---|---|
| Stale | 16 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
earthquake_count Count Earthquakes ~1,065
Count 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; queryEcho reports the window and filters the count actually covers. When exceeds_limit is true, the count exceeds 20,000 and a full search would be truncated — narrow filters before fetching. USGS returns the max_allowed cap (20,000); EMSC count endpoint does not return this field (max_allowed will be null). Counts can be scoped to a rectangular study area with min_latitude, max_latitude, min_longitude, and max_longitude — each independently optional. Combining the box with the lat/lon/radius circle intersects the two, counting only events inside both. Both catalogs include non-tectonic records, so a radius over a mining region counts quarry blasts alongside earthquakes — pass event_type="earthquake" on USGS to exclude them. USGS-specific filters (alert_level, event_type, min_felt, min_significance) are not sent when source=emsc — the response names them in ignoredFilters.
| Name | Type | Req | Description |
|---|---|---|---|
| alert_level | string | – | Minimum PAGER alert level. PAGER estimates economic loss and casualties. "green" = minimal impact; "red" = extreme. Only available from USGS. |
| end_time | string | – | End of time range as ISO 8601, in the same forms start_time accepts. Defaults to current time if omitted. |
| event_type | string | – | Filter by upstream event classification, e.g. "earthquake" to exclude quarry blasts and explosions from the count, or "quarry blast" to count only those. Matched verbatim against the USGS catalog, wh… |
| latitude | number | – | Latitude for radius search. Requires longitude and radius_km. |
| longitude | number | – | Longitude for radius search. Requires latitude and radius_km. |
| max_depth_km | number | – | Maximum depth in kilometers. Bounded to the documented -100 to 1000 km catalog envelope. |
| max_latitude | number | – | Northern edge of a bounding-box search, in degrees. |
| max_longitude | number | – | Eastern edge of a bounding-box search, in degrees. |
| max_magnitude | number | – | Maximum magnitude. |
| min_depth_km | number | – | Minimum depth in kilometers. Bounded to the documented -100 to 1000 km catalog envelope. Shallow quakes (0–70 km) typically cause more surface damage than deep quakes (>300 km). |
| min_felt | integer | – | Minimum number of DYFI (Did You Feel It?) reports. Use to count events with confirmed public impact. Only available from USGS. |
| min_latitude | number | – | Southern edge of a bounding-box search, in degrees. Independent of the other three box parameters — supply any of them. Must not exceed max_latitude when both are given. |
| min_longitude | number | – | Western edge of a bounding-box search, in degrees. Range extends beyond ±180 so a box can cross the antimeridian (e.g. min_longitude=170, max_longitude=190) — always keep min_longitude at or below ma… |
| min_magnitude | number | – | Minimum magnitude (Richter or equivalent). M2.5+ is felt by some people; M5+ can cause damage; M7+ is major. |
| min_significance | integer | – | Minimum USGS significance score (0–2000+). Combines magnitude, felt reports, and PAGER estimates. Significant events typically score 600+. Only available from USGS. |
| radius_km | number | – | Search radius in kilometers from the lat/lon point. Max 20001.6, the ceiling USGS enforces — half the Earth's great-circle circumference. Converted to degrees for EMSC (1° ≈ 111.2 km). |
| source | string | – | Data source. Both catalogs are global. "usgs" covers global events with PAGER, DYFI, and ShakeMap metadata. "emsc" is an independent global catalog operated by the European-Mediterranean Seismologica… |
| start_time | string | – | Start of time range as ISO 8601 (e.g. "2026-01-01" or "2026-05-23T00:00:00"). A bare year expands to January 1st and an unpadded month or day is zero-padded, so both sources honor the same window. De… |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Number of events matching the query. |
| error | object | – | Present when the call failed. Absent on success. |
| exceeds_limit | boolean | – | True when count exceeds 20000 — a full earthquake_search would be truncated. For EMSC, evaluated against the known 20000 limit since max_allowed is not returned. Narrow filters to retrieve all matchi… |
| ignoredFilters | array | – | USGS-only filters supplied in the input but not sent upstream because source=emsc does not support them. The count is NOT constrained by these — re-run with source=usgs to apply them. Absent when eve… |
| max_allowed | number|null | – | Maximum events the API would return for a full fetch. 20000 for USGS. Null for EMSC — the EMSC count endpoint does not return this field. |
| queryEcho | object | – | Echo of the effective parameters the count covers, including server-resolved defaults. Read start_time and end_time to know which window the count spans — a filter absent here was not sent upstream. |
| source | string | – | Data source used. |
No examples provided.
earthquake_get_event Get Earthquake Event Detail ~213
Fetch 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, the moment-tensor focal mechanism, landslide and liquefaction alerts, origin quality (azimuthal gap, station count, location uncertainty), and finite-fault rupture dimensions. Products are omitted when USGS produced none — a small automatic event typically has no detail at all, while a large reviewed one has most of it. Event IDs appear in the "id" field of earthquake_get_feed and earthquake_search results. This tool is USGS-only — EMSC events have no per-event detail endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | USGS event ID, e.g. "hv74966427" or "us6000sznj". Found in the "id" field of earthquake_get_feed and earthquake_search results. |
| Name | Type | Req | Description |
|---|---|---|---|
| detail | object | – | Analysis products USGS attached to this event. Absent when the event carries none — that means no product was produced, not that impact was zero. |
| error | object | – | Present when the call failed. Absent on success. |
| event | object | – | Full earthquake event detail. |
No examples provided.
earthquake_get_feed Get USGS Earthquake Feed ~462
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. The cursor is opaque and must be passed back verbatim — unlike earthquake_search, these feeds have no upstream paging parameter and USGS regenerates them about once a minute, so a numeric offset across two calls would skip or repeat events. For historical or filtered queries, use earthquake_search instead.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque token for the next page, taken verbatim from a previous call's nextCursor. Omit for the first page. Do not construct, parse, or edit it — it encodes a position in the feed snapshot and is reje… |
| limit | integer | – | Maximum events to return in this call. Default 100, max 1000. Applies to the first page; later pages carry the page size inside the cursor, so set it on the first call rather than changing it mid-seq… |
| magnitude_tier | string | – | Minimum magnitude threshold for the feed. "all" includes microseisms (M<1). "1.0" is M1.0+. "2.5" is M2.5+. "4.5" is M4.5+. "significant" is a USGS curated selection based on magnitude, felt reports,… |
| time_window | string | – | Time window for the feed. "hour" typically returns 0–10 events; "month" can exceed 10,000 for the "all" tier. Prefer "hour" or "day" for real-time status checks. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Number of events returned in this page, not the whole feed. |
| error | object | – | Present when the call failed. Absent on success. |
| events | array | – | Earthquake events for this page, newest first. |
| feed_url | string | – | Source feed URL. |
| generated_at | string | – | ISO 8601 UTC timestamp when this feed was generated by USGS. |
| nextCursor | string | – | Opaque token to pass back as the cursor input for the next page. Present only when more events remain; absent means this was the last page. |
| notice | string | – | Recovery guidance when the feed contains no events, or how to continue when a page was capped — narrowing the magnitude tier, widening the time window, paging with the cursor, or using earthquake_sea… |
| totalCount | number | – | Number of events in the whole feed, across every page. |
| truncated | boolean | – | True when the feed holds more events than this page returned. nextCursor carries the input for the following page. |
No examples provided.
earthquake_search Search Earthquakes ~1,266
Search 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, provide latitude, longitude, and radius_km together. A rectangular study area is expressed with min_latitude, max_latitude, min_longitude, and max_longitude — each independently optional, so a single edge is a valid constraint. Combining the box with the lat/lon/radius circle intersects the two, returning only events inside both. Both catalogs include non-tectonic records (quarry blasts, explosions) — every event carries its event_type, and event_type="earthquake" filters the rest out on USGS. USGS-specific filters (alert_level, event_type, min_felt, min_significance) are not sent when source=emsc — the response names them in ignoredFilters. Use earthquake_count first to gauge result size before requesting large result sets. A single call returns at most 20,000 events; larger result sets are retrieved by paging with offset, which is passed straight through to the upstream FDSN API. When a result is capped, nextOffset carries the offset for the following page and totalCount the full match count — or countUnavailable reports that the count lookup failed and the total is unknown.
| Name | Type | Req | Description |
|---|---|---|---|
| alert_level | string | – | Minimum PAGER alert level. PAGER estimates economic loss and casualties. "green" = minimal impact; "red" = extreme. Only available from USGS. |
| end_time | string | – | End of time range as ISO 8601, in the same forms start_time accepts. Defaults to current time if omitted. |
| event_type | string | – | Filter by upstream event classification, e.g. "earthquake" to exclude quarry blasts and explosions, or "quarry blast" to see only those. Matched verbatim against the USGS catalog, which accepts any s… |
| latitude | number | – | Latitude for radius search. Requires longitude and radius_km. |
| limit | integer | – | Maximum events to return per call. Default 100. Large limits (>1000) may result in slow responses. Max 20000. Combine with offset to retrieve match sets larger than one call can return. |
| longitude | number | – | Longitude for radius search. Requires latitude and radius_km. |
| max_depth_km | number | – | Maximum depth in kilometers. Bounded to the documented -100 to 1000 km catalog envelope. |
| max_latitude | number | – | Northern edge of a bounding-box search, in degrees. |
| max_longitude | number | – | Eastern edge of a bounding-box search, in degrees. |
| max_magnitude | number | – | Maximum magnitude. |
| min_depth_km | number | – | Minimum depth in kilometers. Bounded to the documented -100 to 1000 km catalog envelope. Shallow quakes (0–70 km) typically cause more surface damage than deep quakes (>300 km). |
| min_felt | integer | – | Minimum number of DYFI (Did You Feel It?) reports. Use to find events with confirmed public impact. Only available from USGS. |
| min_latitude | number | – | Southern edge of a bounding-box search, in degrees. Independent of the other three box parameters — supply any of them. Must not exceed max_latitude when both are given. |
| min_longitude | number | – | Western edge of a bounding-box search, in degrees. Range extends beyond ±180 so a box can cross the antimeridian (e.g. min_longitude=170, max_longitude=190) — always keep min_longitude at or below ma… |
| min_magnitude | number | – | Minimum magnitude (Richter or equivalent). M2.5+ is felt by some people; M5+ can cause damage; M7+ is major. |
| min_significance | integer | – | Minimum USGS significance score (0–2000+). Combines magnitude, felt reports, and PAGER estimates. Significant events typically score 600+. Only available from USGS. |
| offset | integer | – | Index of the first event to return, counting from 1 — offset=1 is the first match (both upstream APIs reject 0). Omit for the first page, then pass the nextOffset value from a capped result to fetch… |
| order_by | string | – | Sort order. "time" returns newest first; "magnitude" returns largest first. |
| radius_km | number | – | Search radius in kilometers from the lat/lon point. 100 km covers a metro region; 500 km covers a large country. Max 20001.6, the ceiling USGS enforces. Converted to degrees for EMSC (1° ≈ 111.2 km). |
| source | string | – | Data source. Both catalogs are global. "usgs" covers global events with PAGER, DYFI, and ShakeMap metadata. "emsc" is an independent global catalog operated by the European-Mediterranean Seismologica… |
| start_time | string | – | Start of time range as ISO 8601 (e.g. "2026-01-01" or "2026-05-23T00:00:00"). A bare year expands to January 1st and an unpadded month or day is zero-padded, so both sources honor the same window. De… |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | Number of events returned. |
| countUnavailable | boolean | – | True when the follow-up total-count query failed, so the total is unknown for this call rather than never requested. The returned events are complete and unaffected; only totalCount is missing. Retry… |
| error | object | – | Present when the call failed. Absent on success. |
| events | array | – | Matching earthquake events. |
| ignoredFilters | array | – | USGS-only filters supplied in the input but not sent upstream because source=emsc does not support them. The result set is NOT constrained by these — re-run with source=usgs to apply them. Absent whe… |
| nextOffset | number | – | Value to pass as the offset input to retrieve the next page, with every other input unchanged. Present only when more events remain; absent means this was the last page. |
| notice | string | – | Recovery guidance when results are empty or capped — how to broaden filters or get the full count. Absent when the result set is non-empty and within the limit. |
| queryEcho | object | – | Echo of the effective parameters sent to the upstream API, including server-resolved defaults. Use to diagnose unexpected or empty results — a filter absent here was not sent upstream. |
| source | string | – | Data source used. |
| totalCount | number | – | Total events matching the query before the limit was applied. Fetched via a follow-up count query when results are truncated at the limit. Absent when results were not capped, and when that follow-up… |
| truncated | boolean | – | True when results were capped by the limit parameter. totalCount carries the full match count when available, and nextOffset the input for the following page. With countUnavailable set the total is u… |
No examples provided.
What is the io.github.cyanheads/earthquake-mcp-server server?
io.github.cyanheads/earthquake-mcp-server is listed in the public MCP registry as io.github.cyanheads/earthquake-mcp-server. Search USGS and EMSC seismic data, real-time feeds, event queries, and earthquake counts. This page covers its npm package (@cyanheads/earthquake-mcp-server).
Is the io.github.cyanheads/earthquake-mcp-server server safe to use?
io.github.cyanheads/earthquake-mcp-server scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.cyanheads/earthquake-mcp-server server expose?
io.github.cyanheads/earthquake-mcp-server exposes 4 tools: earthquake_get_feed, earthquake_search, earthquake_get_event, earthquake_count. Their descriptions and schemas cost roughly 3,006 tokens of context every time the server is loaded.
Is the io.github.cyanheads/earthquake-mcp-server server still maintained?
io.github.cyanheads/earthquake-mcp-server is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.cyanheads/earthquake-mcp-server server under?
io.github.cyanheads/earthquake-mcp-server declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.