Skip to content
All engineering use cases

Rainfall radar and gauge APIs

Evaluate available radar products against gauge accumulations and historical rainfall observations. Compare listed sources, access requirements and evidence for rainfall radar and gauge apis.

3 sources · For engineering consultants. Enrichment describes potential applications; review source evidence and limitations.

Check the current DataHub product entitlement for radar; gauge, radar and archive access are different services.

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.

{
  "mcpServers": {
    "terramcp": {
      "url": "https://terramcp.earth/mcp"
    }
  }
}

// After connecting, call this discovery tool:
{
  "name": "get_source",
  "arguments": {
    "slug": "met-office-weather-datahub"
  }
}

Listed sources

Frequently asked questions

Which listed sources support Rainfall radar and gauge APIs?

Start with Met Office Weather DataHub, EA Rainfall API (flood-monitoring), Met Office MIDAS Open (CEDA). Evaluate available radar products against gauge accumulations and historical rainfall observations.

What should I check before using these sources for rainfall radar and gauge apis?

Check the current DataHub product entitlement for radar; gauge, radar and archive access are different services.

How do I inspect Met Office Weather DataHub through MCP?

Connect an MCP client to https://terramcp.earth/mcp and call get_source with slug met-office-weather-datahub. 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.