# QuakeIndex (remote · quakeindex.com)

Live USGS earthquake data: latest quakes, quakes near a US place, and was that an earthquake?

- Trust score: 77/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `quakeindex.com`: 77/100 (this document), [markdown](https://verifymcp.io/servers/com-quakeindex-quakeindex/quakeindex.md), [page](https://verifymcp.io/servers/com-quakeindex-quakeindex/quakeindex)

## Channel facts

- Endpoint: `https://quakeindex.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 61% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-quakeindex-quakeindex 'https://quakeindex.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-quakeindex-quakeindex": {
      "url": "https://quakeindex.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-quakeindex-quakeindex": {
      "type": "http",
      "url": "https://quakeindex.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-quakeindex-quakeindex]
url = "https://quakeindex.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-quakeindex-quakeindex": {
      "type": "remote",
      "url": "https://quakeindex.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-quakeindex-quakeindex --url 'https://quakeindex.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-quakeindex-quakeindex:
    url: "https://quakeindex.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-quakeindex-quakeindex": {
      "Transport": "http",
      "Url": "https://quakeindex.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-quakeindex-quakeindex -t streamable-http -u 'https://quakeindex.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-quakeindex-quakeindex": {
      "type": "http",
      "url": "https://quakeindex.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 77, +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.

### 2026-11-19 (score 76, +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.

### 2026-11-17 (score 75, +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.

### 2026-11-15 (score 74, +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.

### 2026-11-13 (score 73, +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.

### 2026-11-11 (score 72, +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.

### 2026-11-09 (score 71, +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.

### 2026-11-06 (score 70, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (6)

### `latest_earthquakes` (~148 tokens)

Latest earthquakes

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.

Input parameters:

- `hours` (number): How far back to look.
- `limit` (integer)
- `min_magnitude` (number)
- `us_only` (boolean)

### `earthquakes_near` (~226 tokens)

Earthquakes near a place

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.

Input parameters:

- `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'.

### `earthquake_details` (~159 tokens)

Earthquake details and revisions

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.

Input parameters:

- `id` (string, required): USGS event id, e.g. 'ci41234567', or a QuakeIndex or USGS event page URL.

### `place_activity` (~200 tokens)

Is this normal for here?

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.

Input parameters:

- `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'.

### `was_that_an_earthquake` (~305 tokens)

Was that an earthquake?

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.

Input parameters:

- `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'.

### `largest_on_record` (~170 tokens)

Largest earthquakes on record

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.

Input parameters:

- `limit` (integer)
- `place` (string, required): State, 'County, ST', 'Town, ST' or ZIP.
- `radius_km` (number): For a town or ZIP only.
- `state` (string): Optional state to disambiguate.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-quakeindex-quakeindex/quakeindex#diagnostics

## Score history

- 2026-11-21: 77
- 2026-11-20: 76
- 2026-11-19: 76
- 2026-11-18: 75
- 2026-11-17: 75
- 2026-11-16: 74
- 2026-11-15: 74
- 2026-11-14: 73
- 2026-11-13: 73
- 2026-11-12: 72
- 2026-11-11: 72
- 2026-11-10: 71
- 2026-11-09: 71
- 2026-11-08: 70
- 2026-11-07: 70
- 2026-11-06: 70
- 2026-11-05: 69
- 2026-11-04: 69
- 2026-11-03: 68
- 2026-11-02: 68
- 2026-11-01: 67

## Common questions

### 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.

## Links

- Remote endpoint: https://quakeindex.com/mcp
- Website: https://quakeindex.com/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/com-quakeindex-quakeindex/quakeindex.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-quakeindex-quakeindex/quakeindex/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-quakeindex-quakeindex/quakeindex.json
- HTML version of this page: https://verifymcp.io/servers/com-quakeindex-quakeindex/quakeindex
