Connect Hydrata - ANUGA Flood Simulation and your agent gets 9 tools, among them cancel_run, get_project, get_run. It answers at https://hydrata.com/mcp/ over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 5 September 2026; the last check, on 18 October 2026, succeeded.
Run ANUGA flood simulations, track progress, and retrieve results on Hydrata Cloud.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
cancel_run | Cancel an in-flight simulation run. Works on runs in built, queued, or computing status. Cleans up compute resources (terminates EC2 instance, Celery task, or Batch job). Returns 409 if the run is already in a terminal state (complete, canc Inputs: run_id |
get_project | Get details of a specific ANUGA project including its scenarios. Returns the project name, projection (EPSG code), base map ID, and configuration. Inputs: project_id |
get_run | Get full details of a simulation run including timing and results. Returns the complete run record: status, progress, timing (start/end timestamps, duration), compute details (backend, instance type, cost), mesh info, error messages, and re Inputs: run_id |
get_run_status | Lightweight status check for a simulation run (fast, <50ms). Use this for polling instead of get_run. Returns only: id, status, progress_pct (0-100), eta_seconds, error_message, and compute_backend. Poll every 5-10 seconds. Terminal states: Inputs: run_id |
get_scenario | Get scenario details including its current status and latest run. The status field is computed from the latest run and will be one of: created, building, built, queued, computing, processing, complete, error, or cancelled. A scenario must b Inputs: project_id, scenario_id |
list_projects | List ANUGA simulation projects accessible to the authenticated user. Returns a paginated list of projects with their names, projections, and base map references. Inputs: page, page_size |
list_runs | List all simulation runs across all scenarios in a project. Returns a paginated list of runs. Optionally filter by status to find active, completed, or failed runs. Inputs: project_id, status_filter, page, page_size |
retry_run | Retry a failed simulation run. Resets an errored run back to 'created' status and triggers a new package build. The same run ID is reused. Only valid when status is 'error'. Returns 409 for any other state. Inputs: run_id |
start_simulation | Start a flood simulation run for a built scenario. The scenario must be in 'built' status. Returns 202 with the new run. The run transitions through: built → queued → computing → processing → complete. After starting, poll get_run_status to Inputs: scenario_id, compute_backend |
Every block below points at https://hydrata.com/mcp/. Pick your client and copy.
claude mcp add --transport http hydrata-anuga-flood-simulation https://hydrata.com/mcp/
{
"mcpServers": {
"hydrata-anuga-flood-simulation": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://hydrata.com/mcp/"]
}
}
}{
"mcpServers": {
"hydrata-anuga-flood-simulation": {
"url": "https://hydrata.com/mcp/"
}
}
}{
"servers": {
"hydrata-anuga-flood-simulation": {
"type": "http",
"url": "https://hydrata.com/mcp/"
}
}
}{
"context_servers": {
"hydrata-anuga-flood-simulation": {
"url": "https://hydrata.com/mcp/"
}
}
}{
"mcpServers": {
"hydrata-anuga-flood-simulation": {
"serverUrl": "https://hydrata.com/mcp/"
}
}
}{
"mcpServers": {
"hydrata-anuga-flood-simulation": {
"url": "https://hydrata.com/mcp/"
}
}
}name: Hydrata - ANUGA Flood Simulation
version: 0.0.1
schema: v1
mcpServers:
- name: Hydrata - ANUGA Flood Simulation
type: streamable-http
url: https://hydrata.com/mcp/{
"mcpServers": {
"hydrata-anuga-flood-simulation": {
"httpUrl": "https://hydrata.com/mcp/"
}
}
}{
"mcpServers": {
"hydrata-anuga-flood-simulation": {
"type": "http",
"url": "https://hydrata.com/mcp/"
}
}
}{
"mcpServers": {
"hydrata-anuga-flood-simulation": {
"url": "https://hydrata.com/mcp/"
}
}
}goose://extension?url=https%3A%2F%2Fhydrata.com%2Fmcp%2F&type=streamable_http&id=hydrata-anuga-flood-simulation&name=Hydrata%20-%20ANUGA%20Flood%20Simulation
It answered our last check on 18 October 2026 in 588 ms. Over 10 checks since 5 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by hydrata.com and served from hydrata.com, the vendor's own domain: https://hydrata.com/mcp/.
9, as returned by the server's own tools/list on 31 August 2026: cancel_run, get_project, get_run, get_run_status, get_scenario, list_projects, list_runs, retry_run, and 1 more.
It answered our last check on 18 October 2026 in 588 ms. Over 10 checks since 5 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://hydrata.com/mcp/. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.hydrata. Endpoint host: hydrata.com. ARD identifier: urn:air:com.hydrata:mcp:hydrata-mcp-server.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.