Inspect station metadata and quality-labelled time series before selecting rainfall, level or flow observations. Compare listed sources, access requirements and evidence for ea hydrology api.
A wrapper is a separate access route to upstream data, not an independent monitoring network.
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.
Hydrological station metadata and quality-labelled flow, level, groundwater and rainfall time series.
What's in it
Data offered docs-verified
river flow 15-min instantaneous (m3/s) · river flow daily mean/min/max (m3/s) · river level 15-min instantaneous (m) · river level daily min/max (m) · rainfall 15-min total (mm) · rainfall daily total (mm) · groundwater level dipped (mAOD) · groundwater level logged, sub-daily (mAOD) · water quality 15-min instantaneous: dissolved oxygen (% and mg/L), fDOM (RFU), blue-green algae (RFU), turbidity (NTU), chlorophyll (µg/L), conductivity (µS/cm), temperature (°C), ammonium (mg/L), nitrate (mg/L as N), pH
Coverage llm-inferred
England
Resolution docs-verified
typically 15 min (sub-daily) and daily
Formats docs-verified
JSON · CSV · GeoJSON · HTML · RDF/XML · Turtle
Access llm-inferred
No authentication (per catalogue); free; Open Government Licence 3.0
Useful for
Use cases llm-inferred
FRA baseline flows and levels from nearest gauge · Rainfall and river level context for flood event review · Groundwater level baseline for site investigation or geotechnical assessment · Water quality baseline (dissolved oxygen, turbidity, nitrate) for ecological or pollution assessment
Hard limit of 2,000,000 rows per call that cannot be overridden; soft limit of 100,000 rows per call (overridable with _limit) · Hard limit is subject to review and may be reduced if the service is overloaded · Bulk downloads should use the batch API; otherwise keep to one non-batch request in flight at a time · Concurrency limits may be enforced per IP address, and excessive demand may lead to blocking · Logged groundwater sub-daily values may mix 15-min and hourly intervals · Station identifiers are not always unique; some stations need a composite key with a wiskiID · HTML views are intended for debugging and development, not for presentation to consumers
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
Start with EA Hydrology API, MCPBundles EA Hydrology, EA Flood Monitoring API. Inspect station metadata and quality-labelled time series before selecting rainfall, level or flow observations.
What should I check before using these sources for ea hydrology api?
A wrapper is a separate access route to upstream data, not an independent monitoring network.
How do I inspect EA Hydrology API through MCP?
Connect an MCP client to https://terramcp.earth/mcp and call get_source with slug ea-hydrology-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.