Floodwise

io.github.qinisolabsPublished by GitHub account qinisolabsv0.1.0Updated Oct 24, 2026

England flood-risk by postcode for AI agents — verified Environment Agency data, not guesses.

VerifiedSTDIODesktop onlyLocation & LifestyleData & Analytics

Overview

AI-generated overview

Local MCP server that looks up official Environment Agency long-term flood-risk bands for England postcodes and validates UK postcode formats.

What you can do
  • Look up the long-term flood-risk band (High, Medium, Low, Very Low) for an England postcode, with address counts per band and a groundwater indication
  • Validate a UK postcode's format and split it into outcode and incode
  • Return an honest "not found" for well-formed postcodes outside the England dataset instead of inventing a risk level
When to use it
Useful when an assistant is asked about flood risk at an England postcode and should answer from official data rather than guess. Also handy for checking that a postcode is well formed before other lookups.
Requirements
Runs locally over stdio via npx with no key or login. The repository ships only an illustrative sample dataset; the real England data must be downloaded from the government open-data source and built into the package with the provided build script.
Before you install
Covers England only; Welsh, Scottish and Northern Irish postcodes return "not found". Risk is area-level long-term, not property-level, not a live warning, and not insurance, surveying or legal advice. Excludes some flood types such as sewers and overland flow. The bundled sample data is non-geographic and tagged as sample, so real answers require loading the official dataset.

Installation

In SourceWeft

  1. Open Floodwise in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[Qiniso]

floodwise

England flood-risk by postcode for AI agents — verified Environment Agency data, not guesses.

Verified, trustworthy data tools for AI agents. "Qiniso" means "truth" in Zulu.

Website · npm · MCP Registry


Ask an LLM "what's the flood risk at SW1A 1AA?" and it will answer confidently — but it cannot know: per-postcode flood risk is specific, curated data that lives in a government dataset, not in a model's weights. floodwise looks the postcode up in the Environment Agency's official "Flood risk: postcode search tool" data and returns the real long-term risk band — or an honest "not found" instead of a guess.

⚠️ Read this first — what floodwise is and isn't

  • England only. The data is the Environment Agency's, which covers England. Wales (Natural Resources Wales), Scotland (SEPA) and Northern Ireland (DfI) are not covered. A valid Welsh/Scottish postcode returns "not found", never a guess.
  • Area-level, not property-level. The risk is for the area around the addresses in a postcode — not a specific building. The EA states this data is "generally not suitable for property level assessment".
  • Long-term risk, not a live warning. It reflects the long-term annual chance of flooding, not whether flooding is happening now or forecast. It is not insurance, underwriting, surveying or professional advice.

Add it to Claude

floodwise runs locally over stdio (no key, no login). Once it's on npm, add it under mcpServers in your client config:

json
{ "command": "npx", "args": ["-y", "floodwise"] }

Use it as a library

bash
npm i floodwise
ts
import { floodRiskByPostcode, validatePostcode } from "floodwise";
floodRiskByPostcode("SW1A 1AA");// {//   postcode: "SW1A 1AA", found: true, headlineRisk: "Very Low",//   addressesAtRisk: { high: 0, medium: 0, low: 0 }, groundwater: "Unlikely",//   coverage: "England", dataset: "ea-official", ...// }
floodRiskByPostcode("EH1 1AA").found;   // false — valid postcode, but Scotland (out of EA coverage), no guessvalidatePostcode("ec1a1bb");            // { valid: true, postcode: "EC1A 1BB", outcode: "EC1A", incode: "1BB" }

Postcodes are accepted spaced or unspaced, any case. A well-formed postcode that isn't in the loaded England dataset returns found: false with a clear note — it never invents a risk level.

Tools — 2

ToolWhat it answers
flood_risk_by_postcodeThe EA long-term flood-risk band (High/Medium/Low/Very Low) for an England postcode, address counts per band, and the groundwater indication
validate_postcodeIs this a well-formed UK postcode? (deterministic format check + outcode/incode split)

Data

The flood data is the Environment Agency "Flood risk: postcode search tool data" (England), published as open data under the Open Government Licence v3.0. Each postcode carries the number of addresses whose surrounding area is at high (≥3.3%/yr), medium (1–3.3%) or low (0.1–1%) long-term risk from rivers, sea or surface water (the highest of these), plus a separate groundwater Possible/Unlikely indication. Refreshed roughly quarterly.

This repository ships an illustrative starter sample (non-geographic ZZ pseudo-postcodes) so tests run out of the box — every response from it is tagged dataset: "sample". To load the real data, download Postcodes_Risk_Assessment_All.csv from data.gov.uk / the Defra Data Services Platform and run:

bash
npm run build-data /path/to/Postcodes_Risk_Assessment_All.csv 2025-Q4npm run build && npm test

Attribution: Contains public sector information licensed under the Open Government Licence v3.0. © Environment Agency copyright and/or database right. See NOTICE.

What it is not

  • Not advice. Not insurance, underwriting, surveying, mortgage or legal advice; not a property-level survey.
  • Not all flood types. Excludes flooding from highway drains, sewers and overland flow; groundwater is reported separately and isn't combined into the headline band.
  • Not the whole UK. England only (see above).
  • Not a guesser. Unknown/out-of-coverage postcodes return an honest "not found", never a fabricated risk level.

Architecture

A single TypeScript package exposing one MCP server over stdio (local / npx), driven by the same core.ts tool definitions that power the importable library. A Cloudflare Worker entry is included for a future hosted edge endpoint — note the full England dataset (~1.6M postcodes) exceeds the Worker bundle limit, so the hosted build will move the data into Cloudflare D1 (a follow-on); the npm library and stdio server run the full dataset directly.

bash
npm installnpm run buildnpm test

Privacy

This tool runs locally on your machine and is built not to collect, store, or transmit your data — no analytics, no telemetry, no account. All reference data is bundled — no network calls, and nothing leaves your device. Full policy: https://qinisolabs.github.io/privacy.html.

License

Apache-2.0. Flood data © Environment Agency, Open Government Licence v3.0; see NOTICE.

Source: README.md at commit 5a09596

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts