quake-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_earthquakesA | Search the USGS earthquake catalog by time range, magnitude range, and location. Location can be a bounding box (min/max latitude and longitude) or a circle (latitude, longitude, and radius_km). Defaults to the past 30 days, all magnitudes, worldwide, newest first. Returns a formatted list with magnitude, place, time, coordinates, depth, and event ids. |
| get_earthquakeA | Get full details for a single earthquake by its USGS event id (e.g. us7000abcd, returned by the search tools). Includes magnitude, location, depth, time, felt reports, intensity, PAGER alert level, tsunami flag, and a link to the USGS event page. |
| recent_significantA | List significant earthquakes from the last N days, worldwide. Uses the USGS significance score (a combination of magnitude, felt reports, and estimated impact), the same threshold as the official USGS significant events feed. |
| count_earthquakesA | Count earthquakes matching a query without returning event details. Useful for questions like 'how many M4+ quakes hit California this year'. Supports the same time, magnitude, and location filters as search_earthquakes. |
| felt_reportsA | Find earthquakes near a location that have 'Did You Feel It' (DYFI) citizen reports. Returns events sorted by time with their felt report counts and maximum reported intensity. Good for 'did anyone feel a quake near San Francisco this week' questions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| feed-significant-day | USGS significant events feed for the past 24 hours. |
| feed-significant-week | USGS significant events feed for the past 7 days. |
| feed-4.5-day | All magnitude 4.5+ earthquakes worldwide in the past 24 hours. |
| feed-4.5-week | All magnitude 4.5+ earthquakes worldwide in the past 7 days. |
| feed-2.5-day | All magnitude 2.5+ earthquakes worldwide in the past 24 hours. |
| feed-1.0-hour | All magnitude 1.0+ earthquakes worldwide in the past hour. |
TDQS
Scored across 5 tools
Each tool targets a distinct query type: counting, searching, single detail, significant lists, and felt reports. No overlap in purpose.
Most names follow a verb_noun pattern (count_earthquakes, get_earthquake, search_earthquakes). 'felt_reports' is a noun phrase and 'recent_significant' is adjective_noun, but overall the pattern is largely consistent and readable.
With 5 tools, the surface is well-scoped for earthquake queries. Each tool earns its place without being overwhelming or sparse.
The set covers search, counts, detail lookup, significant events, and citizen reports. Minor gaps like absence of a nearby quakes tool are mitigated by search-by-location. Overall, it's a complete query surface for USGS earthquake data.