Remote MCP · Endpoint

Calculate Pool MCP server

No. Calculate Pool answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://calculatepool.com/mcp?src=mcp

The last check completed an MCP handshake.

Registry name
com.calculatepool/calculatepool
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
103 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Swimming pool math: volume in gallons, chemical doses, pump flow and heater BTU for any pool.
Listing
From the official MCP registry (active).
Recent checks of Calculate Pool
CheckedResultHandshake
20 minutes agoHandshake completed103 ms
3 days agoHandshake completed85 ms
14 days agoHandshake completed209 ms
14 days agoHandshake completed184 ms
15 days agoHandshake completed134 ms
16 days agoHandshake completed81 ms
18 days agoHandshake completed127 ms
18 days agoHandshake completed100 ms
19 days agoHandshake completed141 ms
21 days agoHandshake completed145 ms
22 days agoHandshake completed107 ms
25 days agoHandshake completed171 ms

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

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