UK Property Intelligence MCP Server

UK Property Intelligence

This MCP server exposes bounded property intelligence through tools and an interactive MCP App. It does not provide raw bulk data downloads.

Core Workflows

• Look up postcode geography: lat/lon, local authority, ward, LSOA/MSOA, and constituency where present in the local postcode product.
• Resolve free-text property addresses to candidate postcodes from local PPD and EPC address records before asking the user for a postcode.
• Search locally-ingested EPC/DEC certificates by postcode, address fragment, certificate type, and energy band.
• List known addresses for a postcode and look up EPC-backed UPRNs where the source data contains a UPRN.
• Search bounded HMLR sale records, price trends, price distributions, and market activity by full postcode or postcode outer.
• Match HMLR Price Paid transactions to EPC records within a postcode using conservative materialized rule-pass matches where available.
• Estimate conservative price-per-square-foot valuation bands from matched sale prices, transfer dates, and EPC floor area.
• Inspect dataset health, match coverage, valuation usability, outlier counts, stale EPC rates, and property-type coverage before relying on derived metrics.
• Find property opportunities, block-level evidence, repeat-sale movements, and EPC value gaps from the same matched sale/EPC evidence.
• Build a property report with recent sale history, EPC context, geography, match confidence, floor area, price per square metre, and price per square foot.

Interpretation Rules

• Treat materialized PPD/EPC matches as high-confidence joins, while still surfacing match method and confidence metadata.
• Treat ad hoc fallback matches as exploratory evidence, not as high-confidence valuation comps.
• Prefer postcode plus address fragment for property-level questions.
• If the user gives an address without a postcode, call the address resolver first, then use the best candidate postcode with the report or valuation tools.
• Use price-per-area metrics only when the matched EPC has a positive floor area.
• Preserve quality flags such as thin comparable sets, stale EPC records, fallback match evidence, and outlier sale/floor-area values in conclusions.
• Do not infer retrofit actions or improvement uplift unless those facts are present in the returned tool data.
• Surface source attribution and licence boundaries when using address-level EPC data in customer-facing outputs.

Licensing Boundary

HMLR Price Paid data is used for authenticated agent-query and UI-display workflows. EPC non-address fields are licensed under Open Government Licence v3.0. EPC address and postcode fields carry Ordnance Survey/Royal Mail copyright and database-right notices and are used here for bounded energy/property-intelligence workflows, not bulk redistribution.