Skip to content

River Water Watch MCP server

com.riverwaterwatch/river-water-watchriverwaterwatch.comstreamable-httpv1.0.0Scanned

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

4 tools: 1 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 1 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the River Water Watch MCP server can do

The River Water Watch MCP server is published by riverwaterwatch.com, a domain the MCP Registry verified. It has 4 tools. It can create or change data (1 tool: score_sailing), but cannot delete data. 3 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 14, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 1Claude Code: ask
  • score_sailingScore 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 3Show 3 read-only tools
  • get_live_gaugesToday'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.No findings

    Why it is in this group

    • The name "get_live_gauges" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_month_detailWhy 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.No findings

    Why it is in this group

    • The name "get_month_detail" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_monthly_oddsCurrent 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).No findings

    Why it is in this group

    • The name "get_monthly_odds" says "get": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:46 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://www.riverwaterwatch.com/mcp: tools/list returned 4 tools to an anonymous client, including score_sailing (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http river-water-watch https://www.riverwaterwatch.com/mcp
claude mcp add --transport http river-water-watch https://www.riverwaterwatch.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__river-water-watch__get_monthly_odds",
      "mcp__river-water-watch__get_live_gauges",
      "mcp__river-water-watch__get_month_detail"
    ],
    "ask": [
      "mcp__river-water-watch__score_sailing"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as river-water-watch. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.riverwaterwatch/river-water-watch/verify?hash=f1564cfa12c87bc7c89af96dc60434e2d9f4cac086256717785768da230bbf61" | jq -e '.changed == false'

Pinned hash f1564cfa12c8, from Nov 14, 2026, 05:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.riverwaterwatch/river-water-watch/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.riverwaterwatch/river-water-watch
[![Anlyon Radar](https://radar.anlyon.com/badge/com.riverwaterwatch/river-water-watch.svg)](https://radar.anlyon.com/servers/com.riverwaterwatch/river-water-watch)

Source: MCP Registry. Synced Oct 21, 2026, 18:02 UTC.

River Water Watch MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the River Water Watch MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the River Water Watch MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the River Water Watch MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the River Water Watch MCP server have?

4 tools: 1 write, 3 read. score_sailing, get_monthly_odds, get_live_gauges and get_month_detail.

Does the River Water Watch MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the River Water Watch MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the River Water Watch MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.