Remote MCP · Endpoint

Pool Log — CDC-range water test log (no AI) MCP server

No. Pool Log — CDC-range water test log (no AI) answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://pool-log.rowb.app/mcp

The last check completed an MCP handshake.

Registry name
app.rowb.pool-log/water-log
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
452 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Deterministic pool and spa water test log. Checks readings against US CDC ranges. No AI.
Listing
From the official MCP registry (active).
Recent checks of Pool Log — CDC-range water test log (no AI)
CheckedResultHandshake
9 hours agoHandshake completed452 ms
4 days agoHandshake completed487 ms
14 days agoHandshake completed422 ms
15 days agoHandshake completed487 ms
15 days agoHandshake completed480 ms
17 days agoHandshake completed430 ms
18 days agoHandshake completed415 ms
19 days agoHandshake completed419 ms
20 days agoHandshake completed409 ms
21 days agoHandshake completed400 ms
23 days agoHandshake completed404 ms
26 days agoHandshake completed447 ms
28 days agoHandshake completed508 ms

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

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 Pool Log — CDC-range water test log (no AI) and makes no claim about it beyond what these checks measured.