Model Context Protocol

Connect an agent

Give any AI assistant the same research this site does — eleven categories for a UK postcode, side-by-side comparison, and the 45-dataset registry underneath. No account, no API key, nothing to install.

1

Copy this URL
2

Paste it into your AI

Claude, ChatGPT, Cursor, or any other MCP client — wherever it asks for a connector, custom integration or server URL.
3

Ask it about a postcode

“What's SW11 1AA like?” · “Compare M1 1AE and EH1 1YZ on broadband and transport” · “Where would I get EPC data for a property?”

Or add it in one command

Same server, same numbers, if you would rather not click through a settings pane. Nothing here needs the repository cloned.

Claude Code

claude mcp add --transport http agentic-house-search https://agentic-house-search.vercel.app/mcp

Cursor · VS Code

One click, then confirm in the editor.

Add to Cursor Add to VS Code

Any client that edits JSON

{
  "mcpServers": {
    "agentic-house-search": {
      "type": "http",
      "url": "https://agentic-house-search.vercel.app/mcp"
    }
  }
}

By name, no URL

Listed in the official MCP registry, so a client that supports it can find this server itself — search agentic-house-search, or paste the full name.

io.github.asturksever/agentic-house-search

Run it yourself

No rate limit, no dependency on this deployment. Needs Node 20+.

npx -y agentic-house-search

What your agent gets

Five tools, running the same provider modules as the report on this site — so a threshold or a caveat is written once and both surfaces agree.

Tool	What it does
`postcode_report`	Eleven categories for one postcode — demographics, crime, deprivation, prices, broadband, mobile, noise, transport, amenities, schools, environment.
`postcode_lookup`	Geography only: coordinates, local authority, ward, constituency, LSOA/MSOA/OA, police force, deprivation rank. One fast call.
`postcode_compare`	Two to five postcodes side by side, with the comparability caveats attached.
`postcode_search_datasets`	Search the 45-dataset registry by text or category.
`postcode_get_dataset`	One registry entry in full: endpoint, API docs, licence, coverage, cadence.

Before you trust a number it gives you

Geography varies by source. A census figure describes an LSOA — a neighbourhood of roughly 1,500 people, not an address. Ofcom mobile coverage describes an entire local authority, so two postcodes in the same authority always show identical mobile figures. Every figure states what it actually describes; a summary should carry that through.

Coverage is uneven, and said so. Census tables are England & Wales; data.police.uk excludes Scotland; planning, Defra noise and the school register are England-only. Those come back as out_of_coverage with a reason and a link to the devolved equivalent — never as a zero.

Deprivation ranks are not comparable across nations, and postcode_compare will not let a cross-nation comparison pass without saying so.

This is not a survey, a valuation or a conveyancing search.

The small print on the hosted endpoint

Free and unauthenticated, because there is nothing to protect. Every source is public government open data. There is no account, no key and no per-user state, so a sign-in step would guard nothing and cost you a step.

There is a courtesy rate limit — roughly 120 requests an hour — and it exists to keep one runaway agent from burning the fair-use budget of the government APIs underneath, not to nudge you anywhere. Running the server yourself has no limit at all and stays that way. Check the endpoint is up at /health ↗.

Keep the attribution attached. The compilation is CC0; the data is not. It is public sector information under the Open Government Licence v3.0, plus OS and Royal Mail rights in the postcode geography, and OpenStreetMap contributors (ODbL) for amenities. Every response carries this, and it should survive being summarised.