com.prediohq/catastro
REMOTE · API.PREDIOHQ.COM · SCANNED AUG 3
Catastro espanol en JSON limpio: inmuebles por referencia catastral, coordenadas o direccion.
Available components
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 →
Endpoint Security71
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
- 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 Usability63
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · api.prediohq.com
claude mcp add --transport http com-prediohq-catastro https://api.prediohq.com/mcp
[mcp_servers.com-prediohq-catastro] url = "https://api.prediohq.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-prediohq-catastro": {
"type": "remote",
"url": "https://api.prediohq.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-prediohq-catastro --url https://api.prediohq.com/mcp --transport streamable-http
mcp_servers:
com-prediohq-catastro:
url: "https://api.prediohq.com/mcp" {
"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.
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.
- 3 Aug 26 +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.
- 31 Jul 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +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.
- 28 Jul 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.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 64
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 3 Aug 2026 · Probed https://api.prediohq.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=prediohq.com | CN=WE1,O=Google Trust Services,C=US | 29 Jun 2026 | 27 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | fd9fbc0b65a048d113512ce9efac1de1 |
| SANs: prediohq.com, api.prediohq.com, *.api.prediohq.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of api.prediohq.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| prediohq.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.prediohq.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.prediohq.com/mcp | Inconclusive | 401 |
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.
consultar_inmueble_catastro Consultar inmueble del Catastro espanol ~196
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.
| Name | Type | Req | Description |
|---|---|---|---|
| referenciaCatastral | string | yes | Referencia catastral espanola de 14 (parcela), 18 o 20 (inmueble) caracteres alfanumericos. Ejemplo: 9872023VH5797S0001WX |
| Name | Type | Req | Description |
|---|---|---|---|
| candidates | — | yes | — |
| message | string|null | yes | — |
| property | — | yes | — |
| source | object | yes | — |
| status | string | yes | — |
No examples provided.
consultar_inmueble_por_coordenadas Consultar inmueble del Catastro espanol por coordenadas ~282
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).
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Latitud en grados decimales (WGS84/ETRS89). Rango -90..90. Ej: 41.3915 |
| lon | number | yes | 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). |
| Name | Type | Req | Description |
|---|---|---|---|
| candidates | — | yes | — |
| message | string|null | yes | — |
| property | — | yes | — |
| source | object | yes | — |
| status | string | yes | — |
No examples provided.
consultar_inmueble_por_direccion Consultar inmueble del Catastro espanol por direccion ~469
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Municipio por NOMBRE, p. ej. 'SANTA CRUZ DE MUDELA', 'MADRID'. Obligatorio. |
| province | string | yes | 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 | yes | Nombre de la via SIN la sigla, p. ej. 'GLORIA', 'ALCALA'. Obligatorio. |
| streetNumber | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| candidates | — | yes | — |
| message | string|null | yes | — |
| property | — | yes | — |
| source | object | yes | — |
| status | string | yes | — |
No examples provided.