# city.atalaya/riesgos (remote · atalaya.city)

Riesgos en vivo en Colombia: lluvia, inundaciones, incendios, sismos y reportes de vecinos.

- Trust score: 74/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `atalaya.city`: 74/100 (this document), [markdown](https://verifymcp.io/servers/city-atalaya-riesgos/atalaya.md), [page](https://verifymcp.io/servers/city-atalaya-riesgos/atalaya)

## Channel facts

- Endpoint: `https://atalaya.city/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http city-atalaya-riesgos 'https://atalaya.city/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "city-atalaya-riesgos": {
      "url": "https://atalaya.city/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "city-atalaya-riesgos": {
      "type": "http",
      "url": "https://atalaya.city/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.city-atalaya-riesgos]
url = "https://atalaya.city/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "city-atalaya-riesgos": {
      "type": "remote",
      "url": "https://atalaya.city/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add city-atalaya-riesgos --url 'https://atalaya.city/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  city-atalaya-riesgos:
    url: "https://atalaya.city/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "city-atalaya-riesgos": {
      "Transport": "http",
      "Url": "https://atalaya.city/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add city-atalaya-riesgos -t streamable-http -u 'https://atalaya.city/mcp'
```

### Other

```json
{
  "mcpServers": {
    "city-atalaya-riesgos": {
      "type": "http",
      "url": "https://atalaya.city/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 74, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 334 → 380
- [functional] Server version: 1.0.0 → 1.1.0
- [functional] New tool “perfil_cuadro”

### 2026-11-03 (score 74, +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.

### 2026-11-02 (score 73, 0)

- [security] 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

### 2026-11-01 (score 73, +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.

### 2026-10-30 (score 72, +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.

### 2026-10-29 (score 71, 0)

- [security] 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

### 2026-10-28 (score 71, +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.

### 2026-10-27 (score 70, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (3)

### `consultar_riesgo` (~309 tokens)

Consultar riesgos activos en una zona

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.

Input parameters:

- `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).

### `perfil_cuadro` (~386 tokens)

Perfil de riesgo de un lugar (cuadro de 150 m)

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.

Input parameters:

- `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.

### `explicar_cobertura` (~136 tokens)

Qué hacer y qué seguros responden ante un riesgo

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.

Input parameters:

- `tipo` (string, required): Tipo de riesgo (acepta sinónimos: terremoto, derrumbe, aguacero, bache, choque, robo…).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/city-atalaya-riesgos/atalaya#diagnostics

## Score history

- 2026-11-05: 74
- 2026-11-04: 74
- 2026-11-03: 74
- 2026-11-02: 73
- 2026-11-01: 73
- 2026-10-31: 72
- 2026-10-30: 72
- 2026-10-29: 71
- 2026-10-28: 71
- 2026-10-27: 70
- 2026-10-26: 70

## Common questions

### 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://atalaya.city/mcp
- Changelog RSS feed: https://verifymcp.io/servers/city-atalaya-riesgos/atalaya.xml
- Changelog JSON feed: https://verifymcp.io/servers/city-atalaya-riesgos/atalaya.json
- HTML version of this page: https://verifymcp.io/servers/city-atalaya-riesgos/atalaya