# USGS Earthquakes (remote · mcp.olyport.com)

Real-time earthquake events from the US Geological Survey

- Trust score: 67/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.olyport.com`: 67/100 (this document), [markdown](https://verifymcp.io/servers/com-olyport-earthquake/earthquake-mcp.md), [page](https://verifymcp.io/servers/com-olyport-earthquake/earthquake-mcp)

## Channel facts

- Endpoint: `https://mcp.olyport.com/earthquake/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.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-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 76/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 410 tokens (~136/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-olyport-earthquake https://mcp.olyport.com/earthquake/mcp
```

### Codex

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

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-olyport-earthquake --url https://mcp.olyport.com/earthquake/mcp --transport streamable-http
```

### Hermes

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

### Other

```json
{
  "mcpServers": {
    "com-olyport-earthquake": {
      "type": "http",
      "url": "https://mcp.olyport.com/earthquake/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-08-03 (score 67, +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-08-01 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 65, +2)

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

### 2026-07-30 (score 63, +1)

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

### 2026-07-28 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 61, +1)

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

### 2026-07-26 (score 60)

First indexed and scored.

## MCP tools (3)

### `get_recent_earthquakes` (~137 tokens)

Get recent earthquakes worldwide above a minimum magnitude.

    Returns earthquake events from the USGS catalog sorted by time (newest first).
    Useful for monitoring seismic activity globally.

    Args:
        min_magnitude: Minimum magnitude to include (default 2.5). Use 4.5+ for significant quakes only.
        days: Number of days to look back (default 7, max 30).
        limit: Maximum number of earthquakes to return (default 50, max 500).

Input parameters:

- `days` (integer)
- `limit` (integer)
- `min_magnitude` (number)

Output parameters:

- `result` (string)

### `get_earthquakes_near` (~183 tokens)

Get earthquakes near a specific geographic location.

    Searches for earthquakes within a radius of the given coordinates.
    Useful for assessing local seismic risk or investigating felt reports.

    Args:
        latitude: Latitude of the center point (e.g. 37.7749 for San Francisco).
        longitude: Longitude of the center point (e.g. -122.4194 for San Francisco).
        radius_km: Search radius in kilometers (default 100, max 20001).
        min_magnitude: Minimum magnitude to include (default 1.0).
        days: Number of days to look back (default 30, max 365).

Input parameters:

- `days` (integer)
- `latitude` (number, required)
- `longitude` (number, required)
- `min_magnitude` (number)
- `radius_km` (number)

Output parameters:

- `result` (string)

### `get_earthquake_detail` (~90 tokens)

Get full details of a specific earthquake event by its USGS event ID.

    Returns comprehensive information including magnitude, location, depth,
    felt reports, tsunami status, and tectonic summary when available.

    Args:
        event_id: The USGS event ID (e.g. 'us7000m1xh'). Get IDs from search results.

Input parameters:

- `event_id` (string, required)

Output parameters:

- `result` (string)

## Diagnostics

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

## Score history

- 2026-08-03: 67
- 2026-08-02: 66
- 2026-08-01: 66
- 2026-07-31: 65
- 2026-07-30: 63
- 2026-07-29: 62
- 2026-07-28: 62
- 2026-07-27: 61
- 2026-07-26: 60

## Links

- Remote endpoint: https://mcp.olyport.com/earthquake/mcp
- Website: https://olyport.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-olyport-earthquake/earthquake-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-olyport-earthquake/earthquake-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-olyport-earthquake/earthquake-mcp