mcp server
Hydrata - ANUGA Flood Simulation
Run ANUGA flood simulations, track progress, and retrieve results on Hydrata Cloud.
Description as published by the maintainer. Source
- version 0.1.0
- slowing
slowing — Most recent push to the repository was 2026-03-01.
What this server can do
9 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
cancel_run(run_id)- 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, cancelled, or error). Required: run_id.
get_project(project_id)- Get details of a specific ANUGA project including its scenarios. Returns the project name, projection (EPSG code), base map ID, and configuration. Required: project_id.
get_run(run_id)- 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 result log. Use get_run_status for lightweight polling; use this for final results. Required: run_id.
get_run_status(run_id)- 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: complete, error, cancelled. Required: run_id.
get_scenario(project_id, scenario_id)- 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 be in 'built' status before it can be run. Required: project_id, scenario_id.
list_projects(page, page_size)- List ANUGA simulation projects accessible to the authenticated user. Returns a paginated list of projects with their names, projections, and base map references.
list_runs(page, page_size, project_id, status_filter)- 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. Required: project_id.
retry_run(run_id)- 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. Required: run_id.
start_simulation(scenario_id, compute_backend)- 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 track progress. Returns 409 if the scenario is not in the correct state. Required: scenario_id.
Last successful function declaration observed on . Source: https://hydrata.com/mcp/. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://hydrata.com/mcp/.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 0 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-03-01 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 0 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 0.1.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-03-01 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | MIT | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-03-01 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub | |
| mcp tools declared | 9 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | hydrata.com | |
| mcp endpoint status | ok | The server listed 9 functions when asked. | as of probe | hydrata.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json