# UK Data: England river and tide levels (remote · ukdata.reliness.co.uk)

Live Environment Agency river levels, flows, rainfall and tide gauges across England

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

## Components

- remote · `ukdata.reliness.co.uk`: 75/100 (this document), [markdown](https://verifymcp.io/servers/uk-co-reliness-uk-water-levels/mcp-uk-water-levels.md), [page](https://verifymcp.io/servers/uk-co-reliness-uk-water-levels/mcp-uk-water-levels)

## Channel facts

- Endpoint: `https://ukdata.reliness.co.uk/mcp/uk-water-levels`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.5.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-11-21.

- **Endpoint Security**: 69/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1078 tokens (~179/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the UK Data: England river and tide levels MCP server?

UK Data: England river and tide levels is a hosted endpoint at https://ukdata.reliness.co.uk/mcp/uk-water-levels, 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.

### Claude

```bash
claude mcp add --transport http uk-co-reliness-uk-water-levels 'https://ukdata.reliness.co.uk/mcp/uk-water-levels'
```

### Cursor

```json
{
  "mcpServers": {
    "uk-co-reliness-uk-water-levels": {
      "url": "https://ukdata.reliness.co.uk/mcp/uk-water-levels"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "uk-co-reliness-uk-water-levels": {
      "type": "http",
      "url": "https://ukdata.reliness.co.uk/mcp/uk-water-levels"
    }
  }
}
```

### Codex

```toml
[mcp_servers.uk-co-reliness-uk-water-levels]
url = "https://ukdata.reliness.co.uk/mcp/uk-water-levels"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "uk-co-reliness-uk-water-levels": {
      "type": "remote",
      "url": "https://ukdata.reliness.co.uk/mcp/uk-water-levels",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add uk-co-reliness-uk-water-levels --url 'https://ukdata.reliness.co.uk/mcp/uk-water-levels' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  uk-co-reliness-uk-water-levels:
    url: "https://ukdata.reliness.co.uk/mcp/uk-water-levels"
```

### Netclaw

```json
{
  "McpServers": {
    "uk-co-reliness-uk-water-levels": {
      "Transport": "http",
      "Url": "https://ukdata.reliness.co.uk/mcp/uk-water-levels"
    }
  }
}
```

### Vellum

```bash
assistant mcp add uk-co-reliness-uk-water-levels -t streamable-http -u 'https://ukdata.reliness.co.uk/mcp/uk-water-levels'
```

### Other

```json
{
  "mcpServers": {
    "uk-co-reliness-uk-water-levels": {
      "type": "http",
      "url": "https://ukdata.reliness.co.uk/mcp/uk-water-levels"
    }
  }
}
```

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-11-21 (score 75, +1)

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

### 2026-11-18 (score 74, +1)

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

### 2026-11-16 (score 73, +1)

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

### 2026-11-14 (score 72, +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-11-12 (score 71, +1)

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

### 2026-11-10 (score 70, +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-11-08 (score 69, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-07 (score 68)

First indexed and scored.

## MCP tools (6)

### `river_level_now` (~142 tokens)

Latest water level at one Environment Agency gauge, compared with its typical range (low, normal or high), plus the latest flow where the gauge measures it. Useful for boaters, anglers and residents asking whether the river is high right now. Source: Environment Agency real-time flood-monitoring API; readings are usually 15 minutes apart and old readings are flagged stale. Level is a gauge height, not water depth, and this is not a flood warning service. (cost: 1 credit)

Input parameters:

- `station_id` (string): string, required, Environment Agency station reference, e.g. 2200TH (Reading); find ids with river_levels_near

### `river_level_history` (~195 tokens)

River level readings at one gauge since a time (default the last 24 hours, up to 7 days back), with the lowest and highest point, change since the start and whether the river is rising, falling or steady over the last hour. Answers "has the river peaked yet" for flood watchers and anglers. Source: Environment Agency real-time flood-monitoring API. The series is thinned to a manageable number of points; it is not a forecast. (cost: 1 credit)

Input parameters:

- `points` (string): integer, optional, max points in the returned series, 2-100, default 24
- `since` (string): string, optional, ISO date-time (UTC if no offset) or YYYY-MM-DD within the last 7 days, default 24 hours ago
- `station_id` (string): string, required, Environment Agency station reference, e.g. 2200TH

### `river_stations_on_river` (~204 tokens)

Lists the Environment Agency level gauges on a named river in England (for example River Thames or River Severn) with station ids, towns and coordinates. Useful for boaters planning a trip or anyone following a river downstream. Source: Environment Agency real-time flood-monitoring API. The upstream name match is exact, so if nothing matches the tool retries once as "River <Name>" in title case (e.g. "thames" becomes "River Thames") and reports the name it used; other spellings are not guessed, and the list is not in upstream-to-downstream order. (cost: 1 credit)

Input parameters:

- `limit` (string): integer, optional, max stations returned, 1-100, default 25
- `river_name` (string): string, required, river name as the Environment Agency writes it, e.g. River Thames; "thames" or "river thames" is retried as "River Thames"

### `river_level_record` (~117 tokens)

Record high, record low and highest recent level at one Environment Agency gauge, with how far today's level is below the record. Answers "is this a record flood" for journalists, residents and property buyers. Source: Environment Agency real-time flood-monitoring API (station stage scale). Records only cover the years the gauge has operated, and some gauges publish none. (cost: 1 credit)

Input parameters:

- `station_id` (string): string, required, Environment Agency station reference, e.g. 1491TH (Kings Mill, Oxford)

### `river_flow_now` (~219 tokens)

Latest river flow in cubic metres per second (cumecs) at one gauge, or at the nearest flow gauges to a point. The number kayakers, canoeists and anglers ask for. Source: Environment Agency real-time flood-monitoring API. Pass station_id for one gauge, or lat and lon to search nearby; only some gauges measure flow, and readings older than 6 hours are flagged stale. (cost: 1 credit)

Input parameters:

- `dist_km` (number|string): number, optional, search radius in km, 0.5-50, default 15
- `lat` (number|string): number, optional, latitude (required if no station_id)
- `limit` (string): integer, optional, gauges returned when searching, 1-5, default 3
- `lon` (number|string): number, optional, longitude (required if no station_id)
- `station_id` (string): string, optional, Environment Agency station reference, e.g. 1490TH; use this or lat and lon

### `rainfall_last_24h` (~201 tokens)

How much rain fell over the last 24 hours (or up to 7 days) at the nearest working Environment Agency rain gauge, in millimetres, with the wettest 15 minutes and how complete the record is. Observed rainfall for gardeners, farmers, groundskeepers and anyone checking "how much rain did we get". Source: Environment Agency real-time flood-monitoring API (tipping-bucket gauges). It measures one point, not your exact location, and is not a forecast. (cost: 1 credit)

Input parameters:

- `dist_km` (number|string): number, optional, search radius in km, 0.5-50, default 10
- `hours` (string): integer, optional, hours to total back from now, 1-168, default 24
- `lat` (number|string): number, required, latitude (England)
- `lon` (number|string): number, required, longitude

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/uk-co-reliness-uk-water-levels/mcp-uk-water-levels#diagnostics

## Score history

- 2026-11-21: 75
- 2026-11-20: 74
- 2026-11-19: 74
- 2026-11-18: 74
- 2026-11-17: 73
- 2026-11-16: 73
- 2026-11-15: 72
- 2026-11-14: 72
- 2026-11-13: 71
- 2026-11-12: 71
- 2026-11-11: 70
- 2026-11-10: 70
- 2026-11-09: 69
- 2026-11-08: 69
- 2026-11-07: 68

## Common questions

### What is the UK Data: England river and tide levels MCP server?

UK Data: England river and tide levels is an MCP server listed in the public MCP registry as uk.co.reliness/uk-water-levels. Live Environment Agency river levels, flows, rainfall and tide gauges across England. This page covers its hosted endpoint (https://ukdata.reliness.co.uk/mcp/uk-water-levels).

### Is the UK Data: England river and tide levels MCP server safe to use?

UK Data: England river and tide levels scores 75 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 UK Data: England river and tide levels MCP server expose?

UK Data: England river and tide levels exposes 6 tools: river_level_now, river_level_history, river_stations_on_river, river_level_record, river_flow_now, rainfall_last_24h. Their descriptions and schemas cost roughly 1,078 tokens of context every time the server is loaded.

### Does the UK Data: England river and tide levels MCP server require authentication?

No. We connected to UK Data: England river and tide levels without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the UK Data: England river and tide levels MCP server still maintained?

UK Data: England river and tide levels is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the UK Data: England river and tide levels MCP server?

VerifyMCP ran 13 checks on UK Data: England river and tide levels, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://ukdata.reliness.co.uk/mcp/uk-water-levels
- Website: https://ukdata.reliness.co.uk/
- Changelog RSS feed: https://verifymcp.io/servers/uk-co-reliness-uk-water-levels/mcp-uk-water-levels.xml
- Changelog JSON feed: https://verifymcp.io/servers/uk-co-reliness-uk-water-levels/mcp-uk-water-levels/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/uk-co-reliness-uk-water-levels/mcp-uk-water-levels.json
- HTML version of this page: https://verifymcp.io/servers/uk-co-reliness-uk-water-levels/mcp-uk-water-levels
