Remote MCP · Endpoint

Water Quality Portal MCP server

No. Water Quality Portal answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://gateway.pipeworx.io/water-quality-portal/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/water-quality-portal
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
75 ms
Tools exposed
45 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Water Quality Portal (WQP) MCP — US ambient water-chemistry monitoring
Listing
From the official MCP registry (active).
Recent checks of Water Quality Portal
CheckedResultHandshake
1 day agoHandshake completed75 ms
3 days agoHandshake completed54 ms
5 days agoHandshake completed72 ms
7 days agoHandshake completed109 ms
8 days agoHandshake completed76 ms
10 days agoHandshake completed184 ms
11 days agoHandshake completed47 ms
13 days agoHandshake completed1.09 s
15 days agoHandshake completed56 ms
17 days agoHandshake completed45 ms
18 days agoHandshake completed51 ms
19 days agoHandshake completed57 ms
21 days agoHandshake completed37 ms
22 days agoHandshake completed40 ms
22 days agoHandshake completed883 ms

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

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 Water Quality Portal and makes no claim about it beyond what these checks measured.