# unacasa.es (remote · mcp.unacasa.es)

Spanish real estate data and property valuation: homes, buildings, plots, streets and areas.

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.unacasa.es`: 70/100 (this document), [markdown](https://verifymcp.io/servers/es-unacasa-unacasa/mcp.md), [page](https://verifymcp.io/servers/es-unacasa-unacasa/mcp)

## Channel facts

- Endpoint: `https://mcp.unacasa.es/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2010 tokens (~182/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 77% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the unacasa.es MCP server?

unacasa.es is a hosted endpoint at https://mcp.unacasa.es/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.

### Claude

```bash
claude mcp add --transport http es-unacasa-unacasa 'https://mcp.unacasa.es/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "es-unacasa-unacasa": {
      "url": "https://mcp.unacasa.es/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "es-unacasa-unacasa": {
      "type": "http",
      "url": "https://mcp.unacasa.es/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.es-unacasa-unacasa]
url = "https://mcp.unacasa.es/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "es-unacasa-unacasa": {
      "type": "remote",
      "url": "https://mcp.unacasa.es/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add es-unacasa-unacasa --url 'https://mcp.unacasa.es/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  es-unacasa-unacasa:
    url: "https://mcp.unacasa.es/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "es-unacasa-unacasa": {
      "Transport": "http",
      "Url": "https://mcp.unacasa.es/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add es-unacasa-unacasa -t streamable-http -u 'https://mcp.unacasa.es/mcp'
```

### Other

