Homedex MCP server
uk.homedex/homedexhomedex.ukstreamable-httpv1.0.1Scanned
UK homes for sale and to let from estate agents, plus Land Registry sold prices. Read-only.
8 tools: 3 change things and 5 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Homedex MCP server can do
The Homedex MCP server is published by homedex.uk, a domain the MCP Registry verified. It has 8 tools. It can create or change data (3 tools: area_stats, nearby_sold and coverage), but cannot delete data. 5 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 16, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
8 tools
Changes things 3Claude Code: ask
area_statsSold-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), median…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Sold prices and energy ratings for an area
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
coverageAn 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 aut…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: How complete Homedex is in an area
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
nearby_soldRecent standard sales registered with HM Land Registry near a UK postcode, newest first, with price, date, address, property type, tenure and distance.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Recent sales near a postcode
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
Only reads 5Show 5 read-only tools
fetchThe full details of one home by the id that search returned (its Homedex number, e.g.No findings
Why it is in this group
- The name "fetch" says "fetch": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Full details of one Homedex home
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
get_listingEverything about one listing by its Homedex number (e.g.No findings
Why it is in this group
- The name "get_listing" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Full details of one home
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
healthReturns ok and the running version.No findings
Why it is in this group
- The description's first verb is "return": a word for reading.
Description, as the server wrote it Returns ok and the running version. For monitoring; not needed for answers.
Annotations the server declares
- title: Check Homedex is working
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
searchSearches homes for sale or to let from participating UK estate agents with one plain-English query, e.g.No findings
Why it is in this group
- The name "search" says "search": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Search Homedex homes (one plain-English query)
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
search_listingsLive 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…No findings
Why it is in this group
- The name "search_listings" says "search": a word for reading.
Description, as the server wrote it 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'. Homes only, unless commercial (shops, offices, industrial units) is asked for with property_type commercial or the commercial filter; commercial results have commercial: true. 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.
Annotations the server declares
- title: Search homes for sale or to let
- readOnlyHint: true
- destructiveHint: false
- openWorldHint: false
- idempotentHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 18, 2026, 16:23 UTC, unchanged since Nov 4, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.homedex.uk/mcp: tools/list returned 8 tools to an anonymous client, including area_stats (write), nearby_sold (write), coverage (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:search_listingsOnly readsdescriptioninputSchema
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http homedex https://api.homedex.uk/mcpclaude mcp add --transport http homedex https://api.homedex.uk/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__homedex__search_listings",
"mcp__homedex__get_listing",
"mcp__homedex__health",
"mcp__homedex__search",
"mcp__homedex__fetch"
],
"ask": [
"mcp__homedex__area_stats",
"mcp__homedex__nearby_sold",
"mcp__homedex__coverage"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as homedex. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/uk.homedex/homedex/verify?hash=497b013a555baf5f892717ffc00c72c0f0c7570fb1a87528a46f2a711b9b4498" | jq -e '.changed == false'Pinned hash 497b013a555b, from Nov 16, 2026, 22:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/uk.homedex/homedex/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/uk.homedex/homedex)Source: MCP Registry. Synced Nov 3, 2026, 11:18 UTC.
Homedex MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Homedex MCP server safe?
- No scan can promise that. What its definitions show: 8 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Homedex MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Homedex MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Homedex MCP server have?
- 8 tools: 3 write, 5 read. area_stats, nearby_sold, coverage, search_listings, get_listing, health, search and fetch.
Does the Homedex MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Homedex MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Homedex MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.