Developer · Remote MCP server

Hydrata - ANUGA Flood Simulation

Run ANUGA flood simulations, track progress, and retrieve results on Hydrata Cloud.

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
com.hydrata/hydrata-mcp-server
Version
0.2.0
Status
Active
Category
developer
Transport
Streamable HTTP
Published
2026-09-21
Updated
2026-09-21
Publisher
com.hydrata
Namespace
Namespace verified by the MCP Registry via the domain hydrata.com · how
Repository
github.com/Hydrata/hydrata-mcp-server
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
Streamable HTTPhttps://hydrata.com/mcp/None

Live check

This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.

Reachable
Yes (HTTP 200)
Handshake
Hydrata 4.0.5 · protocol 2025-06-18
Tools discovered
17 - show nameslist_projects, get_project, get_scenario, start_simulation, get_run_status, get_run, cancel_run, retry_run, list_runs, create_project, presign_terrain_upload, finalize_terrain_upload, get_terrain, create_time_series, attach_input_layer, create_scenario, build_scenario
Checked on
2026-10-05

How the live check works

How to connect Hydrata - ANUGA Flood Simulation

Hydrata - ANUGA Flood Simulation is a remote MCP server: there is nothing to install. Its endpoint is https://hydrata.com/mcp/, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More developer servers

All 5,152 →
ServerRunsEndpoint or package
HwatuVerification browser for coding agents: headless WebKit, DOM eval, screenshots, pixel-diff.Local · stdioMCP Bundle (.mcpb): hongnoul/hwatu/releases/download/v0.6.0/hwatu-mc
HwcontractJudge hardware timing/serial against a contract: pass/marginal/fail (WS2812, DShot, logs)Local · stdioPyPI: hwcontract
hybridlogReads your own Garmin mirror: readiness, training load, muscle freshness, and read-only SQL.Remote & Local · HTTP, stdiox
HydraDNSManage a self-hosted DNS firewall: block domains, create policies, read query logs and metrics.Local · stdioOCI image (Docker): ghcr.io/hydradns/hydra-cli:0.1.0
Hyperframesrender MCPA paid remote MCP for HyperFrames, built to return verdicts, receipts, usage logs, and audit-ready J.Remote · HTTPLive check: ✗ no handshakehyperframesrender.clauxel.com
Hyperliquid Agent GatewayRead-only MCP gateway to Hyperliquid: liquidation distance, funding carry, HyperEVM flows. No keys.Local · stdioPyPI: hyperliquid-agent-gateway
Hypermnesia MCP VizRead-only visualization for Cortex memory, knowledge, sessions, traces, and codebase graphs.Local · stdioPyPI: hypermnesia-mcp-viz
HyperpingUptime, API and server monitoring with outages, reporting, on-call and status pages.Remote · HTTPLive check: ✓ handshakeapi.hyperping.io