Check river flow and gage height at USGS stream gauges before a paddling, fishing or riverside trip.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Use this when the user wants to find USGS river or stream gauges (site numbers) by US state and river name, or near a US city or town. Returns up to 25 active gauges with current data, with distance for city searches. Does not accept coordinates and does not return readings; use get_river_conditions for flow and gage height.
Words from the river or gauge name, e.g. Arkansas River. Optional filter.
US city or town with 15,000+ people, e.g. Boulder. Gauges are listed by distance from it.
US state as a two-letter code or name, e.g. CO. Required unless place is given; with place it picks between same-named cities.
Search radius around place in miles, 1 to 50, e.g. 15 (default 15).
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http river-levels https://river-levels.zovo.one/mcp
Use this when the user wants to find USGS river or stream gauges (site numbers) by US state and river name, or near a US city or town. Returns up to 25 active gauges with current data, with distance for city searches. Does not accept coordinates and does not return readings; use get_river_conditions for flow and gage height.
| Argument | Type | Description |
|---|---|---|
| name | string | Words from the river or gauge name, e.g. Arkansas River. Optional filter. |
| place | string | US city or town with 15,000+ people, e.g. Boulder. Gauges are listed by distance from it. |
| state | string | US state as a two-letter code or name, e.g. CO. Required unless place is given; with place it picks between same-named cities. |
| radius_miles | number | Search radius around place in miles, 1 to 50, e.g. 15 (default 15). |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"name": {
"type": "string",
"maxLength": 60,
"description": "Words from the river or gauge name, e.g. Arkansas River. Optional filter."
},
"place": {
"type": "string",
"maxLength": 80,
"description": "US city or town with 15,000+ people, e.g. Boulder. Gauges are listed by distance from it."
},
"state": {
"type": "string",
"maxLength": 40,
"description": "US state as a two-letter code or name, e.g. CO. Required unless place is given; with place it picks between same-named cities."
},
"radius_miles": {
"type": "number",
"description": "Search radius around place in miles, 1 to 50, e.g. 15 (default 15)."
}
}
}Use this when the user wants current river flow (discharge) or gage height at USGS stream gauges, the 24-hour trend, how today compares with the same date in past years, or a printable condition sheet. Takes 1 to 10 USGS site numbers and 1 to 7 days; returns a PDF and a CSV of readings. Readings are provisional. Does not forecast and is not a flood warning; use find_river_gauges first when the site number is unknown.
| Argument | Type | Description |
|---|---|---|
| days | number | Days of readings to include, 1 to 7, e.g. 7 (default 7). |
| paper | string | PDF paper size, e.g. letter (default) or a4. |
| site_ids* | array | USGS site numbers to check, e.g. ["01646500","01638500"]. 1 to 10 entries. |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"site_ids"
],
"properties": {
"days": {
"type": "number",
"description": "Days of readings to include, 1 to 7, e.g. 7 (default 7)."
},
"paper": {
"enum": [
"letter",
"a4"
],
"type": "string",
"description": "PDF paper size, e.g. letter (default) or a4."
},
"site_ids": {
"type": "array",
"items": {
"type": "string",
"maxLength": 40,
"description": "USGS site number, 8 to 15 digits, e.g. 01646500."
},
"description": "USGS site numbers to check, e.g. [\"01646500\",\"01638500\"]. 1 to 10 entries."
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 8, 2026.