Remote MCP · Endpoint

Uk Flood Monitoring MCP server

No. Uk Flood Monitoring answered an MCP handshake 17 hours ago.

UpLast checked 17 hours ago

Server URL

https://gateway.pipeworx.io/uk-flood-monitoring/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/uk-flood-monitoring
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
76 ms
Tools exposed
45 tools
Uptime, last 30 days
93.3% from 15 checks
Described by its publisher as
UK Environment Agency real-time flood-monitoring MCP.
Listing
From the official MCP registry (active).
Recent checks of Uk Flood Monitoring
CheckedResultHandshake
17 hours agoHandshake completed76 ms
2 days agoHandshake completed52 ms
4 days agoHandshake completed274 ms
6 days agoHandshake completed73 ms
8 days agoHandshake completed67 ms
9 days agoHandshake completed217 ms
10 days agoHandshake completed40 ms
13 days agoHandshake completed36 ms
14 days agoHandshake completed58 ms
16 days agoHandshake completed768 ms
17 days agoFailed - the request timed out—
19 days agoHandshake completed1.03 s
20 days agoHandshake completed37 ms
21 days agoHandshake completed38 ms
21 days agoHandshake completed54 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 14 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 Uk Flood Monitoring and makes no claim about it beyond what these checks measured.