Hydrata - ANUGA Flood Simulation
REMOTE · HYDRATA.COM · SCANNED SEP 20
Run ANUGA flood simulations, track progress, and retrieve results on Hydrata Cloud.
Available components
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 844 tokens (~93/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Hydrata - ANUGA Flood Simulation MCP server?
Hydrata - ANUGA Flood Simulation is a hosted endpoint at https://hydrata.com/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · hydrata.com
claude mcp add --transport http com-hydrata-hydrata-mcp-server 'https://hydrata.com/mcp/'
{
"mcpServers": {
"com-hydrata-hydrata-mcp-server": {
"url": "https://hydrata.com/mcp/"
}
}
} {
"servers": {
"com-hydrata-hydrata-mcp-server": {
"type": "http",
"url": "https://hydrata.com/mcp/"
}
}
} [mcp_servers.com-hydrata-hydrata-mcp-server] url = "https://hydrata.com/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-hydrata-hydrata-mcp-server": {
"type": "remote",
"url": "https://hydrata.com/mcp/",
"enabled": true
}
}
} openclaw mcp add com-hydrata-hydrata-mcp-server --url 'https://hydrata.com/mcp/' --transport streamable-http
mcp_servers:
com-hydrata-hydrata-mcp-server:
url: "https://hydrata.com/mcp/" {
"McpServers": {
"com-hydrata-hydrata-mcp-server": {
"Transport": "http",
"Url": "https://hydrata.com/mcp/"
}
}
} assistant mcp add com-hydrata-hydrata-mcp-server -t streamable-http -u 'https://hydrata.com/mcp/'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Aug 26 0
- The server no longer declares the “experimental” capability functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://hydrata.com/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hydrata.com | CN=YR1,O=Let's Encrypt,C=US | 28 Jul 2026 | 26 Oct 2026 | RSA 2048 | SHA256-RSA | 5e401bc31e8c0beb3e43797b662cf317334 |
| SANs: backlog.hydrata.com, hydrata.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of hydrata.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| hydrata.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| content-security-policy | frame-ancestors 'self' https://hydrata.com https://www.bmwhi.org https://bmwhi.org https://hydrata.com https://theswamm.com; |
| permissions-policy | camera=(), microphone=(), geolocation=(self), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hydrata.com/mcp/ | Verified | 200 | |
| http (plaintext) | http://hydrata.com/mcp/ | HTTPS enforced | 301 | https://hydrata.com/mcp/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cancel_run ~82
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).
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | integer | yes | The run ID to cancel |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_project ~50
Get details of a specific ANUGA project including its scenarios. Returns the project name, projection (EPSG code), base map ID, and configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | integer | yes | The project ID |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_run ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | integer | yes | The run ID |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_run_status ~84
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.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | integer | yes | The run ID |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
get_scenario ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | integer | yes | The project ID |
| scenario_id | integer | yes | The scenario ID |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_projects ~70
List ANUGA simulation projects accessible to the authenticated user. Returns a paginated list of projects with their names, projections, and base map references.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (default 1) |
| page_size | integer | – | Results per page, max 100 (default 100) |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_runs ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number (default 1) |
| page_size | integer | – | Results per page, max 100 (default 100) |
| project_id | integer | yes | The project ID |
| status_filter | – | – | Filter by status: created, building, built, queued, computing, processing, complete, error, cancelled. Omit for all. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
retry_run ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| run_id | integer | yes | The run ID to retry |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
start_simulation ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| compute_backend | string | – | Compute backend: 'local' (Celery), 'ec2' (dedicated instance), or 'batch' (AWS Batch spot, cheapest). Default: 'local' |
| scenario_id | integer | yes | The scenario ID to run |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the Hydrata - ANUGA Flood Simulation MCP server?
Hydrata - ANUGA Flood Simulation is an MCP server listed in the public MCP registry as com.hydrata/hydrata-mcp-server. Run ANUGA flood simulations, track progress, and retrieve results on Hydrata Cloud. This page covers its hosted endpoint (https://hydrata.com/mcp/).
Is the Hydrata - ANUGA Flood Simulation MCP server safe to use?
Hydrata - ANUGA Flood Simulation scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Hydrata - ANUGA Flood Simulation MCP server expose?
Hydrata - ANUGA Flood Simulation exposes 9 tools: list_projects, get_project, get_scenario, start_simulation, get_run_status, and 4 more. Their descriptions and schemas cost roughly 785 tokens of context every time the server is loaded.
Does the Hydrata - ANUGA Flood Simulation MCP server require authentication?
No. We connected to Hydrata - ANUGA Flood Simulation without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Hydrata - ANUGA Flood Simulation MCP server still maintained?
Hydrata - ANUGA Flood Simulation is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.