# com.prediohq/catastro (remote · api.prediohq.com)

Catastro espanol en JSON limpio: inmuebles por referencia catastral, coordenadas o direccion.

- Trust score: 70/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.prediohq.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/com-prediohq-catastro/api.md), [page](https://verifymcp.io/servers/com-prediohq-catastro/api)

## Channel facts

- Endpoint: `https://api.prediohq.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## 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-08-03.

- **Endpoint Security**: 71/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - 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**: 63/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1085 tokens (~361/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-prediohq-catastro https://api.prediohq.com/mcp
```

### Codex

```toml
[mcp_servers.com-prediohq-catastro]
url = "https://api.prediohq.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-prediohq-catastro": {
      "type": "remote",
      "url": "https://api.prediohq.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-prediohq-catastro --url https://api.prediohq.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-prediohq-catastro:
    url: "https://api.prediohq.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-prediohq-catastro": {
      "type": "http",
      "url": "https://api.prediohq.com/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-08-03 (score 70, +1)

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

### 2026-07-31 (score 69, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 66, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 66, +1)

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

### 2026-07-28 (score 65, +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-07-27 (score 64, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 64)

First indexed and scored.

## MCP tools (3)

### `consultar_inmueble_catastro` (~196 tokens)

Consultar inmueble del Catastro espanol

Devuelve datos catastrales no protegidos de un inmueble espanol a partir de su referencia catastral: clase (urbano/rustico), uso principal, superficie construida (m2), anio de construccion, direccion normalizada y desglose de construcciones (urbano) o cultivos (rustico). Traduce el servicio SOAP/XML de la Direccion General del Catastro (OVC) a JSON denso. Acepta referencias de 14/18/20 caracteres; si la de 14 (parcela) resuelve a varios inmuebles, devuelve la lista de candidatos para desambiguar.

Input parameters:

- `referenciaCatastral` (string, required): Referencia catastral espanola de 14 (parcela), 18 o 20 (inmueble) caracteres alfanumericos. Ejemplo: 9872023VH5797S0001WX

Output parameters:

- `candidates`
- `message` (string|null)
- `property`
- `source` (object)
- `status` (string)

### `consultar_inmueble_por_coordenadas` (~282 tokens)

Consultar inmueble del Catastro espanol por coordenadas

Resuelve y devuelve los datos catastrales no protegidos de un inmueble espanol a partir de unas coordenadas geograficas (latitud/longitud). Util para resolver el inmueble desde un punto de un mapa cuando no se tiene la referencia catastral. SRS soportados: EPSG:4326 (WGS84, por defecto) y EPSG:4258 (ETRS89). Devuelve el MISMO JSON normalizado que la consulta por referencia catastral (clase urbano/rustico, uso, superficie construida, anio, direccion); si el punto cae en una parcela con varios inmuebles, devuelve la lista de candidatos. Cobertura: territorio comun (excluye Pais Vasco y Navarra).

Input parameters:

- `lat` (number, required): Latitud en grados decimales (WGS84/ETRS89). Rango -90..90. Ej: 41.3915
- `lon` (number, required): Longitud en grados decimales (WGS84/ETRS89). Rango -180..180. Ej: 2.1620
- `srs` (string): Codigo EPSG del sistema de referencia. Soportados: EPSG:4326 (WGS84, por defecto) y EPSG:4258 (ETRS89).

Output parameters:

- `candidates`
- `message` (string|null)
- `property`
- `source` (object)
- `status` (string)

### `consultar_inmueble_por_direccion` (~469 tokens)

Consultar inmueble del Catastro espanol por direccion

Resuelve y devuelve los datos catastrales no protegidos de un inmueble urbano espanol a partir de su DIRECCION (provincia, municipio, via y numero). Util para resolver el inmueble desde el texto de un anuncio cuando no se tiene la referencia catastral. Provincia y municipio van por NOMBRE (no codigo); `streetType` es la sigla de la via (CL, AV, PZ...) y se recomienda para acertar. Devuelve el MISMO JSON normalizado que la consulta por referencia (clase urbano/rustico, uso, superficie construida, anio, direccion); si el numero corresponde a varios inmuebles (propiedad horizontal), devuelve la lista de candidatos para desambiguar (afina con bloque/escalera/planta/puerta). Solo direcciones urbanas; cobertura: territorio comun (excluye Pais Vasco y Navarra).

Input parameters:

- `block` (string): Bloque, si aplica (propiedad horizontal). Opcional: afina a un inmueble concreto.
- `door` (string): Puerta, si aplica. Opcional: afina a un inmueble concreto.
- `floor` (string): Planta, si aplica. Opcional: afina a un inmueble concreto.
- `municipality` (string, required): Municipio por NOMBRE, p. ej. 'SANTA CRUZ DE MUDELA', 'MADRID'. Obligatorio.
- `province` (string, required): Provincia por NOMBRE (no codigo), p. ej. 'CIUDAD REAL', 'MADRID'. Obligatorio. Territorio comun (excluye Pais Vasco y Navarra).
- `stairway` (string): Escalera, si aplica. Opcional: afina a un inmueble concreto.
- `streetName` (string, required): Nombre de la via SIN la sigla, p. ej. 'GLORIA', 'ALCALA'. Obligatorio.
- `streetNumber` (string, required): Numero de policia, p. ej. '51'. Obligatorio.
- `streetType` (string): Tipo/sigla de via del Catastro: CL (calle), AV (avenida), PZ (plaza), CR (carretera), CM (camino)... Opcional pero recomendado para acertar la via.

Output parameters:

- `candidates`
- `message` (string|null)
- `property`
- `source` (object)
- `status` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-prediohq-catastro/api#diagnostics

## Score history

- 2026-08-03: 70
- 2026-08-02: 69
- 2026-08-01: 69
- 2026-07-31: 69
- 2026-07-30: 66
- 2026-07-29: 66
- 2026-07-28: 65
- 2026-07-27: 64
- 2026-07-26: 64

## Links

- Remote endpoint: https://api.prediohq.com/mcp
- Authorisation metadata: https://api.prediohq.com/.well-known/oauth-protected-resource/mcp
- Website: https://prediohq.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-prediohq-catastro/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-prediohq-catastro/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-prediohq-catastro/api