Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Nothing to run from here
Homedex is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
8
tools declared
remote
at its publisher
—
calls last 7d
What it does
UK homes for sale and to let from estate agents, plus Land Registry sold prices. Read-only.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http homedex-mcp https://api.homedex.uk/mcp
# 2 — ask your agent for something these tools do
# area_stats, nearby_sold, search_listings and 5 more
Homedex costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
HOAll 1 server
homedex1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http homedex-mcp https://api.homedex.uk/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take x-api-key header (Optional Homedex API key (by arrangement: hello@homedex.uk) for a higher rate limit) if you want to set it.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| area | string | yes | An outcode such as CT20, a postcode such as CT20 3TZ, or a town with a single outcode |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| postcode | string | yes | A full UK postcode, e.g. CT20 3TZ |
| radius_km | number | no | Search radius in km (default 1, max 3) |
| months | integer | no | How far back (default 24 months) |
| limit | integer | no | Most sales to return (default 20) |
| property_type | string | no | Only this property type |
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 pl
| Parameter | Type | Required | Notes |
|---|---|---|---|
| area | string | no | A town (Folkestone), outcode (CT20) or postcode (CT20 3TZ). Needed unless near_postcode is given |
| near_postcode | string | no | Only homes near this full postcode (e.g. CT20 1AA), within within_miles |
| within_miles | number | no | With near_postcode: how far from it, in miles (default 2, up to 10) |
| channel | string | no | sale (default) or rent |
| min_price | integer | no | Pounds (monthly rent for rentals) |
| max_price | integer | no | — |
| min_beds | integer | no | — |
| max_beds | integer | no | — |
| added_since | string | no | Only homes Homedex first saw on or after this date (YYYY-MM-DD), for 'what's new since…' |
| property_type | string | no | — |
| keywords | string | no | Words the listing must mention, e.g. garden parking |
| sort | string | no | 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 |
| limit | integer | no | — |
| cursor | string | no | For more results: the next_cursor from the previous answer, same filters |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| homedex_no | string | yes | The Homedex number, e.g. HX-CT20-00084 |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| area | string | yes | A town (Folkestone), outcode (CT20) or postcode (CT20 3TZ) |
Returns ok and the running version. For monitoring; not needed for answers.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | What to look for, including the place |
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 d
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The id from search, e.g. HX-CT20-00012 |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Homedex or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.0.1 · scanned 4 Nov 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest1da1dc0635333daab14854a03e3fce547cdc7795136193096e1ad8c66cbce139
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| area_stats | no tags | |
| nearby_sold | no tags | |
| search_listings | no tags | |
| get_listing | no tags | |
| coverage | no tags | |
| health | no tags | |
| search | untrusted-input | untrusted-input: keyword "fetch" |
| fetch | untrusted-input | untrusted-input: keyword "fetch" |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest1da1dc0635333daa
Scanned2026-11-04
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.1.
1.0.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Homedex can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.