Atalaya · Los riesgos de tu ciudad MCP server
city.atalaya/riesgosatalaya.citystreamable-httpv1.1.3Scanned
Riesgos en vivo en Colombia: lluvia, inundaciones, incendios, sismos y reportes ciudadanos.
3 tools: 3 change things.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
3 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 Radar only lists and labels, and these labels are the same either way.
What the Atalaya · Los riesgos de tu ciudad MCP server can do
The Atalaya · Los riesgos de tu ciudad MCP server is published by atalaya.city, a domain the MCP Registry verified. It has 3 tools. It can create or change data (3 tools: consultar_riesgo, perfil_cuadro and explicar_cobertura), but cannot delete data. None of its tools only reads.
2 tools bring in text other people can write (consultar_riesgo and perfil_cuadro).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 10, 2026, version 1.1.3.
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.
3 tools
Changes things 3Claude Code: ask
consultar_riesgoRiesgos activos alrededor de un lugar de Colombia, en vivo: eventos de fuentes oficiales (lluvia fuerte, crecientes y vendavales medidos por las estaciones del IDIGER en Bogotá y l…Reads text others writeNo 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.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Riesgos activos alrededor de un lugar de Colombia, en vivo: eventos de fuentes oficiales (lluvia fuerte, crecientes y vendavales medidos por las estaciones del IDIGER en Bogotá y los pluviómetros del SIATA en Medellín y el Valle de Aburrá), sismos recientes del USGS (todo el país), incendios activos detectados por satélite (NASA FIRMS, todo el país), reportes ciudadanos verificados (inundaciones, granizo, huecos, vías bloqueadas, árboles o cables caídos, deslizamientos, incendios) y el pronóstico de lluvia de las próximas 3 y 6 horas para la localidad o comuna más cercana (MET Norway). Acepta un lugar en texto ("Suba, Bogotá", "calle 80 con Boyacá", "Envigado") o coordenadas. Sin datos personales. Úsala cuando alguien pregunte si hay riesgo, lluvia, inundación, sismo, incendio o problemas en una zona de Colombia o si va a llover en las próximas horas.
Annotations the server declares
- title: Consultar riesgos activos en una zona
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
explicar_coberturaGuía informativa para Colombia por tipo de riesgo: pasos inmediatos de seguridad, qué seguros suelen cubrir ese evento (todo riesgo de vehículo, hogar, construcción, accidentes per…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 Guía informativa para Colombia por tipo de riesgo: pasos inmediatos de seguridad, qué seguros suelen cubrir ese evento (todo riesgo de vehículo, hogar, construcción, accidentes personales, vida, responsabilidad civil, SOAT) y qué no suelen cubrir. No da precios. Tipos: lluvia, inundacion, sismo, vendaval, granizo, vial, deslizamiento, incendio, hueco, caida_objetos, obras, hurto.
Annotations the server declares
- title: Qué hacer y qué seguros responden ante un riesgo
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
perfil_cuadroQué tan expuesto está un lugar de Colombia en general, no solo ahora: perfil del cuadro de 150 m que contiene el punto.Reads text others writeNo 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.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Qué tan expuesto está un lugar de Colombia en general, no solo ahora: perfil del cuadro de 150 m que contiene el punto. Trae el riesgo general (suma de riesgos de 8 familias: agua, terreno, sismo y, cuando se publique lo observado en la calle, vías, peatones y ciclistas, redes eléctricas, árboles y obras; medio suma 1 y alto 2, con cuántas familias tienen dato), la amenaza oficial principal (POT de Bogotá y Medellín, estudios y manchas de La Niña del IDEAM) comparada con el resto del municipio, la zona sísmica de la NSR-10 y el suelo de la microzonificación de Bogotá, el relieve, lo que pasa ahora en el cuadro (lluvia, crecientes, pronóstico, sismos con su intensidad), la gente expuesta (DANE 2018 y estimado 2026, viviendas, edificios) y los eventos de los últimos 12 meses. Acepta un lugar en texto, coordenadas o el código del cuadro (columna:fila). Úsala cuando alguien pregunte si una zona es riesgosa, si se inunda, si tiene amenaza de deslizamiento o de sismo, o antes de recomendar un seguro para un sitio. Es por cuadro, no por predio.
Annotations the server declares
- title: Perfil de riesgo de un lugar (cuadro de 150 m)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: 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 outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- 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.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 17, 2026, 15:23 UTC, unchanged since Nov 10, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://atalaya.city/mcp: tools/list returned 3 tools to an anonymous client, including consultar_riesgo (write), perfil_cuadro (write), explicar_cobertura (write)
Posture changes
- Nov 10, 2026
- Tools that change things, listed without credentials: 2 to 3
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.
PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 3.View diff
- Tools that change things, listed without credentials: 2 to 3
Tools1 added, 2 changed.+1 added~2 changedView diff
- Added:perfil_cuadroChanges things
- Changed:consultar_riesgoChanges thingsdescriptionannotations
- Changed:explicar_coberturaChanges thingsdescriptionannotations
Install
Pinned to version 1.1.3. Values in angle brackets are yours to fill in.
claude mcp add --transport http riesgos https://atalaya.city/mcpclaude mcp add --transport http riesgos https://atalaya.city/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__riesgos__consultar_riesgo",
"mcp__riesgos__perfil_cuadro",
"mcp__riesgos__explicar_cobertura"
],
"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 riesgos. Review it before you use it.
Capability tags behind 2 rules
- mcp__riesgos__consultar_riesgo untrusted-input
- mcp__riesgos__perfil_cuadro untrusted-input
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://radar.anlyon.com/api/v1/servers/city.atalaya/riesgos/verify?hash=d20084a6329389e396bd404c74510cfcff255b28fe63e420cf95e6179e35544e" | jq -e '.changed == false'Pinned hash d20084a63293, from Nov 10, 2026, 15:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/city.atalaya/riesgos/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/city.atalaya/riesgos)Source: MCP Registry. Synced Nov 10, 2026, 15:17 UTC.
Atalaya · Los riesgos de tu ciudad MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Atalaya · Los riesgos de tu ciudad MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 3 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 Atalaya · Los riesgos de tu ciudad MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Atalaya · Los riesgos de tu ciudad 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 Atalaya · Los riesgos de tu ciudad MCP server have?
- 3 tools: 3 write. consultar_riesgo, perfil_cuadro and explicar_cobertura.
Does the Atalaya · Los riesgos de tu ciudad MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Atalaya · Los riesgos de tu ciudad MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Atalaya · Los riesgos de tu ciudad MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.