River Level MCP
REMOTE · RIVER-LEVEL-MCP.LIPMICHAL.WORKERS.DEV
Live US river levels, streamflow and NWS flood forecasts from USGS stream gauges.
Available components
Last scanned (10 minutes ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Maps and Location
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
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability69
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
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 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 5 Nov 26 +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.
- 4 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 3 Nov 26 66
First indexed and scored.
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 5 Nov 2026 · Probed https://river-level-mcp.lipmichal.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lipmichal.workers.dev | CN=WE1,O=Google Trust Services,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ebf145553d5751d20e0d3cd51e3d7a94 |
| SANs: lipmichal.workers.dev, *.lipmichal.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of river-level-mcp.lipmichal.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://river-level-mcp.lipmichal.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://river-level-mcp.lipmichal.workers.dev/mcp | Inconclusive | 405 |
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 →
find_river_gauges Find river gauges ~192
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
get_flood_forecast Get river flood forecast ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | 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. |
No output schema declared.
No examples provided.
get_river_history Get river level history ~178
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
get_river_level Get current river level ~163
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.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | 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. |
No output schema declared.
No examples provided.
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.
remote · river-level-mcp.lipmichal.workers.dev
claude mcp add --transport http theluckystrike-river-level-mcp 'https://river-level-mcp.lipmichal.workers.dev/mcp'
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.