@pipeworx/earthscope-fdsn

Connect: https://gateway.pipeworx.io/earthscope-fdsn/mcp · Install: one-click buttons

No MCP client? Skip the connection: POST https://gateway.pipeworx.io/v1/tools/search_packs {"query":"..."} to find a tool below, GET /v1/tools/<name> for its schema, POST the same URL with arguments for the data — see For AI agents.

Tools: 3

Seismic station metadata, federated waveform holdings and regional earthquake catalogues, over the international FDSN web-service standard.

This is the instrument side of seismology, not the global earthquake catalogue — usgs-earthquakes and emsc already cover “what earthquakes happened”. fdsn_events here adds the REGIONAL agency catalogues, which list the local magnitude-1-to-3 seismicity the global catalogues never publish.

Tools

• fdsn_stations(network?, station?, channel?, level?, lat/lon/radius or bbox, …) — where seismometers are, what they record, who operates them, and when.
• fdsn_events(datacenter?, starttime?, min_magnitude?, …) — regional agency earthquake catalogues: gfz (global rapid solutions), ingv (Italy), resif (France), koeri (Turkey).
• fdsn_availability(network, station?, channel?, starttime?, endtime?) — which FDSN data centres hold waveform data for a channel and time window, with each centre’s dataselect URL.

Auth

Keyless.

Data sources

• https://service.earthscope.org/fdsnws/station/1/query — station metadata.
• https://service.earthscope.org/irisws/fedcatalog/1/query — federated holdings.
• https://geofon.gfz.de/fdsnws/event/1/query, https://webservices.ingv.it/fdsnws/event/1/query, https://api.franceseisme.fr/fdsnws/event/1/query, http://www.koeri.boun.edu.tr/services/fdsnws/event/1/query — regional catalogues.

Things the next person would otherwise rediscover (all verified 2026-09-17)

• service.iris.edu 301-redirects to service.earthscope.org. Both work; the old host costs a redirect on every call, so the new one is used directly.
• EarthScope serves only station and dataselect under /fdsnws/. Their event and availability services answer HTTP 404. Availability is behind an EarthScope login — it redirects to a trailing-slash path served by uvicorn with vary: Cookie. That is why fdsn_availability answers from irisws/fedcatalog instead: keyless, and it reports the same holdings question across every federated data centre rather than one.
• nodata=404 makes an empty result indistinguishable from a retired endpoint — both are a bare 404 with an empty body, which is exactly how the retired event service was nearly mistaken for “no earthquakes”. These tools send nodata=204, so an empty result is a 204 and a 404 genuinely means the route is gone.
• Field names differ between level=station and level=channel, and the depth column is spelled Depth/km at one agency and Depth/Km at another, so rows are read by header name with aliases rather than by position.
• fedcatalog answers in its own format=request dialect, not FDSN text: blank-line-separated blocks, each opening with KEY=value service lines and then bare NET STA LOC CHA START END rows.
• FDSN maxradius is in DEGREES of arc, not km. The tools take km and convert (÷ 111.195).

Tools

• fdsn_stations — “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 inst
• fdsn_events — “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, do
• fdsn_availability — “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