Usgs Earthquakes
NPM · @PIPEWORX/MCP-USGS-EARTHQUAKES · 2 COMPONENTS
USGS Earthquake Catalog MCP (FDSNWS event API).
Available components
Last scanned (13 hours ago)
Scores higher than 70% of npm servers
Category Maps and Location
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-usgs-earthquakes). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability58
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1298 tokens (~432/item across 3 items; 3 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 Management30
- Stability observed for 9 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 +4
- Stability: unverified → 0.27 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 29 Oct 26 78
First indexed and scored.
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 7 Nov 2026 · Analysed npm/@pipeworx/mcp-usgs-earthquakes@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-usgs-earthquakes |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-usgs-earthquakes/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3706467430 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:156201de0f54c18c9105893e517c761af825a3ffdf4db83a2dde2648a1c9f4db2f67346328eb7e05422f7c56095d0ddf6a704559cf85c2f497fe3b716 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
count_earthquakes ~518
Count earthquakes matching a filter without returning the events — fast for questions like "how many M5+ quakes in the last 7 days near X". Same filters as search_earthquakes (time, magnitude, circular area); for "last N days/hours" questions pass `days`/`hours` rather than computing start_time yourself. The response echoes the exact start_time/end_time and magnitude filter actually queried, ahead of the count itself. Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Trailing window length in days, measured back from the exact current time (e.g. days: 7 for "the last 7 days"). Use this instead of computing a start_time for relative-window questions — it is the on… |
| end_time | string | – | ISO date/time upper bound, e.g. "2026-06-09". A bare date is treated as 00:00:00 UTC that day. Defaults to now. |
| hours | number | – | Trailing window length in hours, measured back from the exact current time (e.g. hours: 168 for "the past 168 hours"). Same precedence as `days` (ignored if start_time/end_time given); takes priority… |
| latitude | number | – | Center latitude for a circular search. |
| longitude | number | – | Center longitude for a circular search. |
| max_magnitude | number | – | Maximum magnitude. |
| max_radius_km | number | – | Search radius in km around latitude/longitude. |
| min_magnitude | number | – | Minimum magnitude (e.g. 5 for M5+). |
| start_time | string | – | ISO date/time lower bound, e.g. "2026-06-01" or "2026-06-01T00:00:00". A bare date (no time) is treated as 00:00:00 UTC that day. If given, this (with end_time) takes precedence over `days`/`hours`,… |
No output schema declared.
No examples provided.
get_earthquake ~92
Get full detail for a single earthquake by its USGS event id (e.g. "us7000n7n8"). Returns magnitude, location, time, depth, felt reports, tsunami flag, PAGER alert level, status, contributing networks, and detail URLs. Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | USGS event id, e.g. "us7000n7n8". |
No output schema declared.
No examples provided.
search_earthquakes ~630
Search the USGS earthquake catalog (FDSNWS event API) for real-time and historical seismic events. Filter by time window, magnitude, depth, and a circular geographic area. For "last N days/hours" questions pass `days`/`hours` rather than computing start_time yourself. Returns a compact list of quakes with magnitude, location, time, coordinates, depth, and significance, plus the exact start_time/end_time and magnitude filter actually queried. Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Trailing window length in days, measured back from the exact current time (e.g. days: 7 for "the last 7 days"). Use this instead of computing a start_time for relative-window questions — it is the on… |
| end_time | string | – | ISO date/time upper bound, e.g. "2026-06-09". A bare date is treated as 00:00:00 UTC that day. Defaults to now. |
| hours | number | – | Trailing window length in hours, measured back from the exact current time (e.g. hours: 168 for "the past 168 hours"). Same precedence as `days` (ignored if start_time/end_time given); takes priority… |
| latitude | number | – | Center latitude for a circular search (use with longitude + max_radius_km). |
| limit | number | – | Max events to return (default 20, max 100). |
| longitude | number | – | Center longitude for a circular search (use with latitude + max_radius_km). |
| max_depth_km | number | – | Maximum hypocenter depth in km. |
| max_magnitude | number | – | Maximum magnitude. |
| max_radius_km | number | – | Search radius in km around latitude/longitude. |
| min_depth_km | number | – | Minimum hypocenter depth in km. |
| min_magnitude | number | – | Minimum magnitude (e.g. 5 for M5+). |
| order_by | string | – | Sort order: "time" (newest first, default), "magnitude" (largest first), "time-asc", or "magnitude-asc". |
| start_time | string | – | ISO date/time lower bound, e.g. "2026-06-01" or "2026-06-01T00:00:00". A bare date (no time) is treated as 00:00:00 UTC that day. If given, this (with end_time) takes precedence over `days`/`hours`,… |
No output schema declared.
No examples provided.
How do I install the Usgs Earthquakes MCP server?
Usgs Earthquakes runs locally as an npm package, launched with npx -y @pipeworx/mcp-usgs-earthquakes. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-usgs-earthquakes
claude mcp add pipeworx-io-usgs-earthquakes -- npx -y @pipeworx/mcp-usgs-earthquakes
What is the Usgs Earthquakes MCP server?
Usgs Earthquakes is an MCP server listed in the public MCP registry as io.github.pipeworx-io/usgs-earthquakes. USGS Earthquake Catalog MCP (FDSNWS event API). This page covers its npm package (@pipeworx/mcp-usgs-earthquakes).
Is the Usgs Earthquakes MCP server safe to use?
Usgs Earthquakes scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 7 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Usgs Earthquakes MCP server expose?
Usgs Earthquakes exposes 3 tools: search_earthquakes, get_earthquake, count_earthquakes. Their descriptions and schemas cost roughly 1,240 tokens of context every time the server is loaded.
Is the Usgs Earthquakes MCP server still maintained?
Usgs Earthquakes is still listed as active in the MCP registry. We last reached this channel on 7 November 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 Usgs Earthquakes MCP server under?
Usgs Earthquakes declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Usgs Earthquakes MCP server?
VerifyMCP ran 16 checks on Usgs Earthquakes, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.