Catastra MCP server
dev.ldest.catastra/catastracatastra.ldest.devstreamable-httpv1.0.0Scanned
Consultá parcelas catastrales de Argentina desde tu asistente de IA (MCP remoto).
5 tools: 5 change things.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
With Anlyon
5 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. anlyon.dev only lists and labels, and these labels are the same either way.
What the Catastra MCP server can do
The Catastra MCP server is published by catastra.ldest.dev, a domain the MCP Registry verified. It has 5 tools. It can create or change data (5 tools: parcela_por_coordenada, parcela_por_nomenclatura, ficha_parcela, parcelas_en_area and 1 more), but cannot delete data. None of its tools only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Nov 5, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 5Claude Code: ask
cobertura_y_fuentesDevuelve cobertura CABA y atribuciones.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Devuelve cobertura CABA y atribuciones. Get CABA coverage and sources.
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
ficha_parcelaDevuelve la ficha de una parcela de CABA.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Devuelve la ficha de una parcela de CABA. Get a CABA parcel record.
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
parcela_por_coordenadaBusca parcelas en un punto de CABA.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Busca parcelas en un punto de CABA. Find parcels at a point in CABA.
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
parcela_por_nomenclaturaBusca un SMP de CABA con o sin espacios.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Busca un SMP de CABA con o sin espacios. Find a CABA parcel by SMP.
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
parcelas_en_areaBusca parcelas en hasta 1 km², lados de hasta 2 km.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Busca parcelas en hasta 1 km², lados de hasta 2 km. Find parcels in a small area.
Annotations the server declares
- openWorldHint: false
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http catastra https://catastra.ldest.dev/mcpclaude mcp add --transport http catastra https://catastra.ldest.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__catastra__parcela_por_coordenada",
"mcp__catastra__parcela_por_nomenclatura",
"mcp__catastra__ficha_parcela",
"mcp__catastra__parcelas_en_area",
"mcp__catastra__cobertura_y_fuentes"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as catastra. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://anlyon.dev/api/v1/servers/dev.ldest.catastra/catastra/verify?hash=24673c1d3d73010f7beea84d0702e333bba05903f0e8a81226a17842841ff940" | jq -e '.changed == false'Pinned hash 24673c1d3d73, from Nov 5, 2026, 17:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://anlyon.dev/servers/dev.ldest.catastra/catastra/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://anlyon.dev/servers/dev.ldest.catastra/catastra)Source: MCP Registry. Synced Nov 5, 2026, 17:17 UTC.
Catastra MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Catastra MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Catastra MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Catastra MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Catastra MCP server have?
- 5 tools: 5 write. parcela_por_coordenada, parcela_por_nomenclatura, ficha_parcela, parcelas_en_area and cobertura_y_fuentes.
Does the Catastra MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Catastra MCP server changed its tools?
- Not since anlyon.dev started tracking it. Last scanned Nov 5, 2026.