# Zovo River Level Check (remote · river-levels.zovo.one)

Check river flow and gage height at USGS stream gauges before a paddling, fishing or riverside trip.

- Trust score: 87/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `river-levels.zovo.one`: 87/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-river-levels/river-levels.md), [page](https://verifymcp.io/servers/theluckystrike-river-levels/river-levels)

## Channel facts

- Endpoint: `https://river-levels.zovo.one/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**: 97/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server, and every tool looks verifiably read-only (it declares readOnlyHint: true, starts its name with a read verb and describes no write), so an anonymous caller can read but cannot change anything. We can't see whether a tool returns data specific to one caller, so keep any per-user data behind authorisation.
  - 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**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 418 tokens (~139/item across 3 items; 2 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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.
  - Supports UI / widget rendering.

## Install

### How do I install the Zovo River Level Check MCP server?

Zovo River Level Check is a hosted endpoint at https://river-levels.zovo.one/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 theluckystrike-river-levels 'https://river-levels.zovo.one/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-river-levels": {
      "url": "https://river-levels.zovo.one/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-river-levels": {
      "type": "http",
      "url": "https://river-levels.zovo.one/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-river-levels]
url = "https://river-levels.zovo.one/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-river-levels": {
      "type": "remote",
      "url": "https://river-levels.zovo.one/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-river-levels --url 'https://river-levels.zovo.one/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-river-levels:
    url: "https://river-levels.zovo.one/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-river-levels": {
      "Transport": "http",
      "Url": "https://river-levels.zovo.one/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-river-levels -t streamable-http -u 'https://river-levels.zovo.one/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-river-levels": {
      "type": "http",
      "url": "https://river-levels.zovo.one/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-19 (score 87, +1)

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

### 2026-11-17 (score 86, +1)

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

### 2026-11-15 (score 85, +1)

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

### 2026-11-13 (score 84, +1)

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

### 2026-11-11 (score 83, +1)

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

### 2026-11-09 (score 82, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-08 (score 81)

First indexed and scored.

## MCP tools (2)

### `find_river_gauges` (~207 tokens)

Find river gauges

Use this when the user wants to find USGS river or stream gauges (site numbers) by US state and river name, or near a US city or town. Returns up to 25 active gauges with current data, with distance for city searches. Does not accept coordinates and does not return readings; use get_river_conditions for flow and gage height.

Input parameters:

- `name` (string): Words from the river or gauge name, e.g. Arkansas River. Optional filter.
- `place` (string): US city or town with 15,000+ people, e.g. Boulder. Gauges are listed by distance from it.
- `radius_miles` (number): Search radius around place in miles, 1 to 50, e.g. 15 (default 15).
- `state` (string): US state as a two-letter code or name, e.g. CO. Required unless place is given; with place it picks between same-named cities.

Output parameters:

- `gauges` (array)
- `matched_place` (string)
- `note` (string)
- `other_places` (array)
- `retrieved_utc` (string)
- `search` (string)
- `shown` (number)
- `source` (string)
- `source_url` (string)
- `total` (number)

### `get_river_conditions` (~195 tokens)

Get river conditions

Use this when the user wants current river flow (discharge) or gage height at USGS stream gauges, the 24-hour trend, how today compares with the same date in past years, or a printable condition sheet. Takes 1 to 10 USGS site numbers and 1 to 7 days; returns a PDF and a CSV of readings. Readings are provisional. Does not forecast and is not a flood warning; use find_river_gauges first when the site number is unknown.

Input parameters:

- `days` (number): Days of readings to include, 1 to 7, e.g. 7 (default 7).
- `paper` (string): PDF paper size, e.g. letter (default) or a4.
- `site_ids` (array, required): USGS site numbers to check, e.g. ["01646500","01638500"]. 1 to 10 entries.

Output parameters:

- `downloads` (object)
- `provisional_note` (string)
- `retrieved_utc` (string)
- `sites` (array)
- `source` (string)
- `source_url` (string)
- `statistics_note` (string)
- `summary` (object)
- `trend_rule` (string)

## Diagnostics

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

## Score history

- 2026-11-21: 87
- 2026-11-20: 87
- 2026-11-19: 87
- 2026-11-18: 86
- 2026-11-17: 86
- 2026-11-16: 85
- 2026-11-15: 85
- 2026-11-14: 84
- 2026-11-13: 84
- 2026-11-12: 83
- 2026-11-11: 83
- 2026-11-10: 82
- 2026-11-09: 82
- 2026-11-08: 81

## Common questions

### What is the Zovo River Level Check MCP server?

Zovo River Level Check is an MCP server listed in the public MCP registry as io.github.theluckystrike/river-levels. Check river flow and gage height at USGS stream gauges before a paddling, fishing or riverside trip. This page covers its hosted endpoint (https://river-levels.zovo.one/mcp).

### Is the Zovo River Level Check MCP server safe to use?

Zovo River Level Check scores 87 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 Zovo River Level Check MCP server expose?

Zovo River Level Check exposes 2 tools: find_river_gauges, get_river_conditions. Their descriptions and schemas cost roughly 402 tokens of context every time the server is loaded.

### Does the Zovo River Level Check MCP server require authentication?

No. We connected to Zovo River Level Check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Zovo River Level Check MCP server still maintained?

Zovo River Level Check 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 Zovo River Level Check MCP server?

VerifyMCP ran 14 checks on Zovo River Level Check, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 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://river-levels.zovo.one/mcp
- Website: https://river-levels.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-river-levels/river-levels.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-river-levels/river-levels/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/theluckystrike-river-levels/river-levels.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-river-levels/river-levels
