Flood vs River Level MCP
Flood is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). River Level MCP is an MCP server published by theluckystrike. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Flood |  River Level MCP |
|---|---|---|
| Official MCP Registry | Listed Version: 1.1.1 Downloads/month (npm): 1 019 Downloads/week (npm): 117 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Flood | River Level MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-11-02 | Not published |
| Where it runs (differs) | Remote server (gateway.pipeworx.io/flood/mcp) | Remote server (river-level-mcp.lipmichal.workers.dev/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/pipeworx-io/mcp-flood | github.com/theluckystrike/river-level-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-11-03 |
| Endpoint at the last check (differs) | Responded 5 h ago | Responded 19 h ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Flood
Flood MCP — wraps Open-Meteo Flood API (free, no auth)
River Level MCP
Live US river levels, streamflow and NWS flood forecasts from USGS stream gauges.
How to run each
Flood As a remote MCP server
claude mcp add --transport http flood https://gateway.pipeworx.io/flood/mcpRequires: PIPEWORX_API_KEY (secret)
River Level MCP As a remote MCP server
claude mcp add --transport http river-level-mcp https://river-level-mcp.lipmichal.workers.dev/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily check. How we check endpoints
Tools each declares
Neither the marketplaces of River Level MCP nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
The marketplaces of River Level MCP publish no settings it asks for, so we do not compare settings.
What it can do: Flood · What it can do: River Level MCP · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.