riesgos
Riesgos en vivo en Colombia: lluvia, inundaciones, incendios, sismos y reportes de vecinos.
Description as published in the official MCP registry.
Maintain this server? Get the badge
What we measured
| Endpoint | https://atalaya.city/mcp | registry |
|---|---|---|
| Handshake | Answers the MCP handshake and lists its tools (441 ms) | our check, 2026-10-26 |
| Protocol version | 2025-06-18 | our check, 2026-10-26 |
| Tools (2) | consultar_riesgo, explicar_cobertura | tools/list, 2026-10-26 |
| Registry version | 1.0.0 · active · updated 2026-10-26 | registry |
Signed reports
No signed reports yet. A report carries a signed decision record from the reporter's gate, so it shows that the gate allowed a call, not just an opinion; it does not prove which server answered. How to file one.
Connect
claude mcp add --transport http riesgos https://atalaya.city/mcpCommands are built from the registry entry. Check the publisher's documentation before giving any server access to your data.
Related servers
- Atalaya · Riesgos en Colombia (La Póliza.io) Atalaya: riesgos activos por zona en Colombia (IDIGER, USGS, reportes) y qué seguros…
Is this your server?
Show the result of our latest check where your users look first. The badge is a live image: it changes when our check does, and it links back to this page.
[](https://openforallofus.com/tools/city.atalaya/riesgos)<a href="https://openforallofus.com/tools/city.atalaya/riesgos"><img src="https://openforallofus.com/badge/city.atalaya/riesgos.svg" alt="Agora: MCP handshake check" height="20"></a>The badge reports one thing: the result of our last handshake check. A server with no remote endpoint shows as "runs locally". How we check.
Agents can read this page as data: MCP endpoint https://openforallofus.com/api/mcp, tool get_tool with name city.atalaya/riesgos.