# Hydrata - ANUGA Flood Simulation (remote · hydrata.com)

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

- Trust score: 67/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `hydrata.com`: 67/100 (this document), [markdown](https://verifymcp.io/servers/com-hydrata-hydrata-mcp-server/hydrata.md), [page](https://verifymcp.io/servers/com-hydrata-hydrata-mcp-server/hydrata)

## Channel facts

- Endpoint: `https://hydrata.com/mcp/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 844 tokens (~93/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-hydrata-hydrata-mcp-server https://hydrata.com/mcp/
```

### Codex

```toml
[mcp_servers.com-hydrata-hydrata-mcp-server]
url = "https://hydrata.com/mcp/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-hydrata-hydrata-mcp-server": {
      "type": "remote",
      "url": "https://hydrata.com/mcp/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-hydrata-hydrata-mcp-server --url https://hydrata.com/mcp/ --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-hydrata-hydrata-mcp-server:
    url: "https://hydrata.com/mcp/"
```

### Other

```json
{
  "mcpServers": {
    "com-hydrata-hydrata-mcp-server": {
      "type": "http",
      "url": "https://hydrata.com/mcp/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 64, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 64)

First indexed and scored.

## MCP tools (9)

### `list_projects` (~70 tokens)

List ANUGA simulation projects accessible to the authenticated user.

Returns a paginated list of projects with their names, projections,
and base map references.

Input parameters:

- `page` (integer): Page number (default 1)
- `page_size` (integer): Results per page, max 100 (default 100)

Output parameters:

- `result` (string)

### `get_project` (~50 tokens)

Get details of a specific ANUGA project including its scenarios.

Returns the project name, projection (EPSG code), base map ID,
and configuration.

Input parameters:

- `project_id` (integer, required): The project ID

Output parameters:

- `result` (string)

### `get_scenario` (~92 tokens)

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.

Input parameters:

- `project_id` (integer, required): The project ID
- `scenario_id` (integer, required): The scenario ID

Output parameters:

- `result` (string)

### `start_simulation` (~132 tokens)

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.

Input parameters:

- `compute_backend` (string): Compute backend: 'local' (Celery), 'ec2' (dedicated instance), or 'batch' (AWS Batch spot, cheapest). Default: 'local'
- `scenario_id` (integer, required): The scenario ID to run

Output parameters:

- `result` (string)

### `get_run_status` (~84 tokens)

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.

Input parameters:

- `run_id` (integer, required): The run ID

Output parameters:

- `result` (string)

### `get_run` (~86 tokens)

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.

Input parameters:

- `run_id` (integer, required): The run ID

Output parameters:

- `result` (string)

### `cancel_run` (~82 tokens)

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).

Input parameters:

- `run_id` (integer, required): The run ID to cancel

Output parameters:

- `result` (string)

### `retry_run` (~71 tokens)

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.

Input parameters:

- `run_id` (integer, required): The run ID to retry

Output parameters:

- `result` (string)

### `list_runs` (~118 tokens)

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.

Input parameters:

- `page` (integer): Page number (default 1)
- `page_size` (integer): Results per page, max 100 (default 100)
- `project_id` (integer, required): The project ID
- `status_filter`: Filter by status: created, building, built, queued, computing, processing, complete, error, cancelled. Omit for all.

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-hydrata-hydrata-mcp-server/hydrata#diagnostics

## Score history

- 2026-08-03: 67
- 2026-08-02: 67
- 2026-08-01: 66
- 2026-07-31: 66
- 2026-07-30: 66
- 2026-07-29: 66
- 2026-07-28: 65
- 2026-07-27: 64
- 2026-07-26: 64

## Links

- Remote endpoint: https://hydrata.com/mcp/
- Repository: https://github.com/Hydrata/hydrata-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/com-hydrata-hydrata-mcp-server/hydrata/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-hydrata-hydrata-mcp-server/hydrata/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-hydrata-hydrata-mcp-server/hydrata