seismic-mcp
A unified Model Context Protocol server for global seismic data. Queries 20 seismic agencies in parallel; matches cross-agency reports of the same event; surfaces magnitude and location discrepancies so AI agents can see what one feed alone would hide.
Status
Working:
- 20 agencies wired up. FDSN-event: USGS, EMSC, IRIS, INGV, GeoNet, GFZ, NOA, IPGP, NCEDC, SCEDC, ISC, SED, BMKG, NIEP, RESIF, KNMI, NRCAN. Custom (non-FDSN): JMA (Japan), AFAD (Türkiye), IMO (Iceland).
- Cross-agency reconciliation. Spatiotemporal clustering, prime-report selection (local authority > EMSC for Europe > USGS), discrepancy detection (magnitude/location/depth spread). Reviewed bulletins trump preliminary.
- Seven MCP tools:
find_events,get_event,compare_sources,find_discrepancies,list_recent_by_agency,get_agency_info,list_agencies. - TTL cache (60 s) with in-flight de-dup: repeated queries are sub-100 ms.
- 57 unit tests covering parsers, matching, prime-selection, authorities, reconciliation, and cache.
- HTTP frontend for manual inspection: form + Leaflet map + side-by-side compare drawer.
Not yet built: EMSC eventid mapping (cross-references USGS/EMSC IDs for tighter matching), populated known_aliases.json, multi-region per-event authority (KOERI alongside AFAD for Türkiye).
Safety
Reports earthquake data from multiple seismic agencies for research, journalism, situational awareness, and curiosity. It is NOT an early-warning system. All earthquake reports arrive AFTER shaking has already occurred where it was felt. For earthquake preparedness and emergency response, consult official local authorities (USGS ShakeAlert, JMA Earthquake Early Warning, etc.). Preliminary magnitudes and locations are routinely revised by reporting agencies; never make safety decisions based on a single reading.
Run
As an MCP server (Claude Desktop, VS Code, etc.)
Once published to PyPI, no checkout is needed — uvx fetches and runs it:
uvx seismic-mcp
Add to claude_desktop_config.json — Windows path is %APPDATA%\Claude\claude_desktop_config.json, macOS ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"seismic": {
"command": "uvx",
"args": ["seismic-mcp"]
}
}
}
To run from a local checkout instead (development):
uv sync
uv run python server.py
Restart Claude Desktop. The tools appear under the seismic-mcp server in the tools menu.
As a web frontend (manual inspection)
uv run python web.py
Then open http://127.0.0.1:8765/. Same code paths as the MCP server, just exposed over HTTP with a small UI.
Tests
uv run pytest
Architecture
server.py FastMCP entry point — 7 @mcp.tool functions
web.py FastAPI HTTP wrapper around the same tools
src/
schemas.py Pydantic models: SourceReport, ReconciledEvent, ...
adapters/
base.py SeismicAdapter protocol
fdsn.py Header-aware FDSN-event adapter (handles 17 networks)
afad.py Custom AFAD JSON adapter
jma.py Custom JMA list.json adapter
imo.py Custom IMO GeoJSON adapter
__init__.py Registry: make_adapter(code), supported_agencies()
authorities.py Regional-authority bbox lookup
matching.py Spatiotemporal clustering with mag-scaled thresholds
prime_selection.py Headline-report selection rules
reconcile.py Cluster → ReconciledEvent with spreads
cache.py TTL cache + in-flight de-dup
tools/ One file per MCP tool
data/
agency_metadata.json Per-agency coverage, latency, notes
region_authorities.json Region bboxes → authoritative agency
known_aliases.json (manual fallback for matching, currently {})
tests/ pytest suite — 57 tests, fast (<1s)
static/index.html Single-page UI for the HTTP frontend
Metadata
Release files for seismic-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| seismic_mcp-0.1.0.tar.gz | 42.5 kB | Without provenance | Details for seismic_mcp-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| seismic_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for seismic_mcp-0.1.0-py3-none-any.whl |
Total release size: 79.9 kB
Release files / seismic_mcp-0.1.0.tar.gz
| Download URL | seismic_mcp-0.1.0.tar.gz |
|---|---|
| Size | 42.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d8410564bf9650c11e25c2e61bc3e91cdb47313b0a075d821ce034fe0c2cc89c
|
|
BLAKE2b-256 checksum How to use checksums |
b2cbfbfeab966fabd37ae470180b5706040a7a9b12b421423b8993ff5ee7b7bc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.13 {"installer":{"name":"uv","version":"0.11.13","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / seismic_mcp-0.1.0-py3-none-any.whl
| Download URL | seismic_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 37.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
86436eed7513bd9a4c072d4676ca4b4c5eedf860162ef988c845fd04f3f94353
|
|
BLAKE2b-256 checksum How to use checksums |
c8281a8533888a9bf69c099bea0af136ce06888b8d6c48921e291a15dde4029f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.13 {"installer":{"name":"uv","version":"0.11.13","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":null,"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for seismic-mcp 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.