UK Data: England river and tide levels
REMOTE · UKDATA.RELINESS.CO.UK
Live Environment Agency river levels, flows, rainfall and tide gauges across England
Available components
Last scanned (14 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Maps and Location
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 Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability71
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +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.
- 18 Nov 26 +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.
- 16 Nov 26 +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.
- 14 Nov 26 +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.
- 12 Nov 26 +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.
- 10 Nov 26 +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.
- 8 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 7 Nov 26 68
First indexed and scored.
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 21 Nov 2026 · Probed https://ukdata.reliness.co.uk/mcp/uk-water-levels
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=reliness.co.uk | CN=WE1,O=Google Trust Services,C=US | 4 Nov 2026 | 2 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | f1d4f4e9f24c919b0e13c306162294a4 |
| SANs: reliness.co.uk, ukdata.reliness.co.uk, *.ukdata.reliness.co.uk | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ukdata.reliness.co.uk. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| uk. | DS published | 43876 | 8 | Verified |
| co.uk. | DS published | 11810 | 8 | Verified |
| reliness.co.uk. | No DS | 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 |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ukdata.reliness.co.uk/mcp/uk-water-levels | Verified | 200 | |
| http (plaintext) | http://ukdata.reliness.co.uk/mcp/uk-water-levels | Served over HTTP | 200 |
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 →
rainfall_last_24h ~201
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)
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
river_flow_now ~219
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)
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
river_level_history ~195
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)
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
river_level_now ~142
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)
| Name | Type | Req | Description |
|---|---|---|---|
| station_id | string | – | string, required, Environment Agency station reference, e.g. 2200TH (Reading); find ids with river_levels_near |
No output schema declared.
No examples provided.
river_level_record ~117
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)
| Name | Type | Req | Description |
|---|---|---|---|
| station_id | string | – | string, required, Environment Agency station reference, e.g. 1491TH (Kings Mill, Oxford) |
No output schema declared.
No examples provided.
river_stations_on_river ~204
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)
| Name | Type | Req | Description |
|---|---|---|---|
| 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" |
No output schema declared.
No examples provided.
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.
remote · ukdata.reliness.co.uk
claude mcp add --transport http uk-co-reliness-uk-water-levels 'https://ukdata.reliness.co.uk/mcp/uk-water-levels'
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.