Unstable preview. Pages, data and API fields can change or break without notice, so please don't rely on this for anything critical yet. See what has changed.
Agent Service Directory

Homedex

MCP server · api.homedex.uk · found in a public list · checked since 2026-11-03

Live, handshake completed · latest check

As JSON

UK homes for sale and to let, plus Land Registry sold prices.

Our summary of what its own text says it does: automated, not reviewed by a person (placement-ai/7). What this means

Placed in Find property to buy or rent: Listings of homes, land, rooms, workspaces and auctions for sale or rent.

https://api.homedex.uk/mcp MCP endpoint (Streamable HTTP)

The name is the registry's label, not ours. Not reviewed by a person.

Our checks

An unpaid request daily, from eastern North America

Last 2 checks, oldest to newest; room for 28 more

2 passed, 0 failed, 28 not run.

Passed, 30 daysshort history2 of 2 run
Checks missed0in 30 days
Response, latest191 mswhole handshake
Scheduledailyset by usage; rule below
Checked since2026-11-031 day
Freshnessfreshagainst its schedule

Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.

Response times

WindowChecksTimeoutsMedian90th95th99thFastestSlowest
24 hourssince 2026-11-0310——————
7 dayssince 2026-11-0310——————
30 dayssince 2026-11-0310——————

Milliseconds, from eastern North America, timing the whole MCP handshake (initialize to the tools/list answer). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.

Details

Tools listed by the server

area_statscoveragefetchget_listinghealthnearby_soldsearchsearch_listings

Tools
8
This list since
2026-11-04
First listed to us
2026-11-03
List changes, 90 days
1

Names as the server reported them at our latest completed handshake (mcp-handshake/2); a listed tool is not a tested one. Definitions

Access

Our latest check
Nothing asked
Stated
not stated
Payment model
not known
Currency
not known

"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions

Interface it declares

Protocol
MCP 2025-06-18
Capabilities
tools
Transports
streamable-http

As its initialize reply stated it at our check on (mcp-handshake/2): a claim, not tested. Definitions

What it says about itself

Where it works
United Kingdomfrom its listing's description, read 2026-11-03

From the service's own text, put in short words by a small AI model and shown only where its own words support it (stated-facts/5): its claims, not checked by us. Anything not listed, it does not state. Definitions

Calls it declares

  • area_stats area* → outcode name url location local_authority
  • nearby_sold postcode* radius_km months limit property_type → message postcode location radius_km months
  • search_listings area near_postcode within_miles channel min_price max_price min_beds max_beds added_since property_type keywords sort limit cursor → area near results next_cursor total
  • get_listing homedex_no* → homedex_no status message area_url url
  • coverage area* → message areas
  • health → status release
  • search query* → results
  • fetch id* → id title text url metadata

From the tool list it returned to our check (request-shape/2). * marks a required parameter; after → the fields it says it returns. What it declares, not that a call works.

Listing

In the capability tree: Commerce, travel and logistics / Property / Find property to buy or rent (primary); Commerce, travel and logistics / Property / Property prices and valuations. Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/7, tree/3) on 2026-11-03. Wrong place? Tell us.

In the directory: meets our listing criteria (listing-criteria/6): ✓ says what it does; ✓ its latest check passed.

Recent probes

WhenResultTime to headers

cloudflare:MIA
Live, handshake completed HTTP 200 191 ms

cloudflare:MIA
Live, handshake completed HTTP 200 177 ms

What these figures do not show

  • A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/2) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
  • Listed in the Official MCP Registry; this data comes from the Official MCP Registry. Its listing's description is not republished.
  • Limited evidence: monitored for 1 day (less than 30).

Something wrong here?

Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.

Machine-readable: /api/v1/services/cand_0131537519dd50ab