River Water Watch
REMOTE · WWW.RIVERWATERWATCH.COM · SCANNED OCT 4
Score a river cruise date against daily water levels on the Rhine, Danube, Elbe and Seine.
Available components
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 264 tokens (~66/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · www.riverwaterwatch.com
claude mcp add --transport http brandempire-river-water-watch 'https://www.riverwaterwatch.com/mcp'
{
"mcpServers": {
"brandempire-river-water-watch": {
"url": "https://www.riverwaterwatch.com/mcp"
}
}
} {
"servers": {
"brandempire-river-water-watch": {
"type": "http",
"url": "https://www.riverwaterwatch.com/mcp"
}
}
} [mcp_servers.brandempire-river-water-watch] url = "https://www.riverwaterwatch.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"brandempire-river-water-watch": {
"type": "remote",
"url": "https://www.riverwaterwatch.com/mcp",
"enabled": true
}
}
} openclaw mcp add brandempire-river-water-watch --url 'https://www.riverwaterwatch.com/mcp' --transport streamable-http
mcp_servers:
brandempire-river-water-watch:
url: "https://www.riverwaterwatch.com/mcp" {
"McpServers": {
"brandempire-river-water-watch": {
"Transport": "http",
"Url": "https://www.riverwaterwatch.com/mcp"
}
}
} assistant mcp add brandempire-river-water-watch -t streamable-http -u 'https://www.riverwaterwatch.com/mcp'
{
"mcpServers": {
"brandempire-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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 14 Sept 26 +1
- Stability: 0.97 → pass security
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 16 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Oct 2026 · Probed https://www.riverwaterwatch.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.riverwaterwatch.com | CN=YR1,O=Let's Encrypt,C=US | 19 Aug 2026 | 17 Nov 2026 | RSA 2048 | SHA256-RSA | 61d8010ec754cd34a1ba57b1310e8982ead |
| SANs: *.riverwaterwatch.com, riverwaterwatch.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.riverwaterwatch.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| riverwaterwatch.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.riverwaterwatch.com/mcp | Verified | 200 | |
| http (plaintext) | http://www.riverwaterwatch.com/mcp | HTTPS enforced | 308 | https://www.riverwaterwatch.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_live_gauges ~48
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_month_detail ~60
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.
| Name | Type | Req | Description |
|---|---|---|---|
| month | string | yes | – |
| river | string | yes | – |
No output schema declared.
No examples provided.
get_monthly_odds ~57
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.
| Name | Type | Req | Description |
|---|---|---|---|
| river | string | yes | – |
No output schema declared.
No examples provided.
score_sailing ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| departure_date | string | yes | – |
| nights | integer | – | – |
| river | string | yes | – |
No output schema declared.
No examples provided.
What is the River Water Watch MCP server?
River Water Watch is an MCP server listed in the public MCP registry as io.github.brandempire/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 78 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 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.