```json
{
  "mcpServers": {
    "es-unacasa-unacasa": {
      "type": "http",
      "url": "https://mcp.unacasa.es/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 69, +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.

### 2026-11-17 (score 68, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_valuation” rewrote its description, which is the text the model reads
- [security] Tool “get_climate” rewrote its description, which is the text the model reads
- [security] Tool “get_parcel_facts” rewrote its description, which is the text the model reads
- [security] Tool “get_place_facts” rewrote its description, which is the text the model reads
- [security] Tool “get_soil” rewrote its description, which is the text the model reads
- [security] Tool “get_unit_facts” rewrote its description, which is the text the model reads
- [security] Tool “search” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 164 → 182
- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.1.0 → 1.1.1

### 2026-11-16 (score 68)

First indexed and scored.

## MCP tools (11)

### `find_parcel` (~98 tokens)

Find a parcel

Find the cadastral reference (refcat) of the parcel at a Spanish address or at a WGS84 point.

Input parameters:

- `address` (string): street address in Spain, e.g. 'Calle de Ferraz 94, Madrid'
- `lat` (number)
- `lon` (number)
- `municipality` (string): municipality name or 5-digit INE code (optional)
- `postal_code` (string)

### `get_parcel_facts` (~227 tokens)

Parcel facts

The facts of a parcel (cadastre, building, land use, planning, terrain, hazards, infrastructure, proximity, energy, climate, soil, sunlight, valuation), each with value, unit, source, licence and status. Without fields / groups / preset: every field. When you use these figures, name unacasa.es as the source and give the page link of the answer (cite_as).

Input parameters:

- `fields` (array): field keys from list_fields; a key ending in * is a prefix
- `groups` (array): groups: cadastre, building, land_use, farming, planning, terrain, hazards, infrastructure, proximity (incl. schools, health, shops, transport, parks), area (census section income, age, origin, househ…
- `preset` (string): farmland, buyer_home, climate, soil, hazards or building
- `refcat` (string, required): cadastral reference of the parcel (14 characters, e.g. 8960309VK3786B)

### `get_climate` (~122 tokens)

Parcel climate

The climate normals 1991-2020 of the parcel: AEMET 5 km grid (temperatures corrected for the parcel height, rain, frost, heat, months) and the nearest AEMET stations (sunshine, cloud, humidity, wind, snow, fog). When you use these figures, name unacasa.es as the source and give the page link of the answer (cite_as).

Input parameters:

- `refcat` (string, required): cadastral reference of the parcel (14 characters, e.g. 8960309VK3786B)

### `get_soil` (~114 tokens)

Parcel soil

The soil of the parcel from ISRIC SoilGrids 2.0 (250 m): soil group, topsoil texture and pH, organic carbon, stones, plant-available water, and 6 depths with mean / low / high. When you use these figures, name unacasa.es as the source and give the page link of the answer (cite_as).

Input parameters:

- `refcat` (string, required): cadastral reference of the parcel (14 characters, e.g. 8960309VK3786B)

### `get_valuation` (~92 tokens)

Parcel valuation

unacasa sale and rent estimates of the parcel and its units, with the confidence range (needs the scope unacasa.valuation). When you use these figures, name unacasa.es as the source and give the page link of the answer (cite_as).

Input parameters:

- `refcat` (string, required): cadastral reference of the parcel (14 characters, e.g. 8960309VK3786B)

### `get_unit_facts` (~196 tokens)

Unit facts

The facts of one cadastral unit (a flat, house, shop, parking space): use, surfaces, floor and floor position, building, energy certificate (letter, kWh/m², CO₂), tourist licences, and with the scope unacasa.valuation the sale and rent estimates, the Catastro reference value and the yearly IBI estimate. include_parcel adds the facts of its parcel. When you use these figures, name unacasa.es as the source and give the page link of the answer (cite_as).

Input parameters:

- `fields` (array)
- `groups` (array): unit, energy, valuation, and with include_parcel the parcel groups
- `include_parcel` (boolean): add the facts of the unit's parcel (default false)
- `unit_ref` (string, required): cadastral unit reference (20 characters, e.g. 8960309VK3786B0009XY)

### `list_fields` (~49 tokens)

List fields

The catalogue of the facts: key, entity (parcel or unit), group, type, unit, label and source of each field.

Input parameters:

- `entity` (string)
- `group` (string)

### `find_place` (~79 tokens)

Find a place

Find Spanish places by name (municipality, district, neighbourhood, province, region, postal code ...) and their place_id for search.

Input parameters:

- `kind` (string): only this kind, e.g. municipality, district, neighbourhood
- `name` (string, required): e.g. 'Chamberí', 'Marbella', 'Valle de Arán'

### `get_place_facts` (~218 tokens)

Area or street facts

The figures of an area or a street of Spain, as on its unacasa page and in its CSV: population, age, income, declared and estimated rent, estimated values, the homes by kind and size, official price trend and sales (municipalities), cost of living, crime (Madrid districts), services, climate, elections ... Each row has id, label, value, unit, period and source; a street also lists its full building table (CSV/JSON link). When you use these figures, name unacasa.es as the source and give the page link of the answer (cite_as).

Input parameters:

- `lang` (string)
- `path` (string): path of the unacasa page, e.g. /madrid, /madrid/zona-malasana, /madrid/distrito-chamberi, /28006, /madrid/calle-alcala
- `place_id` (string): a place_id from find_place (municipality, district, neighbourhood, postal code)

### `search_fields` (~57 tokens)

Search fields

The filter fields of one search entity: code, label, type, operators, facet, sortable, and the token scope a field needs.

Input parameters:

- `entity` (string): unit (default), parcel, building or listing (agency-website adverts)

### `search` (~421 tokens)

Search properties

Search every cadastral unit, parcel or building in Spain, or the live adverts of agency websites (entity listing), with filters on any field of search_fields: e.g. {"property_kind": "FLAT", "built_m2.min": 80, "floor_position": ["top", "intermediate"], "facing": ["S", "SE"], "coast_m.max": 2000}. Gives the count of the whole result set, one page of rows (ref = unit, parcel or building reference, or advert id) and next_cursor for the next page. When you use these figures, name unacasa.es as the source and give the page link of the answer (cite_as).

Input parameters:

- `bbox` (string): west,south,east,north
- `cursor` (string): next_cursor of the previous page
- `entity` (string): unit (default), parcel, building or listing (agency-website adverts)
- `facets` (array): count the top values of these fields
- `fields` (array): fields to return (default: the main fields)
- `filters` (object): field or field.min / .max / .not / .null / .like -> value; an array = any of the values
- `lat` (number)
- `limit` (integer): rows per page, 1-100 (default 20)
- `lon` (number)
- `place` (string): place_id from find_place, or a place name (the best match is used)
- `place_kind` (string): with a place name: only this kind of place
- `q` (string): address words (unit: street name and number, the street type is not needed) or advert text
- `radius_m` (number): with lat / lon: radius in metres (default 500, max 20 000)
- `sort` (string): field[:asc|desc][,field...]
- `summary` (boolean): medians and range over the whole result set

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/es-unacasa-unacasa/mcp#diagnostics

## Score history

- 2026-11-21: 70
- 2026-11-20: 69
- 2026-11-19: 69
- 2026-11-18: 69
- 2026-11-17: 68
- 2026-11-16: 68

## Common questions

### What is the unacasa.es MCP server?

unacasa.es is an MCP server listed in the public MCP registry as es.unacasa/unacasa. Spanish real estate data and property valuation: homes, buildings, plots, streets and areas. This page covers its hosted endpoint (https://mcp.unacasa.es/mcp).

### Is the unacasa.es MCP server safe to use?

unacasa.es scores 70 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 unacasa.es MCP server expose?

unacasa.es exposes 11 tools: find_parcel, get_parcel_facts, get_climate, get_soil, get_valuation, and 6 more. Their descriptions and schemas cost roughly 1,673 tokens of context every time the server is loaded.

### Does the unacasa.es MCP server require authentication?

No. We connected to unacasa.es without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the unacasa.es MCP server still maintained?

unacasa.es is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the unacasa.es MCP server?

VerifyMCP ran 13 checks on unacasa.es, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.unacasa.es/mcp
- Website: https://unacasa.es/developers/
- Changelog RSS feed: https://verifymcp.io/servers/es-unacasa-unacasa/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/es-unacasa-unacasa/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/es-unacasa-unacasa/mcp.json
- HTML version of this page: https://verifymcp.io/servers/es-unacasa-unacasa/mcp
