# River Water Watch (remote · www.riverwaterwatch.com)

Score a river cruise date against daily water levels on the Rhine, Danube, Elbe and Seine.

- Trust score: 65/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `www.riverwaterwatch.com`: 65/100 (this document), [markdown](https://verifymcp.io/servers/com-riverwaterwatch-river-water-watch/www.md), [page](https://verifymcp.io/servers/com-riverwaterwatch-river-water-watch/www)

## Channel facts

- Endpoint: `https://www.riverwaterwatch.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-10-18.

- **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 4 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**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 264 tokens (~66/item across 4 items; 4 tools + 0 resources), lean.
  - 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**: 67/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.
- **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 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the River Water Watch MCP server?

River Water Watch is a hosted endpoint at https://www.riverwaterwatch.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-riverwaterwatch-river-water-watch 'https://www.riverwaterwatch.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-riverwaterwatch-river-water-watch": {
      "url": "https://www.riverwaterwatch.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-riverwaterwatch-river-water-watch": {
      "type": "http",
      "url": "https://www.riverwaterwatch.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-riverwaterwatch-river-water-watch]
url = "https://www.riverwaterwatch.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-riverwaterwatch-river-water-watch": {
      "type": "remote",
      "url": "https://www.riverwaterwatch.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-riverwaterwatch-river-water-watch --url 'https://www.riverwaterwatch.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-riverwaterwatch-river-water-watch:
    url: "https://www.riverwaterwatch.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-riverwaterwatch-river-water-watch": {
      "Transport": "http",
      "Url": "https://www.riverwaterwatch.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-riverwaterwatch-river-water-watch -t streamable-http -u 'https://www.riverwaterwatch.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-riverwaterwatch-river-water-watch": {
      "type": "http",
      "url": "https://www.riverwaterwatch.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-10-18 (score 65, +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-10-17 (score 64, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-16 (score 64)

First indexed and scored.

## MCP tools (4)

### `get_monthly_odds` (~57 tokens)

Current 12-month cruise-disruption odds for one of Europe's main cruise rivers (chance a sailing day hits low water, or high water on the Seine). Refreshed daily from official sources.

Input parameters:

- `river` (string, required)

### `get_live_gauges` (~48 tokens)

Today's official water-level readings (cm) at the cruise-critical gauges on the Rhine, Danube, Elbe and Seine, with each station's state and its percentile against thirty years.

### `score_sailing` (~99 tokens)

Score a specific river cruise: the chance a sailing departing on a given date meets low water (high water on the Seine) at its river's tightest stretch. Uses the live daily forecast where it reaches (~7 months) and the thirty-year weekly record beyond, plus what the same dates actually did in each of the last five years.

Input parameters:

- `departure_date` (string, required)
- `nights` (integer)
- `river` (string, required)

### `get_month_detail` (~60 tokens)

Why a given month behaves the way it does on one of the four rivers: the seasonal hydrology, the thirty-year frequency, and the last five years' outcomes for that month.

Input parameters:

- `month` (string, required)
- `river` (string, required)

## Diagnostics

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

## Score history

- 2026-10-18: 65
- 2026-10-17: 64
- 2026-10-16: 64

## Common questions

### What is the River Water Watch MCP server?

River Water Watch is an MCP server listed in the public MCP registry as com.riverwaterwatch/river-water-watch. Score a river cruise date against daily water levels on the Rhine, Danube, Elbe and Seine. This page covers its hosted endpoint (https://www.riverwaterwatch.com/mcp).

### Is the River Water Watch MCP server safe to use?

River Water Watch scores 65 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 Water Watch MCP server expose?

River Water Watch exposes 4 tools: get_monthly_odds, get_live_gauges, score_sailing, get_month_detail. Their descriptions and schemas cost roughly 264 tokens of context every time the server is loaded.

### Does the River Water Watch MCP server require authentication?

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

### Is the River Water Watch MCP server still maintained?

River Water Watch is still listed as active in the MCP registry. We last reached this channel on 18 October 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://www.riverwaterwatch.com/mcp
- Website: https://www.riverwaterwatch.com/for-ai
- Changelog RSS feed: https://verifymcp.io/servers/com-riverwaterwatch-river-water-watch/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-riverwaterwatch-river-water-watch/www.json
- HTML version of this page: https://verifymcp.io/servers/com-riverwaterwatch-river-water-watch/www