The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Water Levels listing page.
Lake and reservoir water levels from satellite radar altimetry — 518 inland water bodies worldwide, 1992 to the present, keyless.
Part of Pipeworx — an MCP gateway connecting AI agents to 1684+ live data sources.
| Tool | Answers |
|---|---|
water_level | Current and historical level for a named lake, sea or reservoir |
water_level_search | Which water bodies are monitored, by name, country or continent |
These are RELATIVE height variations, measured against each lake's own reference datum from a single satellite fly-over. They are not absolute elevation and not height above sea level.
A Caspian Sea reading of -1.88 means 1.88 m below that lake's reference, not
below sea level — reporting it as absolute would be wrong by about 28 m for the
Caspian alone. Every response carries measurement_note saying so, and the
per-lake datum where the source states it.
What the readings are good for: direction and magnitude of change. Whether a lake is rising or shrinking, and by how much, is exactly what altimetry answers well.
This dataset is universally cited as USDA FAS G-REALM
(ipad.fas.usda.gov). That host now returns 503 on its reservoir pages and 404
on the old per-lake paths. It has moved to NASA GSFC Global Water Monitor,
and the redirect only appears inside the old page's markup. The filename
convention survived intact — lake000270.10d.2.txt.
None.
Only large water bodies are measurable by radar altimetry; small lakes are not
covered at all. The registry ships with the pack (regenerate with
scripts/ingest-water-levels.ts); the per-lake series are fetched live, so
readings are as current as the source.
https://earth.gsfc.nasa.gov/gwm/timeseries/lake<ID>.10d.2.txtAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
tools/list at https://gateway.pipeworx.io/water-levels/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
Both URLs reach the same gateway and the same 1684+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/lake_water_level. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
Or run it directly to confirm it starts:
It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
The gateway picks the right tool and fills the arguments automatically.
MIT