Using Tamleek Plus via MCP
The MCP server exposes Tamleek's data as deterministic tools — no LLM, no natural-language parsing on our side. An MCP client (Claude, Cursor, or any MCP-compatible agent) calls these tools directly, the same way it would call a local function.
Connecting
- Transport: streamable HTTP. Endpoint:
https://<mcp-host>/mcp. - Auth: an
X-API-Keyheader on every request. Contact your Tamleek Plus contact for a key. - Rate limit: 120 requests/minute per API key by default (may be tuned per token).
- Per-token tool scoping: a key may be restricted to a subset of the 10 tools below. A call to a tool your key isn't scoped for returns
403.
Tool catalog (10 tools)
Two families, one server. Every tool returns a JSON object with a disclaimer.
MoJ registered sales (5 tools)
| Tool | Args | Returns |
|---|---|---|
volume_trend | municipality, year (2020–2026) | Transaction-volume trend (quarter-over-quarter) across a municipality's districts |
district_count | municipality, year | Transactions per district, with a thin-sample warning below 10 sales |
price_index | municipality, property_type (default "villa") | Median price/m² by quarter for a property type |
price_sqm | district, property_type (optional) | Indicative price/m² — median plus p25/p75 — for a district |
null_rate | district | Share of a district's transactions missing a registration date — a data-quality signal |
Aqarat QREP — rental & mortgage (5 tools)
| Tool | Args | Returns |
|---|---|---|
rent_price_sqm | municipality (EN or AR), property_type (optional) | Indicative monthly rent (median + IQR) and rent/m² |
rent_by_bedrooms | municipality, property_type (default "Apartment") | Median monthly rent by bedroom count |
rent_trend | municipality, year, property_type (optional) | Quarterly rent trend — median monthly rent and rent/m² |
mortgage_value_index | municipality, year | Quarterly mortgage value index (median financed value/m² and value) |
mortgage_activity | municipality, year | Mortgage/financing activity per area, with a thin-sample warning below 10 |
What you can ask through MCP
- Quantitative, parameterised questions about registered sales, rent, or mortgage activity by municipality or district.
- Trend and index questions over a specific year or property type.
- Data-quality checks (null rate, thin-sample flags) before you trust a figure downstream.
What you cannot ask through MCP
- Free-form natural-language questions — MCP tools are deterministic and parameterised; there is no NL-to-SQL layer at this level. That reasoning layer is the platform UI's analyst chat, which calls these same underlying data sources with an LLM on top.
- Unit-level or individually-identifiable transaction data (PDPPL).
- Active listing / asking-price data, deal-fairness checks, or Pearl demo valuations — those live on the REST API and the platform UI, not MCP, as of today.
- Anything requiring a valuation verdict — every tool returns indicative statistics, never a single "this is worth X" figure.
Reading a response
Every tool response includes a disclaimer block — treat it as part of the answer, not metadata to discard: it states the data window, the comparable count backing the figure, and a confidence signal (e.g. a thin-sample warning). Mortgage/district counts from Aqarat are page-padded by the source — use them as a relative ranking, not an absolute count.