Atalaya · un proyecto de La Póliza.io MCP server

Which MCP servers are Atalaya · un proyecto de La Póliza.io's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-29

← Back to Atalaya · un proyecto de La Póliza.io

Whose server it is

Registry namecity.atalaya/riesgosverified in the MCP registry

The registry name sits under atalaya.city. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-29

Stateanswerschecked 2026-10-29
Tools2
Server calls itselflapoliza-riesgo
Server version1.0.0
Protocol version2025-06-18

On 2026-10-29 the server answered initialize and tools/list without a sign-in. First answer in 313 ms.

Should an agent connect itNot proven either way yet

Whether its tools do the product's job has not been judged yet.
Checked on 5 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 5, the first on 2026-10-29

INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
Answeredmeasuring5 of the 7 daily checks it takes to print a share
Median first answer284 ms
Space in an agent's context≈ 487 tokensthe definitions of all its tools (2), which an agent carries on every turn
Tool definitionsA · 100 of 100
Typed results0 of 2 toolsdeclared outputSchema: results come typed, read once

Every tool passes all six checks.

What an agent can do with it

not sure · view live risk zones on a map
not sure · see where road, security and weather risks concentrate
cannot · read and file citizen reports about local risks

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers2 tools · read 2026-10-29

consultar_riesgo
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…
explicar_cobertura
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…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Add it

Claude Code, in a terminal

claude mcp add --transport http atalaya https://atalaya.city/mcp

Add to Cursor Add to VS Code

claude.ai, ChatGPT and other clients: add https://atalaya.city/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.