Analytics

heart.homes

Provides Dubai real estate market analytics and historical data through location search, market overview, and price history.

1 endpoint11 known toolsFirst detected August 20, 2026Last detected August 20, 2026

ENDPOINT 1

https://heart.homes/mcp

No auth detected

MCP server metadata

Name: heart-homes
Version: 1.0.0

Capabilities

tools.listChanged

Server instructions

Read-only Dubai residential real-estate data from official Dubai Land Department (DLD) records, aggregated nightly by heart.homes. Call search_locations first to resolve place names to slugs; prices are in AED; rent figures are annual contract values. Every response includes a `path` you can append to https://heart.homes for the matching page.

Known tools 11

search_locations

Resolve a free-text Dubai location name (community, area, or building) to canonical slugs.

Inferred read-only

get_market_overview

City-wide Dubai sales KPIs over the last 12 months (transaction count, total value, median price, median price per sqm) plus data freshness.

Inferred read-only

get_location_stats

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.

Inferred read-only

get_ready_vs_offplan

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.

Inferred read-only

get_price_history

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.

Inferred read-only

get_building_stats

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.

Inferred read-only

rank_buildings

Buildings in one community ranked by 12-month median sale price or median annual rent — answers 'cheapest/most expensive buildings in X'.

Inferred read-only

list_recent_transactions

Most recent registered DLD sales or rent contracts for a community or area slug — real records to ground price talk in.

Inferred read-only

compare_buy_vs_rent

Compare buying vs renting in one community or area: 12-month weighted median sale price, median annual rent, and the implied gross rental yield.

Inferred read-only

rank_communities

Communities ranked by 12-month median sale price or median annual rent — the direct answer to 'cheapest areas', 'most expensive communities', 'most affordable rents'.

Inferred read-only

get_trends_movers

Communities with the biggest 12-month price moves (direction 'up' = risers, 'down' = fallers).

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.heart-homes]
url = "https://heart.homes/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "heart-homes": {
      "type": "http",
      "url": "https://heart.homes/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: heart-homes
Remote MCP URL: https://heart.homes/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "heart-homes": {
      "url": "https://heart.homes/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "heart-homes": {
      "type": "http",
      "url": "https://heart.homes/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "heart-homes",
  "transport": "streamable-http",
  "url": "https://heart.homes/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for heart.homes was fetched 2026-08-23T15:32:23.298Z.

Trust status Neutral

heart.homes is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.