Remote MCP · Endpoint

Hydrata - ANUGA Flood Simulation MCP server

No — it is up, but it requires credentials. Hydrata - ANUGA Flood Simulation answered 1 hour ago with an authentication challenge rather than a session.

Auth requiredLast checked 1 hour ago

Server URL

https://hydrata.com/mcp/

The endpoint is answering and asked us for credentials. That is a working server, not an outage.

Registry name
com.hydrata/hydrata-mcp-server
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
28 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Run ANUGA flood simulations, track progress, and retrieve results on Hydrata Cloud.
Website
https://hydrata.com/docs/mcp/
Repository
https://github.com/Hydrata/hydrata-mcp-server
Listing
From the official MCP registry (active).
Recent checks of Hydrata - ANUGA Flood Simulation
CheckedResultHandshake
1 hour agoCredentials required—
18 hours agoCredentials required—
2 days agoCredentials required—
3 days agoCredentials required—
4 days agoCredentials required—
5 days agoCredentials required—
6 days agoCredentials required—
7 days agoCredentials required—
10 days agoCredentials required—
13 days agoCredentials required—
15 days agoHandshake completed244 ms
17 days agoHandshake completed217 ms
19 days agoHandshake completed213 ms
21 days agoHandshake completed211 ms
23 days agoHandshake completed212 ms
25 days agoHandshake completed248 ms
27 days agoHandshake completed218 ms
28 days agoHandshake completed215 ms
29 days agoHandshake completed275 ms

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

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 Hydrata - ANUGA Flood Simulation and makes no claim about it beyond what these checks measured.