Uk Flood Monitoring
NPM · @PIPEWORX/MCP-UK-FLOOD-MONITORING · 2 COMPONENTS
UK Environment Agency real-time flood-monitoring MCP.
Available components
Last scanned (14 hours ago)
Scores higher than 72% of npm servers
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-uk-flood-monitoring). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1029 tokens (~257/item across 4 items; 4 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 Management23
- Stability observed for 7 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +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.
- 29 Oct 26 79
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-uk-flood-monitoring@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-uk-flood-monitoring |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-uk-flood-monitoring/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3560638665 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:f4a411af803461e73b785df540b85b8351a478c0cf57c55aed327d7d934f5bb6b646569201fbcd98dc149a711a80c0e5d456bca95123171bc30e94d72 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
ukflood_areas ~254
The named flood areas the Environment Agency issues warnings for — the geography behind a warning code. Each area has an fwdCode (e.g. "053FWFPUWI06"), a plain description of the land it covers, its county, EA operational area, the river or sea concerned, a centroid and a quick-dial number. Filter by county or search the description text. Use this to turn a warning code from ukflood_warnings into a place, or to find the code for a place before a flood happens.
| Name | Type | Req | Description |
|---|---|---|---|
| county | string | – | County filter as the EA spells it, e.g. "Lincolnshire". |
| latitude | number | – | Optional latitude for a radius search, e.g. 53.22. |
| limit | number | – | Max areas to return (default 25, max 200). |
| longitude | number | – | Optional longitude for a radius search, e.g. -0.55. |
| radius_km | number | – | Radius in kilometres when latitude/longitude are given (default 15, max 100). |
| search | string | – | Case-insensitive substring matched against the area label, description and river name, e.g. "Thames". |
No output schema declared.
No examples provided.
ukflood_station_readings ~218
Telemetry readings from one Environment Agency monitoring station — water level in metres, river flow in m3/s, or rainfall in mm, typically every 15 minutes. AUTHORITATIVE for "how high is the <English river> at <place> right now". Pass a station reference from ukflood_stations_near, e.g. "5380TH" (Walthamstow, Low Hall, River Lee). Defaults to the latest reading for every measure at the station; pass since to get a time series.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max readings to return (default 50, max 500). Only applies with since. |
| since | string | – | Optional ISO-8601 timestamp, e.g. "2026-09-16T00:00:00Z". When given, returns every reading since then instead of only the latest. |
| station_id | string | yes | EA station reference, e.g. "5380TH". Get one from ukflood_stations_near. |
No output schema declared.
No examples provided.
ukflood_stations_near ~249
Environment Agency river, groundwater, tidal and rainfall monitoring stations near a point in England, with the measures each one reports. Use this to find the station id you then pass to ukflood_station_readings. Returns station reference, label, river and catchment name, town, coordinates and the parameter/unit of every measure at that station. Example: latitude 51.5, longitude -0.12, radius_km 10 for central London.
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | – | Latitude in decimal degrees, e.g. 51.5 (London). |
| limit | number | – | Max stations to return (default 20, max 100). |
| longitude | number | – | Longitude in decimal degrees, e.g. -0.12 (London). |
| parameter | string | – | Optional measure filter: "level" (water level), "flow" (river discharge), "rainfall", "temperature", "wind". Omit for all. |
| radius_km | number | – | Search radius in kilometres (default 10, max 100). |
| river | string | – | Optional river name filter, e.g. "River Thames". Can be used without coordinates. |
No output schema declared.
No examples provided.
ukflood_warnings ~249
Flood warnings and flood alerts currently in force across England, from the Environment Agency. AUTHORITATIVE for "is there a flood warning in <English place>" — this is the feed the government broadcasts from, not a model. Returns each warning with its severity (Severe Flood Warning / Flood Warning / Flood Alert), the named flood area, county, river or sea, the EA message text and when it was last changed, plus a count by severity. A quiet day legitimately returns zero warnings in force; the severity counts are still returned so you can tell "nothing is happening" from "the call failed". Covers England only — Wales (NRW), Scotland (SEPA) and Northern Ireland publish elsewhere.
| Name | Type | Req | Description |
|---|---|---|---|
| county | string | – | Optional county filter, exactly as the EA spells it, e.g. "Lincolnshire", "Somerset". |
| limit | number | – | Max warnings to return (default 50, max 200). |
| min_severity | number | – | Lowest severity to include: 1 Severe Flood Warning, 2 Flood Warning, 3 Flood Alert, 4 also include warnings no longer in force. Default 3 (all live warnings and alerts). |
No output schema declared.
No examples provided.
How do I install the Uk Flood Monitoring MCP server?
Uk Flood Monitoring runs locally as an npm package, launched with npx -y @pipeworx/mcp-uk-flood-monitoring. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-uk-flood-monitoring
claude mcp add pipeworx-io-uk-flood-monitoring -- npx -y @pipeworx/mcp-uk-flood-monitoring
What is the Uk Flood Monitoring MCP server?
Uk Flood Monitoring is an MCP server listed in the public MCP registry as io.github.pipeworx-io/uk-flood-monitoring. UK Environment Agency real-time flood-monitoring MCP. This page covers its npm package (@pipeworx/mcp-uk-flood-monitoring).
Is the Uk Flood Monitoring MCP server safe to use?
Uk Flood Monitoring scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Flood Monitoring MCP server expose?
Uk Flood Monitoring exposes 4 tools: ukflood_warnings, ukflood_stations_near, ukflood_station_readings, ukflood_areas. Their descriptions and schemas cost roughly 970 tokens of context every time the server is loaded.
Is the Uk Flood Monitoring MCP server still maintained?
Uk Flood Monitoring is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Uk Flood Monitoring MCP server under?
Uk Flood Monitoring declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.