unacasa.es
REMOTE · MCP.UNACASA.ES
Spanish real estate data and property valuation: homes, buildings, plots, streets and areas.
Available components
Last scanned (16 hours ago)
Scores higher than 54% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Maps and Location
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. 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. 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 Usability59
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 77% 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +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.
- 18 Nov 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.
- 17 Nov 26 0
- 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 security
- Schema quality: 164 → 182 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.1.0 → 1.1.1 functional
- 16 Nov 26 68
First indexed and scored.
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 21 Nov 2026 · Probed https://mcp.unacasa.es/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.unacasa.es | CN=YE2,O=Let's Encrypt,C=US | 26 Oct 2026 | 24 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 69db83a498748e7e1686f5513d1c7a74cae |
| SANs: mcp.unacasa.es | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.unacasa.es. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| es. | DS published | 4901, 54404 | 8, 8 | Verified |
| unacasa.es. | No DS | 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://mcp.unacasa.es/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.unacasa.es/mcp | HTTPS enforced | 301 | https://mcp.unacasa.es/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 →
find_parcel Find a parcel ~98
Find the cadastral reference (refcat) of the parcel at a Spanish address or at a WGS84 point.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No output schema declared.
No examples provided.
find_place Find a place ~79
Find Spanish places by name (municipality, district, neighbourhood, province, region, postal code ...) and their place_id for search.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | only this kind, e.g. municipality, district, neighbourhood |
| name | string | yes | e.g. 'Chamberí', 'Marbella', 'Valle de Arán' |
No output schema declared.
No examples provided.
get_climate Parcel climate ~122
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).
| Name | Type | Req | Description |
|---|---|---|---|
| refcat | string | yes | cadastral reference of the parcel (14 characters, e.g. 8960309VK3786B) |
No output schema declared.
No examples provided.
get_parcel_facts Parcel facts ~227
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | cadastral reference of the parcel (14 characters, e.g. 8960309VK3786B) |
No output schema declared.
No examples provided.
get_place_facts Area or street facts ~218
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
get_soil Parcel soil ~114
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).
| Name | Type | Req | Description |
|---|---|---|---|
| refcat | string | yes | cadastral reference of the parcel (14 characters, e.g. 8960309VK3786B) |
No output schema declared.
No examples provided.
get_unit_facts Unit facts ~196
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | cadastral unit reference (20 characters, e.g. 8960309VK3786B0009XY) |
No output schema declared.
No examples provided.
get_valuation Parcel valuation ~92
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).
| Name | Type | Req | Description |
|---|---|---|---|
| refcat | string | yes | cadastral reference of the parcel (14 characters, e.g. 8960309VK3786B) |
No output schema declared.
No examples provided.
list_fields List fields ~49
The catalogue of the facts: key, entity (parcel or unit), group, type, unit, label and source of each field.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | – | – |
| group | string | – | – |
No output schema declared.
No examples provided.
search Search properties ~421
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
search_fields Search fields ~57
The filter fields of one search entity: code, label, type, operators, facet, sortable, and the token scope a field needs.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | – | unit (default), parcel, building or listing (agency-website adverts) |
No output schema declared.
No examples provided.
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.
remote · mcp.unacasa.es
claude mcp add --transport http es-unacasa-unacasa 'https://mcp.unacasa.es/mcp'
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.