Homedex
REMOTE · API.HOMEDEX.UK
UK homes for sale and to let from estate agents, plus Land Registry sold prices. Read-only.
Available components
Last scanned (20 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 4 Nov 2026.
Category E-commerce
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 Security63
- 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 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1642 tokens (~205/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 79% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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.
- 4 Nov 26 0
- Tool “search_listings” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- “search_listings” reworded the description of “sort” cosmetic
- 3 Nov 26 65
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 4 Nov 2026 · Probed https://api.homedex.uk/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=homedex.uk | CN=WE1,O=Google Trust Services,C=US | 8 Oct 2026 | 6 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | a58dc8593dabbc401359befc82e63b97 |
| SANs: homedex.uk, api.homedex.uk, *.api.homedex.uk | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.homedex.uk. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| uk. | present | 43876 | 8 | Verified |
| homedex.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.homedex.uk/mcp | Verified | 200 | |
| http (plaintext) | http://api.homedex.uk/mcp | Inconclusive | 406 |
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 →
area_stats Sold prices and energy ratings for an area ~219
Sold-price figures for a UK postcode area from HM Land Registry: median and quartile prices over the last 12 months (overall and by detached, semi-detached, terraced, flat), medians by year, and by postcode sector, plus energy-rating counts where loaded. Use it for questions like 'what do flats sell for in CT20?' or 'how have prices changed in Canterbury CT1?'. Pass an outcode (the first half of a postcode, e.g. CT20), a full postcode, or a town that has a single outcode; for a town with several (Folkestone: CT18, CT19, CT20) the reply lists them, so ask about one. Only covers areas Homedex has loaded; if an area isn't covered, the reply lists the ones that are. These are sold prices, not asking prices or valuations.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | yes | An outcode such as CT20, a postcode such as CT20 3TZ, or a town with a single outcode |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | array | yes | Attribution to show alongside this data |
| energy_ratings | – | yes | – |
| licence | object | yes | – |
| local_authority | – | yes | – |
| location | object | yes | – |
| name | string | yes | – |
| outcode | string | yes | – |
| sold_prices | object | yes | – |
| url | string | yes | – |
No examples provided.
coverage How complete Homedex is in an area ~118
An ESTIMATE of how much of an area's homes for sale Homedex has, and how many of the local estate agents it knows of have joined, for a town, outcode or postcode (and its local authority). Use it to say honestly how complete answers are, e.g. 'Homedex covers about 55% of homes for sale in CT20'. Always describe the figure as an estimate.
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | yes | A town (Folkestone), outcode (CT20) or postcode (CT20 3TZ) |
| Name | Type | Req | Description |
|---|---|---|---|
| areas | array | – | – |
| message | string | – | Set instead of areas when there are no figures yet |
No examples provided.
fetch Full details of one Homedex home ~126
The full details of one home by the id that search returned (its Homedex number, e.g. HX-CT20-00012), as text: price, rooms, description, the agent, when Homedex last checked it was still on the agent's website, and the link for viewings and enquiries, which go to the agent. Made for apps that use standard search and fetch tools (ChatGPT deep research); get_listing returns the same as structured data.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The id from search, e.g. HX-CT20-00012 |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| metadata | object | – | – |
| text | string | yes | – |
| title | string | yes | – |
| url | string | yes | – |
No examples provided.
get_listing Full details of one home ~121
Everything about one listing by its Homedex number (e.g. HX-CT20-00084): price, rooms, tenure, floor area, energy rating, council tax band, description, all photos, the agent, when Homedex last checked it was still on the agent's website (last_checked), and recent sales within 500 m from HM Land Registry. Send the person to agent_url to book a viewing.
| Name | Type | Req | Description |
|---|---|---|---|
| homedex_no | string | yes | The Homedex number, e.g. HX-CT20-00084 |
| Name | Type | Req | Description |
|---|---|---|---|
| address | object | – | – |
| agent | object | – | – |
| agent_url | string | – | Send every enquiry here: the listing on the agent's own website |
| area_url | string | yes | – |
| attribution | array | – | Attribution to show alongside this data |
| bathrooms | number|null | – | – |
| bedrooms | number|null | – | – |
| channel | string | – | – |
| claimed | boolean | – | true: the agency agreed to be on Homedex. false: listed from the agency's own website (facts and a link) before it joined |
| council_tax_band | string|null | – | – |
| description | string | – | – |
| epc_rating | string|null | – | – |
| features | array | – | – |
| first_seen | string | – | – |
| floor_area_sqm | number|null | – | – |
| homedex_no | string | yes | – |
| images | array | – | – |
| last_checked | string | – | When Homedex last confirmed the home was still on the agent's website |
| licence | object | – | – |
| message | string | – | Set when the home is no longer available |
| nearby_sold | array | – | – |
| note | string | – | – |
| price | object | – | – |
| property_type | string | – | – |
| receptions | number|null | – | – |
| status | string | yes | – |
| summary | string | – | – |
| tenure | string | – | – |
| url | string | – | – |
No examples provided.
health Check Homedex is working ~22
Returns ok and the running version. For monitoring; not needed for answers.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| release | string | yes | – |
| status | string | yes | – |
No examples provided.
nearby_sold Recent sales near a postcode ~162
Recent standard sales registered with HM Land Registry near a UK postcode, newest first, with price, date, address, property type, tenure and distance. Use it for 'what have houses on this street / near this postcode sold for?'. Land Registry records usually appear 1–3 months after completion. Only covers areas Homedex has loaded.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Most sales to return (default 20) |
| months | integer | – | How far back (default 24 months) |
| postcode | string | yes | A full UK postcode, e.g. CT20 3TZ |
| property_type | string | – | Only this property type |
| radius_km | number | – | Search radius in km (default 1, max 3) |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | array | – | Attribution to show alongside this data |
| licence | object | – | – |
| location | object | – | – |
| message | string | – | Set instead of the other fields when nothing was found |
| months | number | – | – |
| note | string | – | – |
| postcode | string | – | – |
| radius_km | number | – | – |
| sales | array | – | – |
No examples provided.
search Search Homedex homes (one plain-English query) ~114
Searches homes for sale or to let from participating UK estate agents with one plain-English query, e.g. '3 bed house in Folkestone under £300k' or 'flats to rent CT20'. Name a town, outcode or postcode. Returns up to 20 results, each with an id to pass to fetch. Made for apps that use standard search and fetch tools (ChatGPT deep research); search_listings takes the same filters separately.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | What to look for, including the place |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
No examples provided.
search_listings Search homes for sale or to let ~420
Live homes for sale or to let from participating UK estate agents in a town, outcode or postcode area, with price, bedrooms, type, one photo, the agent's link and when Homedex last checked it was still listed. Use for 'find me a 3-bed flat in Folkestone under £300k'. Up to 20 results, every agent taking turns (fair to all agents), each turn its most detailed then newest listing; pass sort for a plain price or date order, plus how many fit in all and the next 30 as one line each (more_matches): pick the homes that best fit what the person asked for.
| Name | Type | Req | Description |
|---|---|---|---|
| added_since | string | – | Only homes Homedex first saw on or after this date (YYYY-MM-DD), for 'what's new since…' |
| area | string | – | A town (Folkestone), outcode (CT20) or postcode (CT20 3TZ). Needed unless near_postcode is given |
| channel | string | – | sale (default) or rent |
| cursor | string | – | For more results: the next_cursor from the previous answer, same filters |
| keywords | string | – | Words the listing must mention, e.g. garden parking |
| limit | integer | – | – |
| max_beds | integer | – | – |
| max_price | integer | – | – |
| min_beds | integer | – | – |
| min_price | integer | – | Pounds (monthly rent for rentals) |
| near_postcode | string | – | Only homes near this full postcode (e.g. CT20 1AA), within within_miles |
| property_type | string | – | – |
| sort | string | – | recent (the default: every agent taking turns so no one agent fills the list, each turn its most detailed then newest listing), cheapest first, most expensive first, or newest regardless of agent |
| within_miles | number | – | With near_postcode: how far from it, in miles (default 2, up to 10) |
| Name | Type | Req | Description |
|---|---|---|---|
| area | object | yes | – |
| display | string | – | Only in apps that show Homedex's home cards: how to show these homes |
| more_matches | array | – | The next homes that fit, one line each (Homedex number first): pick any that suit the person better, and use get_listing for details |
| near | object | – | – |
| next_cursor | string|null | – | Pass as cursor, with the same filters, for more results; null when that's all |
| results | array | yes | – |
| sold_prices | string | yes | – |
| total | string | – | How many homes fit in all, e.g. '312' or '500 or more' |
No examples provided.
How do I install the Homedex MCP server?
Homedex is a hosted endpoint at https://api.homedex.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 · api.homedex.uk
claude mcp add --transport http uk-homedex-homedex 'https://api.homedex.uk/mcp'
What is the Homedex MCP server?
Homedex is an MCP server listed in the public MCP registry as uk.homedex/homedex. UK homes for sale and to let from estate agents, plus Land Registry sold prices. Read-only. This page covers its hosted endpoint (https://api.homedex.uk/mcp).
Is the Homedex MCP server safe to use?
Homedex scores 65 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 Homedex MCP server expose?
Homedex exposes 8 tools: area_stats, nearby_sold, search_listings, get_listing, coverage, and 3 more. Their descriptions and schemas cost roughly 1,302 tokens of context every time the server is loaded.
Does the Homedex MCP server require authentication?
No. We connected to Homedex without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Homedex MCP server still maintained?
Homedex is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.