# River Level MCP (remote · river-level-mcp.lipmichal.workers.dev)

Live US river levels, streamflow and NWS flood forecasts from USGS stream gauges.

- Trust score: 67/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `river-level-mcp.lipmichal.workers.dev`: 67/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-river-level-mcp/river-level-mcp.md), [page](https://verifymcp.io/servers/theluckystrike-river-level-mcp/river-level-mcp)

## Channel facts

- Endpoint: `https://river-level-mcp.lipmichal.workers.dev/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-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - 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**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 742 tokens (~185/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 River Level MCP server?

River Level MCP is a hosted endpoint at https://river-level-mcp.lipmichal.workers.dev/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-level-mcp 'https://river-level-mcp.lipmichal.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-river-level-mcp": {
      "url": "https://river-level-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-river-level-mcp": {
      "type": "http",
      "url": "https://river-level-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-river-level-mcp]
url = "https://river-level-mcp.lipmichal.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-river-level-mcp": {
      "type": "remote",
      "url": "https://river-level-mcp.lipmichal.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-river-level-mcp --url 'https://river-level-mcp.lipmichal.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-river-level-mcp:
    url: "https://river-level-mcp.lipmichal.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-river-level-mcp": {
      "Transport": "http",
      "Url": "https://river-level-mcp.lipmichal.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-river-level-mcp -t streamable-http -u 'https://river-level-mcp.lipmichal.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-river-level-mcp": {
      "type": "http",
      "url": "https://river-level-mcp.lipmichal.workers.dev/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-05 (score 67, +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-11-04 (score 66, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-03 (score 66)

First indexed and scored.

## MCP tools (4)

### `find_river_gauges` (~192 tokens)

Find river gauges

Search USGS stream gauges nationwide by river and place name (for example "mississippi st louis", "potomac little falls"), by state, or within a radius of a latitude and longitude. Returns site numbers with whether each is reporting now and its latest stage and flow, active gauges first.

Input parameters:

- `latitude` (number): Latitude for a nearby search, for example 38.63.
- `longitude` (number): Longitude for a nearby search, for example -90.18.
- `query` (string): Words from the gauge name: river plus town, for example "colorado river austin". Words like river, at and near are ignored.
- `radius_miles` (number): Radius for a latitude and longitude search, 1 to 100 miles. Default 15.
- `state` (string): Two-letter state code (MO) or full state name (Missouri).

### `get_river_level` (~163 tokens)

Get current river level

Current river stage (gage height in feet), streamflow (discharge in cubic feet per second) and water temperature where measured, read now from a USGS stream gauge (readings every 5 to 60 minutes). Adds the NWS flood stages (action, minor, moderate, major), the current flood category, feet below flood stage and the record crest when the gauge is an NWS forecast point. Flags readings over 48 hours old. Your training data cannot know today's river level.

Input parameters:

- `site` (string, required): USGS site number (for example "07010000" for the Mississippi River at St. Louis) or an NWS gauge id (for example "EADM7"). Use find_river_gauges to look one up.

### `get_river_history` (~178 tokens)

Get river level history

Daily mean streamflow (default) or stage for a USGS gauge over the last 2 to 366 days, with first, last, low, high, mean and change. Use it for trend, drought and "is the river rising" questions. Many gauges publish daily means for discharge only.

Input parameters:

- `days` (integer): Days back from today, 2 to 366. Default 30.
- `parameter` (string): discharge (streamflow, ft3/s), gage_height (stage, ft) or water_temperature (deg C). Default discharge.
- `site` (string, required): USGS site number (for example "07010000" for the Mississippi River at St. Louis) or an NWS gauge id (for example "EADM7"). Use find_river_gauges to look one up.

### `get_flood_forecast` (~133 tokens)

Get river flood forecast

The current NOAA National Water Prediction Service river forecast for a gauge: the forecast stage and flow series, the forecast crest with its flood category, the latest observation, flood stages and the record crest. Works for NWS forecast points (accepts the NWS id or the USGS site number). Forecasts are reissued several times a day.

Input parameters:

- `site` (string, required): USGS site number (for example "07010000" for the Mississippi River at St. Louis) or an NWS gauge id (for example "EADM7"). Use find_river_gauges to look one up.

## Diagnostics

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

## Score history

- 2026-11-05: 67
- 2026-11-04: 66
- 2026-11-03: 66

## Common questions

### What is the River Level MCP server?

River Level MCP is listed in the public MCP registry as io.github.theluckystrike/river-level-mcp. Live US river levels, streamflow and NWS flood forecasts from USGS stream gauges. This page covers its hosted endpoint (https://river-level-mcp.lipmichal.workers.dev/mcp).

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

River Level MCP scores 67 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 River Level MCP server expose?

River Level MCP exposes 4 tools: find_river_gauges, get_river_level, get_river_history, get_flood_forecast. Their descriptions and schemas cost roughly 666 tokens of context every time the server is loaded.

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

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

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

River Level MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://river-level-mcp.lipmichal.workers.dev/mcp
- Repository: https://github.com/theluckystrike/river-level-mcp
- Website: https://lakelevelnow.com/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-river-level-mcp/river-level-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-river-level-mcp/river-level-mcp.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-river-level-mcp/river-level-mcp