city.atalaya/riesgos
REMOTE · ATALAYA.CITY
Riesgos en vivo en Colombia: lluvia, inundaciones, incendios, sismos y reportes de vecinos.
Available components
Last scanned (23 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Maps and Location
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 1142 tokens (~380/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 Management30
- Stability observed for 9 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 4 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 334 → 380 ▼ functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “perfil_cuadro” functional
- 3 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.
- 2 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “consultar_riesgo” rewrote its description, which is the text the model reads security
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “explicar_cobertura” rewrote its description, which is the text the model reads security
- 28 Oct 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 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
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 4 Nov 2026 · Probed https://atalaya.city/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=atalaya.city | CN=YE2,O=Let's Encrypt,C=US | 25 Oct 2026 | 23 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6bbc95eab0333415b23785ec679b5917292 |
| SANs: atalaya.city, www.atalaya.city | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of atalaya.city. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| city. | present | 57326 | 8 | Verified |
| atalaya.city. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://www.googletagmanager.com https://www.google-analytics.com https://unpkg.com https://cdnjs.cloudflare.com https://cdn.jsdelivr.net blob:; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://unpkg.com https://cdnjs.cloudflare.com; img-src 'self' data: blob: * https://tile.openstreetmap.org https://cartodb-basemaps-a.global.ssl.fastly.net https://cartodb-basemaps-b.global.ssl.fastly.net https://cartodb-basemaps-c.global.ssl.fastly.net https://cartodb-basemaps-d.global.ssl.fastly.net https://a.basemaps.cartocdn.com https://b.basemaps.cartocdn.com https://c.basemaps.cartocdn.com https://d.basemaps.cartocdn.com; font-src 'self' * https://fonts.gstatic.com; connect-src 'self' https://www.google-analytics.com https://analytics.google.com https://stats.g.doubleclick.net https://api.maptiler.com https://tiles.openfreemap.org https://photon.komoot.io https://unpkg.com https://cdnjs.cloudflare.com https://lapoliza.io blob:; repo |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(self), microphone=(), camera=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://atalaya.city/mcp | Verified | 200 | |
| http (plaintext) | http://atalaya.city/mcp | HTTPS enforced | 301 | https://atalaya.city/mcp |
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 →
consultar_riesgo Consultar riesgos activos en una zona ~309
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 verificados de vecinos (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.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | – | Latitud (alternativa a lugar). |
| lon | number | – | Longitud (alternativa a lugar). |
| lugar | string | – | Barrio, dirección o ciudad en Colombia. Incluye la ciudad si no es Bogotá. |
| radio_km | number | – | Radio de búsqueda en km (0,5 a 15; por defecto 3). |
No output schema declared.
No examples provided.
explicar_cobertura Qué hacer y qué seguros responden ante un riesgo ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| tipo | string | yes | Tipo de riesgo (acepta sinónimos: terremoto, derrumbe, aguacero, bache, choque, robo…). |
No output schema declared.
No examples provided.
perfil_cuadro Perfil de riesgo de un lugar (cuadro de 150 m) ~386
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.
| Name | Type | Req | Description |
|---|---|---|---|
| celda | string | – | Código del cuadro, columna:fila (p. ej. el que devuelve consultar_riesgo). |
| lat | number | – | Latitud (alternativa a lugar). |
| lon | number | – | Longitud (alternativa a lugar). |
| lugar | string | – | Dirección, barrio o sitio en Colombia (incluye la ciudad si no es Bogotá). Mejor una dirección que un barrio: el perfil es del cuadro de 150 m donde cae el punto. |
No output schema declared.
No examples provided.
How do I install the city.atalaya/riesgos MCP server?
city.atalaya/riesgos is a hosted endpoint at https://atalaya.city/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 · atalaya.city
claude mcp add --transport http city-atalaya-riesgos 'https://atalaya.city/mcp'
What is the city.atalaya/riesgos MCP server?
city.atalaya/riesgos is an MCP server listed in the public MCP registry as city.atalaya/riesgos. Riesgos en vivo en Colombia: lluvia, inundaciones, incendios, sismos y reportes de vecinos. This page covers its hosted endpoint (https://atalaya.city/mcp).
Is the city.atalaya/riesgos MCP server safe to use?
city.atalaya/riesgos scores 74 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 city.atalaya/riesgos MCP server expose?
city.atalaya/riesgos exposes 3 tools: consultar_riesgo, perfil_cuadro, explicar_cobertura. Their descriptions and schemas cost roughly 831 tokens of context every time the server is loaded.
Does the city.atalaya/riesgos MCP server require authentication?
No. We connected to city.atalaya/riesgos without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the city.atalaya/riesgos MCP server still maintained?
city.atalaya/riesgos is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.