mcp-registry/io.github.brandempire/river-water-watch · v1.0.0
As of 2026-10-19 19:57 UTC, the Brandempire River Water Watch MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Score a river cruise date against daily water levels on the Rhine, Danube, Elbe and Seine.
Claude Code
claude mcp add --transport http brandempire-river-water-watch-mcp-server https://www.riverwaterwatch.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"brandempire-river-water-watch-mcp-server": {
"type": "http",
"url": "https://www.riverwaterwatch.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
4 of 4 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
6 parameter(s) across 3 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.brandempire%2Friver-water-watch/fixes
{
"name": "get_live_gauges",
"description": "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.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_month_detail",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"river",
"month"
],
"properties": {
"month": {
"enum": [
"january",
"february",
"march",
"april",
"may",
"june",
"july",
"august",
"september",
"october",
"november",
"december"
],
"type": "string"
},
"river": {
"enum": [
"rhine",
"danube",
"elbe",
"seine"
],
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_monthly_odds",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"river"
],
"properties": {
"river": {
"enum": [
"rhine",
"danube",
"elbe",
"seine"
],
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.brandempire/river-water-watch"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.brandempire/river-water-watch"}) over MCP.
score_sailing ~197 tokensget_month_detail ~155 tokensget_monthly_odds ~117 tokensget_live_gauges ~75 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.brandempire%2Friver-water-watch?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.brandempire%2Friver-water-watch?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.brandempire%2Friver-water-watch.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.brandempire%2Friver-water-watch.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.brandempire%2Friver-water-watch?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:8f8fffd7618cf754…, first seen 2026-10-17, included at leaf 7931 of 28,506. Version history · verify what your client received.
Compare: most reliable data servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-19 19:57 UTC, the Brandempire River Water Watch MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Brandempire River Water Watch MCP server advertises 4 tools, including get_live_gauges, get_month_detail, get_monthly_odds, score_sailing.
Point your MCP client at this streamable-http endpoint: https://www.riverwaterwatch.com/mcp
Glimind scanned all 4 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.