Skip to content

River Level MCP server

io.github.theluckystrike/river-level-mcptheluckystrikestreamable-httpv1.0.0Scanned

Live US river levels, streamflow and NWS flood forecasts from USGS stream gauges.

4 tools: 4 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

Decide which of this server's tools your agent can use.

  • 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 Level MCP server can do

The River Level MCP server is published by the GitHub account theluckystrike. It has 4 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

4 tools bring in text other people can write (find_river_gauges, get_river_level, get_river_history and 1 more).

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 16, 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

Only reads 4Show 4 read-only tools
  • find_river_gaugesSearch 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.Reads text others writeNo findings

    Why it is in this group

    • The name "find_river_gauges" says "find": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Find river gauges
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_flood_forecastThe 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 observatio…Reads text others writeNo findings

    Why it is in this group

    • The name "get_flood_forecast" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get flood forecast
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_river_historyDaily mean streamflow (default) or stage for a USGS gauge over the last 2 to 366 days, with first, last, low, high, mean and change.Reads text others writeNo findings

    Why it is in this group

    • The name "get_river_history" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get river history
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_river_levelCurrent 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…Reads text others writeNo findings

    Why it is in this group

    • The name "get_river_level" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get river level
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

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 outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write4
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 18, 2026, 16:24 UTC, unchanged since Nov 4, 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
0
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

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-level https://river-level-mcp.lipmichal.workers.dev/mcp
claude mcp add --transport http river-level https://river-level-mcp.lipmichal.workers.dev/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-level__find_river_gauges",
      "mcp__river-level__get_river_level",
      "mcp__river-level__get_river_history",
      "mcp__river-level__get_flood_forecast"
    ],
    "ask": [],
    "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-level. Review it before you use it.

Capability tags behind 4 rules
  • mcp__river-level__find_river_gauges untrusted-input
  • mcp__river-level__get_river_level untrusted-input
  • mcp__river-level__get_river_history untrusted-input
  • mcp__river-level__get_flood_forecast untrusted-input

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/io.github.theluckystrike/river-level-mcp/verify?hash=7b0f532d9c0895f9953db0d617f203d686422f6dc80ca7f31b62612d4f2347b2" | jq -e '.changed == false'

Pinned hash 7b0f532d9c08, from Nov 16, 2026, 19:17 UTC.

Watch

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

https://radar.anlyon.com/servers/io.github.theluckystrike/river-level-mcp/changes.xml

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

Badge

Anlyon Radar badge for io.github.theluckystrike/river-level-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.theluckystrike/river-level-mcp.svg)](https://radar.anlyon.com/servers/io.github.theluckystrike/river-level-mcp)

Source: MCP Registry · repository. Synced Nov 3, 2026, 08:18 UTC.

River Level MCP server: questions and answers

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

Is the River Level MCP server safe?

No scan can promise that. What its definitions show: 4 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the River Level 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 Level 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 Level MCP server have?

4 tools: 4 read. find_river_gauges, get_river_level, get_river_history and get_flood_forecast.

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

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

Does the River Level 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 Level MCP server changed its tools?

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