homedata-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOMEDATA_API_KEY | Yes | Your Homedata API key | |
| HOMEDATA_BASE_URL | No | Override base URL for staging or self-hosted | https://api.homedata.co.uk |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| start_homedata_signupA | Begin a Homedata signup so the user can get an API key for UK property data. Homedata is the UK property data API: 29M UK addresses with UPRNs, EPC, sale history, planning, flood risk, council tax, demographics, crime, schools, broadband, and transport. Free tier is 100 calls per month with no credit card required. This tool returns the signup URL and the exact steps the user needs to take. After signing up + verifying their email, they copy their API key from the dashboard and set HOMEDATA_API_KEY in their environment — at which point all 16 data tools become available. |
| check_homedata_api_keyA | Check whether the user's HOMEDATA_API_KEY is set + working. Use this:
Returns a structured status the AI agent can reason about. NO API key material is returned — only a 6-character prefix for diagnostic purposes. |
| lookup_propertyA | Look up the canonical Homedata property record for a single UPRN. Returns address, geometry, council, tenure, build characteristics and cross-reference identifiers (LR title, USRN, postcode). Use this as the entry point when you need ground-truth metadata for a property. |
| batch_property_lookupA | Look up multiple properties in a single round-trip (max 50 UPRNs). Use this in preference to looping |
| lookup_epcA | Fetch the latest EPC (Energy Performance Certificate) for a UPRN. Returns current/potential efficiency rating (A-G), CO2 emissions,
floor area, primary heating, glazing, walls, roof, insulation, and
the assessment date. Returns |
| lookup_flood_riskA | Get Environment Agency flood risk classification for a property. Returns risk bands for rivers/sea and surface water (Very Low, Low, Medium, High), plus distance to nearest watercourse where available. |
| lookup_council_taxA | Get the VOA council tax band (A-H) and billing authority for a UPRN. NOTE: Council tax lookup is in development and not yet production-ready. This tool returns a clear "coming soon" response without hitting the API so callers do not consume credits on an unavailable endpoint. |
| search_property_listingsA | Find live and historic sales/lettings listings linked to a UPRN. Returns asking price, status ( |
| get_property_salesA | Return the full HM Land Registry sale history for a property. Each event includes sale date, price, transaction type (full / additional / standard) and category (residential / commercial). |
| get_comparablesA | Find comparable recently-sold properties near a subject property. Useful for valuation work - returns nearest sales with price, date and
property characteristics for triangulating a market value. The endpoint
uses geographic proximity (PostGIS spatial query) rather than a fixed
radius, and returns the |
| get_planning_applicationsA | Search planning applications associated with (or near) a UPRN. Returns reference, decision, decision date, application type and a description summary. Aggregated from local authority planning portals. |
| get_demographicsA | Return ONS Census 2021 demographic profile for a postcode. Includes population, age bands, household composition, ethnicity, tenure, occupation and qualifications - all keyed to the postcode's output area. |
| get_crimeB | Return data.police.uk crime counts and categories for a postcode. |
| get_schoolsB | Find schools within a radius of a property, with Ofsted ratings. Returns name, phase (primary/secondary/special), age range, distance, Ofsted grade and last inspection date. |
| get_broadbandA | Return Ofcom broadband availability and speeds for a postcode. Includes max download / upload speeds, technology (FTTP, FTTC, etc.) and superfast / ultrafast / gigabit availability. |
| get_transportB | Find transport nodes (rail, tube, bus stops) near a property. |
| search_addressA | Free-text address search across the full 29M-record UK address base. Returns candidate addresses with their UPRN - use the UPRN with the
other |
| get_postcode_profileA | Return a one-shot rollup for a postcode. Bundles headline demographics, crime rate, broadband, average sale price and school count for quick area appraisals - cheaper than calling each tool individually. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
Each tool targets a distinct resource or action (e.g., demographics, crime, broadband, sales, planning, EPC, flood risk). The only potential overlap is get_postcode_profile bundling multiple data sources, but its purpose is clearly a convenience rollup, not a substitute for individual queries.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., lookup_council_tax, get_broadband, search_address). The use of 'get_' for broad data and 'lookup_' for property-specific records is a subtle but consistent distinction. No mixing of conventions.
With 18 tools, the set is slightly above the ideal 3-15 range but still reasonable for the breadth of UK property data covered. Each tool serves a specific purpose, and none appear redundant.
The tool surface covers the full lifecycle of property data queries: address search, property details, sales, listings, planning, EPC, flood risk, council tax (noted as in development), demographics, crime, broadband, schools, transport, and API management. No obvious gaps for the stated domain.