QuakeIndex
REMOTE · QUAKEINDEX.COM
Live USGS earthquake data: latest quakes, quakes near a US place, and was that an earthquake?
Available components
Last scanned (16 hours ago)
Scores higher than 67% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1412 tokens (~235/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 61% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Nov 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://quakeindex.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=quakeindex.com | CN=YE1,O=Let's Encrypt,C=US | 26 Sept 2026 | 25 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6715c95e4763b5af3b97581ae25d2a9bf67 |
| SANs: *.quakeindex.com, quakeindex.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of quakeindex.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| quakeindex.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| content-security-policy | frame-ancestors 'self' |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://quakeindex.com/mcp | Verified | 200 | |
| http (plaintext) | http://quakeindex.com/mcp | HTTPS enforced | 301 | https://quakeindex.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
earthquake_details Earthquake details and revisions ~159
Everything QuakeIndex holds about one earthquake by USGS event id (or a QuakeIndex/USGS event URL), including every revision it observed — e.g. 'magnitude revised from 4.1 to 3.9'. An automatic solution is a first estimate and says so. Data: USGS, as held by QuakeIndex. Each result includes its source, when the data was last confirmed, and links to the QuakeIndex and USGS event pages. No predictions and no warnings: results name ShakeAlert and MyShake as the sources of earthquake early warning.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | USGS event id, e.g. 'ci41234567', or a QuakeIndex or USGS event page URL. |
No output schema declared.
No examples provided.
earthquakes_near Earthquakes near a place ~226
Earthquakes within a radius of coordinates, a US ZIP code or a US town, over the last 1-365 days, newest first, each with its distance, plus the largest in the window. Data: USGS, as held by QuakeIndex. Each result includes its source, when the data was last confirmed, and links to the QuakeIndex and USGS event pages. No predictions and no warnings: results name ShakeAlert and MyShake as the sources of earthquake early warning.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | US town or city, e.g. 'Ridgecrest'. Add state. |
| days | number | – | – |
| latitude | number | – | Decimal degrees. Give with longitude, OR use zip, OR city. |
| limit | integer | – | – |
| longitude | number | – | – |
| min_magnitude | number | – | – |
| radius_km | number | – | – |
| state | string | – | Two-letter code or name, with city. |
| zip | string | – | US 5-digit ZIP code, e.g. '93555'. |
No output schema declared.
No examples provided.
largest_on_record Largest earthquakes on record ~170
The largest earthquakes in QuakeIndex's copy of the USGS catalogue for a US state, county ('Kern County, CA'), town ('Ridgecrest, CA') or ZIP code, with the catalogue span it covers. Data: USGS, as held by QuakeIndex. Each result includes its source, when the data was last confirmed, and links to the QuakeIndex and USGS event pages. No predictions and no warnings: results name ShakeAlert and MyShake as the sources of earthquake early warning.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| place | string | yes | State, 'County, ST', 'Town, ST' or ZIP. |
| radius_km | number | – | For a town or ZIP only. |
| state | string | – | Optional state to disambiguate. |
No output schema declared.
No examples provided.
latest_earthquakes Latest earthquakes ~148
The most recent earthquakes recorded by USGS worldwide or only in the United States, newest first, filtered by minimum magnitude and hours back (up to 7 days). Use for 'any earthquakes today?' questions. Data: USGS, as held by QuakeIndex. Each result includes its source, when the data was last confirmed, and links to the QuakeIndex and USGS event pages. No predictions and no warnings: results name ShakeAlert and MyShake as the sources of earthquake early warning.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | number | – | How far back to look. |
| limit | integer | – | – |
| min_magnitude | number | – | – |
| us_only | boolean | – | – |
No output schema declared.
No examples provided.
place_activity Is this normal for here? ~200
The QuakeIndex score for a US state or county: the last 7 days' earthquake activity ranked 0-100 against that place's own 10-year history, its label (quiet / typical / elevated / unusual) and the normal band for a week. It describes observed activity and is NOT a forecast or a risk rating. A missing score is never zero. Data: USGS, as held by QuakeIndex. Each result includes its source, when the data was last confirmed, and links to the QuakeIndex and USGS event pages. No predictions and no warnings: results name ShakeAlert and MyShake as the sources of earthquake early warning.
| Name | Type | Req | Description |
|---|---|---|---|
| county | string | – | Optional county within state, e.g. 'Kern'. |
| place | string | – | Alternative free text: 'Nevada' or 'Washoe County, NV'. |
| state | string | – | Two-letter code or name, e.g. 'CA'. |
No output schema declared.
No examples provided.
was_that_an_earthquake Was that an earthquake? ~305
Checks whether USGS has recorded an earthquake that someone who just felt shaking a few minutes ago could have felt: large and close enough for an estimated intensity of MMI 2+ at their location (Atkinson & Wald 2007, the equation USGS Did You Feel It? uses). Answers yes (with the event), not_yet_reported (nothing yet, but small quakes take minutes to be catalogued, so this is not a no), or no; smaller quakes recorded nearby are listed as too small to feel. The result links USGS Did You Feel It? for reporting shaking. Data: USGS, as held by QuakeIndex. Each result includes its source, when the data was last confirmed, and links to the QuakeIndex and USGS event pages. No predictions and no warnings: results name ShakeAlert and MyShake as the sources of earthquake early warning.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | US town or city, e.g. 'Ridgecrest'. Add state. |
| latitude | number | – | Decimal degrees. Give with longitude, OR use zip, OR city. |
| longitude | number | – | – |
| minutes_ago | number | – | Roughly how long ago the shaking was felt. |
| radius_km | number | – | – |
| state | string | – | Two-letter code or name, with city. |
| zip | string | – | US 5-digit ZIP code, e.g. '93555'. |
No output schema declared.
No examples provided.
How do I install the QuakeIndex MCP server?
QuakeIndex is a hosted endpoint at https://quakeindex.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · quakeindex.com
claude mcp add --transport http com-quakeindex-quakeindex 'https://quakeindex.com/mcp'
What is the QuakeIndex MCP server?
QuakeIndex is an MCP server listed in the public MCP registry as com.quakeindex/quakeindex. Live USGS earthquake data: latest quakes, quakes near a US place, and was that an earthquake? This page covers its hosted endpoint (https://quakeindex.com/mcp).
Is the QuakeIndex MCP server safe to use?
QuakeIndex scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the QuakeIndex MCP server expose?
QuakeIndex exposes 6 tools: latest_earthquakes, earthquakes_near, earthquake_details, place_activity, was_that_an_earthquake, largest_on_record. Their descriptions and schemas cost roughly 1,208 tokens of context every time the server is loaded.
Does the QuakeIndex MCP server require authentication?
No. We connected to QuakeIndex without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the QuakeIndex MCP server still maintained?
QuakeIndex is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the QuakeIndex MCP server?
VerifyMCP ran 13 checks on QuakeIndex, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.