seismic-mcp
A unified MCP server that queries 20 seismic agencies in parallel, reconciles cross-agency earthquake reports, and surfaces discrepancies for AI agents.
README
seismic-mcp
<!-- mcp-name: io.github.hoon1983/seismic-mcp -->
A unified Model Context Protocol server for global earthquake data. Queries 20 seismic agencies in parallel; matches cross-agency reports of the same earthquake; 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
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.