predio
Registry code: 84ca0ad33a484506
Servidor MCP que traduce el Catastro Inmobiliario de Espana (OVC) a JSON. Usa `consultar_inmueble_catastro` con una referencia catastral (14/18/20 caracteres), `consultar_inmueble_por_coordenadas` con latitud/longitud (p. ej. un punto de un mapa), o `consultar_inmueble_por_direccion` con provincia/municipio/via/numero (p. ej. el texto de un anuncio), para obtener clase, uso, superficie construida, anio y direccion de un inmueble. Las tres devuelven el mismo JSON normalizado.
- endpoint
- https://api.prediohq.com/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is predio live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is predio free to use?
- Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
- What tools does predio have?
- 3 tools: consultar_inmueble_catastro, consultar_inmueble_por_coordenadas, consultar_inmueble_por_direccion.
- Is predio safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.2%· all time 99.2%
last good check
of 3 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- used for
- look up a spanish property by cadastral reference
- find cadastral data by coordinates
- find cadastral data by address
- takes → gives
- text, data → data
- tools
- 3 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
consultar_inmueble_catastro reads auth-required 15h ago
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.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "referenciaCatastral" ], "properties": { "referenciaCatastral": { "type": "string", "pattern": "^[0-9A-Za-z]{14}(?:[0-9A-Za-z]{4}(?:[0-9A-Za-z]{2})?)?$", "maxLength": 20, "minLength": 14, "description": "Referencia catastral espanola de 14 (parcela), 18 o 20 (inmueble) caracteres alfanumericos. Ejemplo: 9872023VH5797S0001WX" } }, "additionalProperties": false }arguments 17 linesconsultar_inmueble_por_coordenadas reads auth-required 15h ago
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).
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "lat", "lon" ], "properties": { "lat": { "type": "number", "maximum": 90, "minimum": -90, "description": "Latitud en grados decimales (WGS84/ETRS89). Rango -90..90. Ej: 41.3915" }, "lon": { "type": "number", "maximum": 180, "minimum": -180, "description": "Longitud en grados decimales (WGS84/ETRS89). Rango -180..180. Ej: 2.1620" }, "srs": { "type": "string", "description": "Codigo EPSG del sistema de referencia. Soportados: EPSG:4326 (WGS84, por defecto) y EPSG:4258 (ETRS89)." } }, "additionalProperties": false }arguments 27 linesconsultar_inmueble_por_direccion reads auth-required 15h ago
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).
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "province", "municipality", "streetName", "streetNumber" ], "properties": { "door": { "type": "string", "description": "Puerta, si aplica. Opcional: afina a un inmueble concreto." }, "block": { "type": "string", "description": "Bloque, si aplica (propiedad horizontal). Opcional: afina a un inmueble concreto." }, "floor": { "type": "string", "description": "Planta, si aplica. Opcional: afina a un inmueble concreto." }, "province": { "type": "string", "minLength": 1, "description": "Provincia por NOMBRE (no codigo), p. ej. 'CIUDAD REAL', 'MADRID'. Obligatorio. Territorio comun (excluye Pais Vasco y Navarra)." }, "stairway": { "type": "string", "description": "Escalera, si aplica. Opcional: afina a un inmueble concreto." }, "streetName": { "type": "string", "minLength": 1, "description": "Nombre de la via SIN la sigla, p. ej. 'GLORIA', 'ALCALA'. Obligatorio." }, "streetType": { "type": "string", "description": "Tipo/sigla de via del Catastro: CL (calle), AV (avenida), PZ (plaza), CR (carretera), CM (camino)... Opcional pero recomendado para acertar la via." }, "municipality": { "type": "string", "minLength": 1, "description": "Municipio por NOMBRE, p. ej. 'SANTA CRUZ DE MUDELA', 'MADRID'. Obligatorio." }, "streetNumber": { "type": "string", "minLength": 1, "description": "Numero de policia, p. ej. '51'. Obligatorio." } }, "additionalProperties": false }arguments 53 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id84ca0ad33a484506.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/84ca0ad33a484506/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/84ca0ad33a484506?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.