Hydrata - ANUGA Flood Simulation by hydrata.com
MCP server · Cloud & infrastructure · indexed, not reviewed
Hostedvendor's own
Not reviewed
No score, grade or rank. This listing is facts from the official MCP registry and our own checks, and it stays out of the rankings until the panel reviews it.
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/- GitHub stars
- 1
- Registry entry
- updated 21 Sep 2026
From the official MCP registry, the package registries and our own checks. JSON · Markdown
Why it's listed
- It's published in the registry under hydrata.com, a namespace the registry only gives to whoever proves they control that domain.
Being indexed says nothing about quality, and nobody can pay for it. Is this yours? Ask for a review.
Tools it lists 17 · about 6,814 tokens of context · checked 1 hour ago
| Tool | What it does | Hint |
|---|---|---|
list_projectsList Projects | List ANUGA simulation projects accessible to the authenticated user. Returns a paginated list of projects with their names, projections, and base map references. | |
get_projectGet Project | Get details of a specific ANUGA project including its scenarios. Returns the project name, projection (EPSG code), base map ID, and configuration. | |
get_scenarioGet 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 latest run and will be one of: created, building, built,… | |
start_simulationStart 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,… | |
get_run_statusGet 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… | |
get_runGet 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,… | |
cancel_runCancel 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… | |
retry_runRetry 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. | |
list_runsList 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. | |
create_projectCreate 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 scenario in the project is meshed and run in — pick the UTM… | |
presign_terrain_uploadPresign 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, PUT the file straight to `upload_url`, sending the SAME… | |
finalize_terrain_uploadFinalize 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 Terrain row (status `creating`) and queues the import chain —… | |
get_terrainGet 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`, `not_found` (the project has no terrain yet; an unknown terrain_id… | |
create_time_seriesCreate Time Series | Create a time series (rain gauge, hydrograph, tide/stage) in a project. POSTs /projects/<id>/time-series/ with `series_type` and `units` as top-level fields. `series_type` is checked against the four choices and `data`… | |
attach_input_layerAttach 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: first upload the GeoJSON yourself, with the same credential, to… | |
create_scenarioCreate Scenario | Create a DRAFT scenario (no build, no run) and report its mesh-triangle estimate. POSTs /projects/<id>/scenarios/ with the write fields, then GETs the scenario detail — the create response carries NO estimate; the… | |
build_scenarioBuild 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 is spent: 1. GET the scenario detail. A record with no… |
What https://hydrata.com/mcp/ answered to tools/list, asked without credentials over MCP 2026-07-28. The token figure is the size of the list as sent, divided by four; a model sees about that much before it calls anything. Full definitions, input schemas included, are in the listing's JSON under mcpTools.
How its tools read to an agent 0 errors · 19 warnings · 0 notes
- warnTC07build_scenariothe description is about 812 tokens
- warnTC13create_time_seriesdata (object with no properties)
- warnTC16attach_input_layerno readOnlyHint or destructiveHint
- warnTC16build_scenariono readOnlyHint or destructiveHint
- warnTC16cancel_runno readOnlyHint or destructiveHint
- warnTC16create_projectno readOnlyHint or destructiveHint
- warnTC16create_scenariono readOnlyHint or destructiveHint
- warnTC16create_time_seriesno readOnlyHint or destructiveHint
- warnTC16finalize_terrain_uploadno readOnlyHint or destructiveHint
- warnTC16get_projectno readOnlyHint or destructiveHint
- warnTC16get_runno readOnlyHint or destructiveHint
- warnTC16get_run_statusno readOnlyHint or destructiveHint
- warnTC16get_scenariono readOnlyHint or destructiveHint
- warnTC16get_terrainno readOnlyHint or destructiveHint
- warnTC16list_projectsno readOnlyHint or destructiveHint
- warnTC16list_runsno readOnlyHint or destructiveHint
- warnTC16presign_terrain_uploadno readOnlyHint or destructiveHint
- warnTC16retry_runno readOnlyHint or destructiveHint
- warnTC16start_simulationno readOnlyHint or destructiveHint
The checks from /check and anchor check, run each day on the list above: about 6,814 tokens of definitions. Not part of the score yet. Check your own server.