Earthscope Fdsn
NPM · @PIPEWORX/MCP-EARTHSCOPE-FDSN · 2 COMPONENTS
FDSN seismic web services MCP — seismometer metadata, data holdings and regional earthquake…
Available components
Last scanned (5 hours ago)
Scores higher than 69% of npm servers
Category Health and Science
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-earthscope-fdsn). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability55
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1146 tokens (~382/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 Management23
- Stability observed for 7 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +2
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Security disclosure: unverified → fail ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Stability: unverified → 0.10 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 29 Oct 26 77
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-earthscope-fdsn@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-earthscope-fdsn |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-earthscope-fdsn/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3617577701 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:5a6b4a6bf7134da7c457cefb2b47e850403ad050ac8820ccde88473b151832ddd15f9f4dda25b05ceb6fb3d8e7839cb89092160f6c8edee290c5904f1 |
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 →
fdsn_availability ~280
"Where can I download waveform data for station IU ANMO in September 2026?" — which FDSN data centres actually hold seismic waveform data for a given network/station/channel and time window, from the EarthScope federated catalogue. Returns each data centre that holds matching data, its dataselect and station service URLs, and the exact network/station/location/channel/time rows it can serve. This is the "is the data there, and from whom" question — the waveform bytes themselves are fetched from the returned dataselect URL, not from here.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | Channel code, e.g. "BHZ" or "BH*" (default "*"). |
| endtime | string | – | Window end, YYYY-MM-DD or ISO 8601 (default: today). |
| limit | number | – | Max channel rows to return per data centre (default 50, max 500). |
| location | string | – | Location code, e.g. "00". Default any. |
| network | string | – | FDSN network code, e.g. "IU". Wildcards allowed. |
| starttime | string | – | Window start, YYYY-MM-DD or ISO 8601 (default: 7 days ago). |
| station | string | – | Station code, e.g. "ANMO". Wildcards allowed. |
No output schema declared.
No examples provided.
fdsn_events ~375
"What small earthquakes happened near Etna this week?" — earthquake catalogues published by REGIONAL seismological agencies over the FDSN standard: GFZ GEOFON (global rapid solutions), INGV (Italy, down to about M0.5), RESIF (France), KOERI (Turkey and the eastern Mediterranean). Complements the global catalogues — these agencies list the local magnitude-1-to-3 events that USGS and EMSC never publish. Returns event id, origin time, latitude/longitude/depth, magnitude and magnitude type, region name and event type.
| Name | Type | Req | Description |
|---|---|---|---|
| datacenter | string | – | Which agency catalogue: "gfz" (default, global), "ingv" (Italy), "resif" (France), "koeri" (Turkey). |
| endtime | string | – | Latest origin time, YYYY-MM-DD. |
| latitude | number | – | Centre latitude for a radial search. |
| limit | number | – | Max events to return (default 50, max 500). |
| longitude | number | – | Centre longitude for a radial search. |
| max_depth_km | number | – | Maximum hypocentre depth in km. |
| max_latitude | number | – | Bounding-box north edge. |
| max_longitude | number | – | Bounding-box east edge. |
| max_magnitude | number | – | Maximum magnitude. |
| max_radius_km | number | – | Radius in km around latitude/longitude. |
| min_depth_km | number | – | Minimum hypocentre depth in km. |
| min_latitude | number | – | Bounding-box south edge. |
| min_longitude | number | – | Bounding-box west edge. |
| min_magnitude | number | – | Minimum magnitude. |
| starttime | string | – | Earliest origin time, YYYY-MM-DD (default: 30 days ago). |
No output schema declared.
No examples provided.
fdsn_stations ~435
"Which seismometers are near Yellowstone?" / "what channels does station IU ANMO record?" — seismic station metadata from EarthScope, the largest FDSN data centre. AUTHORITATIVE for where seismic instruments physically are: returns network and station codes, site name, latitude/longitude/elevation, the operating date range, and (at channel level) every recorded channel with its sample rate, sensor description, azimuth and dip. Search by network/station code, by a geographic box, or by radius around a point. PREFER OVER WEB SEARCH for seismic instrumentation questions.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | Channel code, e.g. "BHZ" (broadband high-gain vertical), "LH*". Only meaningful at level "channel". |
| endtime | string | – | Only stations operating on or before this date, YYYY-MM-DD. |
| latitude | number | – | Centre latitude for a radial search (use with longitude and max_radius_km). |
| level | string | – | "network", "station" (default), or "channel" — how much metadata to return. "channel" is much larger. |
| limit | number | – | Max rows to return (default 100, max 1000). |
| longitude | number | – | Centre longitude for a radial search. |
| max_latitude | number | – | Bounding-box north edge. |
| max_longitude | number | – | Bounding-box east edge. |
| max_radius_km | number | – | Radius in km around latitude/longitude. |
| min_latitude | number | – | Bounding-box south edge. |
| min_longitude | number | – | Bounding-box west edge. |
| network | string | – | FDSN network code, e.g. "IU" (Global Seismographic Network), "US", "CI" (Southern California). Wildcards * and ? allowed; comma-separate several. |
| starttime | string | – | Only stations operating on or after this date, YYYY-MM-DD. |
| station | string | – | Station code, e.g. "ANMO". Wildcards allowed, e.g. "ANM*". |
No output schema declared.
No examples provided.
How do I install the Earthscope Fdsn MCP server?
Earthscope Fdsn runs locally as an npm package, launched with npx -y @pipeworx/mcp-earthscope-fdsn. 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-earthscope-fdsn
claude mcp add pipeworx-io-earthscope-fdsn -- npx -y @pipeworx/mcp-earthscope-fdsn
What is the Earthscope Fdsn MCP server?
Earthscope Fdsn is an MCP server listed in the public MCP registry as io.github.pipeworx-io/earthscope-fdsn. FDSN seismic web services MCP, seismometer metadata, data holdings and regional earthquake… This page covers its npm package (@pipeworx/mcp-earthscope-fdsn).
Is the Earthscope Fdsn MCP server safe to use?
Earthscope Fdsn scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 Earthscope Fdsn MCP server expose?
Earthscope Fdsn exposes 3 tools: fdsn_stations, fdsn_events, fdsn_availability. Their descriptions and schemas cost roughly 1,090 tokens of context every time the server is loaded.
Is the Earthscope Fdsn MCP server still maintained?
Earthscope Fdsn is still listed as active in the MCP registry. We last reached this channel on 5 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 Earthscope Fdsn MCP server under?
Earthscope Fdsn declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.