HouseData
REMOTE · HOUSEDATA.UK
UK property data: EPC, flood risk, planning, sale prices, MEES 2030 checks and grants.
Available components
Last scanned (15 hours ago)
Scores higher than 63% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1080 tokens (~98/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 85% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 13 Oct 26 69
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Probed https://housedata.uk/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.housedata.uk | CN=YR1,O=Let's Encrypt,C=US | 5 Oct 2026 | 3 Jan 2027 | RSA 2048 | SHA256-RSA | 639a5b843c21d61ecd50c7c500c6fd53483 |
| SANs: *.housedata.uk, housedata.uk | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of housedata.uk. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| uk. | present | 43876 | 8 | Verified |
| housedata.uk. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self';script-src 'self' 'unsafe-inline' https://js.stripe.com https://unpkg.com https://cdn.jsdelivr.net https://*.clarity.ms;script-src-attr 'self' 'unsafe-inline';style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://unpkg.com;font-src 'self' https://fonts.gstatic.com;img-src 'self' data: https: blob:;connect-src 'self' https://api.stripe.com https://*.clarity.ms;frame-src https://js.stripe.com;base-uri 'self';form-action 'self';frame-ancestors 'self';object-src 'none';upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://housedata.uk/mcp | Verified | 200 | |
| http (plaintext) | http://housedata.uk/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_epc_compliance Check EPC / MEES compliance ~69
Batch-checks up to 50 properties (by id or postcode) against Minimum Energy Efficiency Standard (MEES) 2030 thresholds and flags expired certificates. Use for landlord portfolio compliance sweeps.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | Property ids and/or postcodes, up to 50 |
No output schema declared.
No examples provided.
get_area_market Get area market trend ~59
UK House Price Index and local market trend (price growth, transaction velocity, property mix) for a postcode area.
| Name | Type | Req | Description |
|---|---|---|---|
| postcode | string | yes | UK postcode or outcode, e.g. "CV4 7AL" or "CV4" |
No output schema declared.
No examples provided.
get_broadband Get broadband availability ~62
Ofcom broadband and mobile coverage for a postcode. Requires a HouseData API key. Live-checked per call, so this can take several seconds — do not call it in a tight loop over many postcodes.
| Name | Type | Req | Description |
|---|---|---|---|
| postcode | string | yes | UK postcode |
No output schema declared.
No examples provided.
get_epc_history Get EPC history ~90
All EPC certificates lodged for a property over time, with floor area, room counts and rating per certificate. A floor-area jump between certificates with no matching planning record is the single highest-value red flag for a cash buyer.
| Name | Type | Req | Description |
|---|---|---|---|
| property_id | string | yes | The property id returned by search_property (an EPC certificate lmk-key). Prefer this over re-supplying a postcode once you have it. |
No output schema declared.
No examples provided.
get_flood_risk Get flood risk ~105
Environment Agency flood zone (river/sea) and surface-water risk for a property, reported separately. Returns an explicit absent state rather than a false "low" when EA has no data for the location.
| Name | Type | Req | Description |
|---|---|---|---|
| postcode | string | – | UK postcode — required if property_id is not given |
| property_id | string | – | The property id returned by search_property (an EPC certificate lmk-key). Prefer this over re-supplying a postcode once you have it. |
No output schema declared.
No examples provided.
get_grants Get grant eligibility ~114
Energy-efficiency and home-improvement grant schemes a property may be eligible for, based on EPC rating, council tax band, tenure and income band.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | – |
| income_range | string | – | – |
| postcode | string | – | UK postcode — required if property_id is not given |
| property_id | string | – | The property id returned by search_property (an EPC certificate lmk-key). Prefer this over re-supplying a postcode once you have it. |
| tenure | string | – | – |
No output schema declared.
No examples provided.
get_planning_history Get planning history ~82
Nearby planning applications and decisions, plus a rule-based planning approval-likelihood score for the area.
| Name | Type | Req | Description |
|---|---|---|---|
| postcode | string | – | UK postcode — required if property_id is not given |
| property_id | string | – | The property id returned by search_property (an EPC certificate lmk-key). Prefer this over re-supplying a postcode once you have it. |
No output schema declared.
No examples provided.
get_price_history Get Price Paid history ~91
HM Land Registry Price Paid transaction history for a property or postcode.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | House number/name to narrow results within the postcode |
| postcode | string | – | UK postcode — required if property_id is not given |
| property_id | string | – | The property id returned by search_property (an EPC certificate lmk-key). Prefer this over re-supplying a postcode once you have it. |
No output schema declared.
No examples provided.
get_prism_score Get PRISM consent-gap score ~119
Housedata PRISM score: identifies where a property's features (extensions, conversions, floor-area changes) lack a corresponding planning/building-control record, with remediation paths. Requires an active HouseData API key — if the account is not entitled, the error explains how to upgrade.
| Name | Type | Req | Description |
|---|---|---|---|
| postcode | string | – | UK postcode — required if property_id is not given |
| property_id | string | – | The property id returned by search_property (an EPC certificate lmk-key). Prefer this over re-supplying a postcode once you have it. |
No output schema declared.
No examples provided.
get_property_summary Get property summary ~82
One-call overview of a property: EPC headline, last sale, flood risk, LPA, planning-risk score and council tax band. Start here after disambiguating with search_property.
| Name | Type | Req | Description |
|---|---|---|---|
| property_id | string | yes | The property id returned by search_property (an EPC certificate lmk-key). Prefer this over re-supplying a postcode once you have it. |
No output schema declared.
No examples provided.
search_property Search for a property ~74
Find candidate properties by address or postcode. Always call this first and confirm the match with the user before running other tools — never guess which property was meant.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Free-text address or postcode, e.g. "14 Acacia Road, CV4 7AL" or "CV4 7AL" |
No output schema declared.
No examples provided.
How do I install the HouseData MCP server?
HouseData is a hosted endpoint at https://housedata.uk/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · housedata.uk
claude mcp add --transport http uk-housedata-housedata 'https://housedata.uk/mcp'
What is the HouseData MCP server?
HouseData is an MCP server listed in the public MCP registry as uk.housedata/housedata. UK property data: EPC, flood risk, planning, sale prices, MEES 2030 checks and grants. This page covers its hosted endpoint (https://housedata.uk/mcp).
Is the HouseData MCP server safe to use?
HouseData scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the HouseData MCP server expose?
HouseData exposes 11 tools: search_property, get_property_summary, get_epc_history, get_price_history, get_area_market, and 6 more. Their descriptions and schemas cost roughly 947 tokens of context every time the server is loaded.
Does the HouseData MCP server require authentication?
No. We connected to HouseData without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the HouseData MCP server still maintained?
HouseData is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.