Remote MCP · Endpoint

RiverWatch: USGS river levels & stream-flow gauges — per query MCP server

No. RiverWatch: USGS river levels & stream-flow gauges — per query answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://a2awire.com/mcp/data/riverwatch-usgs-river-levels-stream-flow-gauges-dc094e/http

The last check completed an MCP handshake.

Registry name
com.a2awire/data-river-level-stream-flow-flood-alert-gauge
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
44 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
River levels & flood alerts: USGS gauges. $0.01/query. Register in-session — free testnet funds.
Listing
From the official MCP registry (active).
Recent checks of RiverWatch: USGS river levels & stream-flow gauges — per query
CheckedResultHandshake
2 hours agoHandshake completed44 ms
2 days agoHandshake completed123 ms
4 days agoHandshake completed108 ms
6 days agoHandshake completed196 ms
7 days agoHandshake completed40 ms
8 days agoHandshake completed34 ms
9 days agoHandshake completed473 ms
12 days agoHandshake completed406 ms
14 days agoHandshake completed528 ms
15 days agoHandshake completed371 ms
17 days agoHandshake completed279 ms
18 days agoHandshake completed123 ms
19 days agoHandshake completed315 ms
20 days agoHandshake completed225 ms
20 days agoHandshake completed298 ms
22 days agoHandshake completed380 ms
23 days agoHandshake completed246 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with RiverWatch: USGS river levels & stream-flow gauges — per query and makes no claim about it beyond what these checks measured.