earthquake-mcp-server
Real-time earthquake data and seismic monitoring for AI agents via the USGS Earthquake Catalog API. No API key required — all data is open and free.
Features
- Real-time data from the USGS Earthquake Hazards Program
- No API key needed — fully open data
- Global coverage — all earthquakes worldwide
- Tsunami warnings, felt reports, and PAGER alert levels
- Magnitude filtering, date ranges, and radius search
- Historical data going back decades
Tools
| Tool | Description |
|---|---|
tool_get_recent_earthquakes |
Recent earthquakes (last N hours), filtered by magnitude |
tool_search_earthquakes |
Search by date range and magnitude |
tool_get_significant_earthquakes |
Major earthquakes (M5.0+) sorted by magnitude |
tool_earthquakes_near_location |
Earthquakes within a radius of lat/lon coordinates |
tool_get_seismic_summary |
24h global seismic activity summary with statistics |
tool_get_earthquake_count |
Count earthquakes in a time range |
tool_get_largest_earthquakes |
Top N largest earthquakes in the last N years |
tool_get_magnitude_info |
Educational: Moment Magnitude Scale explained |
Installation
pip install earthquake-mcp-server
Usage with Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"earthquake": {
"command": "earthquake-mcp-server"
}
}
}
Example Queries
- "Show me all earthquakes in the last 24 hours with magnitude 4.0+"
- "Were there any significant earthquakes near Japan this week?"
- "What is the seismic activity summary for today?"
- "Find earthquakes near coordinates 35.6°N, 139.7°E (Tokyo) in the last 30 days"
- "What are the 10 largest earthquakes in the last year?"
- "How strong was the strongest earthquake this month?"
Data Source
All data comes from the USGS Earthquake Catalog API, maintained by the U.S. Geological Survey. Data is real-time and updated continuously.
License
MIT License — see LICENSE
Related MCP Servers
- space-mcp-server — NASA space data
- climate-risk-mcp-server — Climate & ESG data
- geospatial-mcp-server — OpenStreetMap & geospatial tools
Metadata
Release files for earthquake-mcp-server 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 | |
|---|---|---|---|---|
| earthquake_mcp_server-0.1.0.tar.gz | 7.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| earthquake_mcp_server-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 16.4 kB
Release files / earthquake_mcp_server-0.1.0.tar.gz
| Download URL | earthquake_mcp_server-0.1.0.tar.gz |
|---|---|
| Size | 7.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c7fa1aa9a811de73d2098ccab60217908d00c46ad397475a20882f57d2282780
|
|
BLAKE2b-256 checksum How to use checksums |
095453dc724ebda8542669772d954f3ceb4c7413c80cb05318f15917b7a65577
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.3
|
Release files / earthquake_mcp_server-0.1.0-py3-none-any.whl
| Download URL | earthquake_mcp_server-0.1.0-py3-none-any.whl |
|---|---|
| Size | 9.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
94fb070717172e4bed2891b43a4a4995e6b4e59c109e652dc99ea62d1f0ca0b5
|
|
BLAKE2b-256 checksum How to use checksums |
95c06c938f9be5462919094dd2b443735bcd12fedbd972fe17c40028c6923fcf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.3
|
Security for earthquake-mcp-server 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.