# Hydrata - ANUGA Flood Simulation (slim) > Hydrata - ANUGA Flood Simulation, an MCP server by hydrata.com, listed from the official MCP registry. Indexed, not reviewed: facts and our own checks, no score or ranking. Run ANUGA flood simulations, track progress, and retrieve results on Hydrata Cloud. - Full: https://www.anchorterminal.com/tools/hydrata-mcp-server.md (~1,600 tokens) · this version ~1,530 tokens · JSON https://www.anchorterminal.com/tools/hydrata-mcp-server.json · canonical https://www.anchorterminal.com/tools/hydrata-mcp-server - Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-05 # Hydrata - ANUGA Flood Simulation > Indexed, not reviewed: facts from the official MCP registry and our own checks. No score, grade or rank, and not in the rankings until the panel reviews it. How the index works: https://www.anchorterminal.com/indexed/ - Kind: MCP server, by hydrata.com (https://hydrata.com) - Category: Cloud & infrastructure (https://www.anchorterminal.com/categories/infrastructure.md) - Listed because: It's published in the registry under hydrata.com, a namespace the registry only gives to whoever proves they control that domain. - What the official MCP registry says: Run ANUGA flood simulations, track progress, and retrieve results on Hydrata Cloud. ## Facts - MCP registry: `com.hydrata/hydrata-mcp-server` 0.2.0 - Endpoint: https://hydrata.com/mcp/ (streamable HTTP) - Source: https://github.com/Hydrata/hydrata-mcp-server - GitHub stars: 1 - Registry entry updated: 2026-09-21 ## Tools - Tools it lists (17, about 6,814 tokens of context, `tools/list` without credentials over MCP 2026-07-28, checked 2026-10-04 22:23 UTC): - `list_projects`: List ANUGA simulation projects accessible to the authenticated user. Returns a paginated list of projects with their names, projections, and base map… - `get_project`: Get details of a specific ANUGA project including its scenarios. Returns the project name, projection (EPSG code), base map ID, and configuration. - `get_scenario`: Get scenario details including its `computed_status` and latest run. The `computed_status` field (there is NO `status` key on a scenario) is derived from the… - `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 →… - `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),… - `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),… - `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… - `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… - `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… - `create_project`: Create a new ANUGA project. Returns the project record including its id. The caller's own account becomes the owner. `projection` is the projected CRS every… - `presign_terrain_upload`: Step 1 of a terrain import: get a presigned S3 PUT URL for a GeoTIFF DEM. The agent moves the bytes itself — no tool accepts file contents. After this call,… - `finalize_terrain_upload`: Step 2 of a terrain import: register the PUT GeoTIFF as a Terrain and start the import. Call this only after the presigned PUT returned 200. Creates the… - `get_terrain`: Poll a terrain's import until it is `ready` (or `error`), bounded by timeout_seconds. Returns `outcome` — exactly one of `ready`, `error`, `timed_out`,… - `create_time_series`: Create a time series (rain gauge, hydrograph, tide/stage) in a project. POSTs /projects//time-series/ with `series_type` and `units` as top-level fields.… - `attach_input_layer`: Attach a GeoJSON you uploaded to GeoNode as the project's boundary, friction, inflow, rainfall, structure or mesh_region layer. The agent moves the bytes:… - `create_scenario`: Create a DRAFT scenario (no build, no run) and report its mesh-triangle estimate. POSTs /projects//scenarios/ with the write fields, then GETs the scenario… - `build_scenario`: Build a scenario's package (mesh + inputs) after showing what it will cost, and poll until built. Order of operations, so the number is shown before anything… - How its tools read to an agent (0 errors, 19 warnings, 0 notes, about 6,814 tokens; rules at https://www.anchorterminal.com/check.md; not part of the score): - warn TC07 build_scenario: the description is about 812 tokens - warn TC13 create_time_series: data (object with no properties) - warn TC16 attach_input_layer: no readOnlyHint or destructiveHint - warn TC16 build_scenario: no readOnlyHint or destructiveHint - warn TC16 cancel_run: no readOnlyHint or destructiveHint - warn TC16 create_project: no readOnlyHint or destructiveHint - warn TC16 create_scenario: no readOnlyHint or destructiveHint - warn TC16 create_time_series: no readOnlyHint or destructiveHint - warn TC16 finalize_terrain_upload: no readOnlyHint or destructiveHint - warn TC16 get_project: no readOnlyHint or destructiveHint - warn TC16 get_run: no readOnlyHint or destructiveHint - warn TC16 get_run_status: no readOnlyHint or destructiveHint - warn TC16 get_scenario: no readOnlyHint or destructiveHint - warn TC16 get_terrain: no readOnlyHint or destructiveHint - warn TC16 list_projects: no readOnlyHint or destructiveHint - warn TC16 list_runs: no readOnlyHint or destructiveHint - warn TC16 presign_terrain_upload: no readOnlyHint or destructiveHint - warn TC16 retry_run: no readOnlyHint or destructiveHint - warn TC16 start_simulation: no readOnlyHint or destructiveHint - JSON: https://www.anchorterminal.com/api/v1/tools/hydrata-mcp-server.json - Being indexed says nothing about quality, and nobody can pay for it. Ask for a review: https://www.anchorterminal.com/builders/#claiming