Check warning areas and current alerts for England and Wales before reviewing local gauge readings. Compare listed sources, access requirements and evidence for uk flood warnings api.
These selections do not provide a single UK-wide warning feed; check Scotland and Northern Ireland separately.
Discover sources with MCP
Add this server to an HTTP-compatible MCP client, then call get_source to inspect the first source. The tool call is shown separately from the client configuration. Review upstream access details before requesting data.
Free open data; no authentication or registration; Open Government Licence (version 3 per licence URL in docs); attribution statement requested
Useful for
Use cases llm-inferred
Nearest river-level and flow gauge lookup for FRA baseline flow context · Historic level and flow readings via startdate/enddate for hydrological model calibration · Flood warning and flood area screening within a radius of a site (lat/long/dist filter) · Latest rainfall and level readings as a context check for drainage strategy studies
Labelled a trial/beta service; feedback requested · No service-level guarantee; should not be relied on for safety-critical applications · Does not replace the Agency's official channels for notifying the public of floods · Responses may be redirected at high load or in future versions; clients must follow standard HTTP redirects · Responses may be cached briefly; custom filtering reduces cache hits · Readings are sometimes updated in batches, so a complete history needs the since filter · Some endpoints impose a length limit by default; check the metadata limit and offset values · No rate limit documented; the docs recommend one call every 15 minutes (data/readings?latest) rather than crawling every station
A Model Context Protocol (MCP) server that provides access to the UK Environment Agency's Real Time Flood Monitoring API. This server allows you to access near real-time flood warnings, water level measurements, flow data, and monitoring station information.
What's in it
Data offered docs-verified
flood warnings and alerts with severity levels · flood areas · water level readings · flow readings · temperature readings · wind readings · monitoring station information · historical readings
Coverage docs-verified
UK per docs (ENTRY regions says England only; verify)
Update frequency docs-verified
every 15 minutes
Formats docs-verified
MCP stdio
Access docs-verified
Free/open: no API key or registration. Server code MIT; data under the Open Government Licence v3
Useful for
Use cases llm-inferred
Nearest-gauge river level and flow context for FRA baseline · Check live flood warnings and alerts for a site's catchment · Pull recent level and flow readings for hydrological baseline review · Locate monitoring stations within a set radius of a project site
No service level guarantee; not suitable for safety-critical applications · Upstream Environment Agency API is Beta · Responses may be cached for short periods · List tools capped at 500 items (default 50; readings default 100), 60 KB truncation; use limit/offset to paginate · Coverage conflict: docs say UK, ENTRY metadata says England
Which listed sources support UK flood warnings API?
Start with EA Flood Monitoring API, EA Flood MCP, NRW API portal. Check warning areas and current alerts for England and Wales before reviewing local gauge readings.
What should I check before using these sources for uk flood warnings api?
These selections do not provide a single UK-wide warning feed; check Scotland and Northern Ireland separately.
How do I inspect EA Flood Monitoring API through MCP?
Connect an MCP client to https://terramcp.earth/mcp and call get_source with slug ea-flood-monitoring-api. Review its provenance, access requirements and limitations before contacting the upstream service. Discovery does not make every listed source directly executable through the router.
Are these sources free and independently verified?
Access and licence terms belong to each upstream provider; some products require registration or payment. Open each listing for evidence, health status and enrichment provenance. A wrapper and its underlying API can refer to the same dataset and are not independent observations.