# Uk Flood Monitoring (npm · @pipeworx/mcp-uk-flood-monitoring) UK Environment Agency real-time flood-monitoring MCP. - Trust score: 82/100 (high trust) - Change this week: +3 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-05 ## Components - remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-uk-flood-monitoring/uk-flood-monitoring-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-uk-flood-monitoring/uk-flood-monitoring-mcp) - npm · `@pipeworx/mcp-uk-flood-monitoring`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-uk-flood-monitoring/pipeworx-mcp-uk-flood-monitoring.md), [page](https://verifymcp.io/servers/pipeworx-io-uk-flood-monitoring/pipeworx-mcp-uk-flood-monitoring) ## Channel facts - Registry: `npm` - Package: `@pipeworx/mcp-uk-flood-monitoring` - Version: `0.2.0` - Transport: `stdio` ## Trust breakdown 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. 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-05. - **Supply Chain Security**: 100/100 - No malware found by supply-chain analysis. - No known CVEs affecting this package version or its production dependencies. - No install/post-install scripts declared. - No production dependencies, so there is no dependency health to assess. - **Provenance & Transparency**: 97/100 - Source repository is publicly reachable at the declared URL. - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-uk-flood-monitoring). - Clear OSI-approved license (MIT). - Actively maintained (last published 6 days ago). - Disclosure check failed: no security disclosure policy was found in the source repository. - **Schema Quality & AI Usability**: 63/100 - AI-judged instruction clarity (excellent). - 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. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 23/100 - Stability observed for 7 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 5 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 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. ### Claude ```bash claude mcp add pipeworx-io-uk-flood-monitoring -- npx -y @pipeworx/mcp-uk-flood-monitoring ``` ### Cursor ```json { "mcpServers": { "pipeworx-io-uk-flood-monitoring": { "command": "npx", "args": [ "-y", "@pipeworx/mcp-uk-flood-monitoring" ] } } } ``` ### VS Code ```json { "servers": { "pipeworx-io-uk-flood-monitoring": { "command": "npx", "args": [ "-y", "@pipeworx/mcp-uk-flood-monitoring" ] } } } ``` ### Codex ```bash codex mcp add pipeworx-io-uk-flood-monitoring -- npx -y @pipeworx/mcp-uk-flood-monitoring ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "pipeworx-io-uk-flood-monitoring": { "type": "local", "command": [ "npx", "-y", "@pipeworx/mcp-uk-flood-monitoring" ], "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add pipeworx-io-uk-flood-monitoring --command npx --arg -y --arg @pipeworx/mcp-uk-flood-monitoring ``` ### Hermes ```yaml mcp_servers: pipeworx-io-uk-flood-monitoring: command: "npx" args: ["-y", "@pipeworx/mcp-uk-flood-monitoring"] ``` ### Netclaw ```json { "McpServers": { "pipeworx-io-uk-flood-monitoring": { "Transport": "stdio", "Command": "npx", "Arguments": [ "-y", "@pipeworx/mcp-uk-flood-monitoring" ] } } } ``` ### Vellum ```bash assistant mcp add pipeworx-io-uk-flood-monitoring -t stdio -c npx -a -y @pipeworx/mcp-uk-flood-monitoring ``` ### Other ```json { "mcpServers": { "pipeworx-io-uk-flood-monitoring": { "command": "npx", "args": [ "-y", "@pipeworx/mcp-uk-flood-monitoring" ] } } } ``` ## 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-04 (score 82, +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. ### 2026-11-02 (score 81, +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. ### 2026-10-31 (score 80, +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-10-29 (score 79) First indexed and scored. ## MCP tools (4) ### `ukflood_warnings` (~249 tokens) Flood warnings and flood alerts currently in force across England, from the Environment Agency. AUTHORITATIVE for "is there a flood warning in " — 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. Input parameters: - `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). ### `ukflood_stations_near` (~249 tokens) 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. Input parameters: - `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. ### `ukflood_station_readings` (~218 tokens) 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 at 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. Input parameters: - `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, required): EA station reference, e.g. "5380TH". Get one from ukflood_stations_near. ### `ukflood_areas` (~254 tokens) 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. Input parameters: - `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". ## Diagnostics Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-uk-flood-monitoring/pipeworx-mcp-uk-flood-monitoring#diagnostics ## Score history - 2026-11-05: 82 - 2026-11-04: 82 - 2026-11-03: 81 - 2026-11-02: 81 - 2026-11-01: 80 - 2026-10-31: 80 - 2026-10-30: 79 - 2026-10-29: 79 ## Common questions ### 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. ## Links - npm package: https://www.npmjs.com/package/@pipeworx/mcp-uk-flood-monitoring - Socket report: https://socket.dev/npm/package/@pipeworx/mcp-uk-flood-monitoring - Repository: https://github.com/pipeworx-io/mcp-uk-flood-monitoring - Website: https://pipeworx.io/packs/uk-flood-monitoring - Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-uk-flood-monitoring/pipeworx-mcp-uk-flood-monitoring.xml - Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-uk-flood-monitoring/pipeworx-mcp-uk-flood-monitoring.json - HTML version of this page: https://verifymcp.io/servers/pipeworx-io-uk-flood-monitoring/pipeworx-mcp-uk-flood-monitoring