Heart Homes — Dubai property data
REMOTE · HEART.HOMES · SCANNED OCT 4
Dubai property prices, rents and trends from official Dubai Land Department records. Read-only.
Available components
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 Security74
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1165 tokens (~105/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 59% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Heart Homes — Dubai property data MCP server?
Heart Homes — Dubai property data is a hosted endpoint at https://heart.homes/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 · heart.homes
claude mcp add --transport http homes-heart-heart-homes 'https://heart.homes/mcp'
{
"mcpServers": {
"homes-heart-heart-homes": {
"url": "https://heart.homes/mcp"
}
}
} {
"servers": {
"homes-heart-heart-homes": {
"type": "http",
"url": "https://heart.homes/mcp"
}
}
} [mcp_servers.homes-heart-heart-homes] url = "https://heart.homes/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"homes-heart-heart-homes": {
"type": "remote",
"url": "https://heart.homes/mcp",
"enabled": true
}
}
} openclaw mcp add homes-heart-heart-homes --url 'https://heart.homes/mcp' --transport streamable-http
mcp_servers:
homes-heart-heart-homes:
url: "https://heart.homes/mcp" {
"McpServers": {
"homes-heart-heart-homes": {
"Transport": "http",
"Url": "https://heart.homes/mcp"
}
}
} assistant mcp add homes-heart-heart-homes -t streamable-http -u 'https://heart.homes/mcp'
{
"mcpServers": {
"homes-heart-heart-homes": {
"type": "http",
"url": "https://heart.homes/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 +7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
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 5 Oct 2026 · Probed https://heart.homes/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=heart.homes | CN=WE1,O=Google Trust Services,C=US | 24 Sept 2026 | 23 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | bd9097a719d9bff213078465e0ab2ff9 |
| SANs: heart.homes, www.heart.homes, *.www.heart.homes | ||||||
| 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 heart.homes. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| homes. | present | 33262, 64382 | 8, 8 | Verified |
| heart.homes. | 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://heart.homes/mcp | Verified | 200 | |
| http (plaintext) | http://heart.homes/mcp | HTTPS enforced | 301 | https://heart.homes/mcp |
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 →
compare_buy_vs_rent Buy vs rent comparison ~78
Compare buying vs renting in one community or area: 12-month weighted median sale price, median annual rent, and the implied gross rental yield. Optionally filter to one property class.
| Name | Type | Req | Description |
|---|---|---|---|
| propertyClass | string | – | Property class filter |
| slug | string | yes | Location slug (community or area) as returned by search_locations |
No output schema declared.
No examples provided.
get_building_stats Building statistics ~94
Stats for one building: 12-month sales, median price, trend, recent sales, property-type mix, and - where rent contracts can be attributed to the building - median annual rent and recent rent contracts, and a per-bedroom rent breakdown where enough contracts resolve a bedroom. Takes the communitySlug + buildingSlug pair returned by search_locations.
| Name | Type | Req | Description |
|---|---|---|---|
| buildingSlug | string | yes | – |
| communitySlug | string | yes | – |
No output schema declared.
No examples provided.
get_location_stats Location statistics ~154
Headline stats for one community or area slug: 12-month sales volume, median price, price per sqm, 12-month trend, plus a property-class mix for sales and rents. When propertyClass is set for a community, also returns per-bedroom sales and rent breakdowns; rent bedroom coverage is partial and must be reported as approximate using rentBedroomCoveragePct and rentBedroomNote. Per-bedroom rent for a single building is not available.
| Name | Type | Req | Description |
|---|---|---|---|
| propertyClass | string | – | When set, also return the per-bedroom sales breakdown and, where attributable, a per-bedroom rent breakdown with partial-coverage figure (communities only) |
| slug | string | yes | Location slug (community or area) as returned by search_locations |
No output schema declared.
No examples provided.
get_market_overview Dubai market overview ~48
City-wide Dubai sales KPIs over the last 12 months (transaction count, total value, median price, median price per sqm) plus data freshness. Good first call for broad questions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_price_history Monthly price history ~108
Monthly transaction counts and median prices for a community/area slug (or city-wide when slug is omitted), for sales or rents, optionally filtered to one property class. Rent medians are annual contract values in AED/year.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | 'sale' = DLD sales transactions, 'rent' = Ejari rent contracts |
| months | integer | – | – |
| propertyClass | string | – | Property class filter |
| slug | string | – | Omit for city-wide history |
No output schema declared.
No examples provided.
get_ready_vs_offplan Ready vs off-plan (secondary market) split ~157
Sales split between the secondary (ready / resale) market and the off-plan (pre-completion developer) market for one community or area over the last 12 months - transaction count, total value, and median price for each. "ready" = completed homes resold on the secondary market; "off-plan" = pre-completion developer sales. Property flipping, reselling, and "resale market" questions are READY / secondary-market questions: report the ready row here and do not present off-plan figures as flipping or resale figures. Optionally filter to one property class.
| Name | Type | Req | Description |
|---|---|---|---|
| propertyClass | string | – | Property class filter |
| slug | string | yes | Location slug (community or area) as returned by search_locations |
No output schema declared.
No examples provided.
get_trends_movers Trending communities ~67
Communities with the biggest 12-month price moves (direction 'up' = risers, 'down' = fallers). Only communities with 30+ sales are included, so thin-volume noise is excluded.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
list_recent_transactions Recent transactions ~83
Most recent registered DLD sales or rent contracts for a community or area slug - real records to ground price talk in.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | 'sale' = DLD sales transactions, 'rent' = Ejari rent contracts |
| limit | integer | – | – |
| slug | string | yes | Location slug (community or area) as returned by search_locations |
No output schema declared.
No examples provided.
rank_buildings Rank buildings within a community ~107
Buildings in one community ranked by 12-month median sale price or median annual rent - answers 'cheapest/most expensive buildings in X'. Rent coverage is partial: Ejari records carry no building name, so only buildings whose project name identifies them uniquely have rent stats. Buildings with fewer than 5 records are excluded.
| Name | Type | Req | Description |
|---|---|---|---|
| communitySlug | string | yes | Community slug from search_locations |
| limit | integer | – | – |
| metric | string | yes | – |
| order | string | yes | – |
No output schema declared.
No examples provided.
rank_communities Rank communities by price or rent ~123
Communities ranked by 12-month median sale price or median annual rent - the direct answer to 'cheapest areas', 'most expensive communities', 'most affordable rents'. Only communities with 30+ transactions are ranked; without a propertyClass filter, only residential classes (apartments + villas) count, so whole-building leases and land deals don't skew the medians.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| metric | string | yes | Rank by sale prices or by annual rents |
| order | string | yes | – |
| propertyClass | string | – | Property class filter |
No output schema declared.
No examples provided.
search_locations Search locations ~72
Resolve a free-text Dubai location name (community, area, or building) to canonical slugs. Always call this first when the user names a place; other tools take the returned slugs.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Restrict results to one kind |
| query | string | yes | Location name to search for |
No output schema declared.
No examples provided.
What is the Heart Homes — Dubai property data MCP server?
Heart Homes — Dubai property data is an MCP server listed in the public MCP registry as homes.heart/heart-homes. Dubai property prices, rents and trends from official Dubai Land Department records. Read-only. This page covers its hosted endpoint (https://heart.homes/mcp).
Is the Heart Homes — Dubai property data MCP server safe to use?
Heart Homes — Dubai property data scores 77 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 Heart Homes — Dubai property data MCP server expose?
Heart Homes — Dubai property data exposes 11 tools: search_locations, get_market_overview, get_location_stats, get_ready_vs_offplan, get_price_history, and 6 more. Their descriptions and schemas cost roughly 1,091 tokens of context every time the server is loaded.
Does the Heart Homes — Dubai property data MCP server require authentication?
No. We connected to Heart Homes — Dubai property data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Heart Homes — Dubai property data MCP server still maintained?
Heart Homes — Dubai property data is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.