Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Catastra

REMOTE · CATASTRA.LDEST.DEV

Parcelas catastrales de CABA y AMBA (Buenos Aires) desde tu asistente de IA (MCP remoto).

+4 this week 76 Trust /100

Last scanned (19 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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 Security83
Transport & Reachability100
Schema Quality & AI Usability52
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 283 tokens (~56/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

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 →

Changelog

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 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

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

  • 17 Nov 26 +1

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

  • 15 Nov 26 +1

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

  • 13 Nov 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.

  • 10 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.

  • 8 Nov 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.

  • 6 Nov 26 +1
    • Tool “cobertura_y_fuentes” rewrote its description, which is the text the model reads security
    • Tool “ficha_parcela” rewrote its description, which is the text the model reads security
    • Tool “parcela_por_coordenada” rewrote its description, which is the text the model reads security
    • Tool “parcela_por_nomenclatura” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
    • “parcela_por_nomenclatura” added an optional parameter “partida” cosmetic
    • “parcela_por_nomenclatura” added an optional parameter “partido” cosmetic
    • Tool “parcela_por_nomenclatura” changed its title: Buscar por SMP → Buscar por nomenclatura, SMP o partida cosmetic
Diagnostics

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://catastra.ldest.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=ldest.dev CN=WE1,O=Google Trust Services,C=US 10 Nov 2026 8 Feb 2027 ECDSA 256 ECDSA-SHA256 f2050900447da0e313f3778b001cc310
SANs: ldest.dev, *.ldest.dev
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

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of catastra.ldest.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
ldest.dev. No DS 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

WWW-Authenticate challenge Bearer realm="catastra"

Bearer realm="catastra"

Protected resource metadata

Retrieved No
Problem No resource metadata

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://catastra.ldest.dev/mcp Verified 200
http (plaintext) http://catastra.ldest.dev/mcp HTTPS enforced 301 https://catastra.ldest.dev/mcp
MCP tools · 5 exposed · ~283 tokens

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 →

Tool Tokens
cobertura_y_fuentes ~24

Devuelve cobertura disponible y atribuciones. Get available coverage and sources.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

ficha_parcela ~49

Devuelve la ficha de una parcela CABA o PBA. Get a CABA or PBA parcel record.

NameTypeReqDescription
idstringyes–
incluir_geometriaboolean––

Structured output declared, but exposes no named fields.

No examples provided.

parcela_por_coordenada ~55

Busca parcelas en un punto de CABA o PBA. Find CABA or PBA parcels.

NameTypeReqDescription
incluir_geometriaboolean––
latnumberyes–
lonnumberyes–

Structured output declared, but exposes no named fields.

No examples provided.

parcela_por_nomenclatura ~79

Busca SMP CABA, CCA PBA o partida y partido. Find parcels by cadastral identifier.

NameTypeReqDescription
incluir_geometriaboolean––
jurisdiccionstring––
nomenclaturastring––
partida–––
partido–––
smpstring––

Structured output declared, but exposes no named fields.

No examples provided.

parcelas_en_area ~76

Busca parcelas en hasta 1 km², lados de hasta 2 km. Find parcels in a small area.

NameTypeReqDescription
cursor–––
limiteinteger––
max_latnumberyes–
max_lonnumberyes–
min_latnumberyes–
min_lonnumberyes–

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Catastra MCP server?

Catastra is a hosted endpoint at https://catastra.ldest.dev/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 · catastra.ldest.dev

# add to Claude Code
claude mcp add --transport http dev-ldest-catastra-catastra 'https://catastra.ldest.dev/mcp'
Common questions

What is the Catastra MCP server?

Catastra is an MCP server listed in the public MCP registry as dev.ldest.catastra/catastra. Parcelas catastrales de CABA y AMBA (Buenos Aires) desde tu asistente de IA (MCP remoto). This page covers its hosted endpoint (https://catastra.ldest.dev/mcp).

Is the Catastra MCP server safe to use?

Catastra scores 76 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 Catastra MCP server expose?

Catastra exposes 5 tools: parcela_por_coordenada, parcela_por_nomenclatura, ficha_parcela, parcelas_en_area, cobertura_y_fuentes. Their descriptions and schemas cost roughly 283 tokens of context every time the server is loaded.

Does the Catastra MCP server require authentication?

Yes. Catastra asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the Catastra MCP server still maintained?

Catastra 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 Catastra MCP server?

VerifyMCP ran 13 checks on Catastra, 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.