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 1 hour ago.

UpLast checked 1 hour 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
43 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
River levels & flood alerts: USGS gauges. $0.01/query. Register in-session — free testnet funds.
Website
https://a2awire.com/data/riverwatch-usgs-river-levels-stream-flow-gauges-dc094e
Repository
https://github.com/ee324/a2awire
Listing
From the official MCP registry (active).
Recent checks of RiverWatch: USGS river levels & stream-flow gauges — per query
CheckedResultHandshake
1 hour agoHandshake completed43 ms
1 day agoHandshake completed276 ms
2 days agoHandshake completed172 ms
3 days agoHandshake completed220 ms
4 days agoHandshake completed291 ms
5 days agoHandshake completed245 ms
6 days agoHandshake completed33 ms
9 days agoHandshake completed896 ms
12 days agoHandshake completed62 ms
14 days agoHandshake completed561 ms
16 days agoHandshake completed195 ms
18 days agoHandshake completed123 ms
20 days agoHandshake completed44 ms
22 days agoHandshake completed123 ms
25 days agoHandshake completed108 ms
26 days agoHandshake completed196 ms
28 days agoHandshake completed40 ms
29 days agoHandshake completed34 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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.