_ registry / mcp streamable-http · checked 1h ago

lapoliza-riesgo

https://atalaya.city

Registry code: bf4ed4d2caf155a5

api record

Atalaya (https://atalaya.city) es el mapa de zonas de riesgo en vivo de Colombia, un proyecto de La Póliza.io, agencia de seguros colombiana; este conector de solo lectura expone sus datos. Usa consultar_riesgo para saber qué pasa ahora alrededor de un lugar: eventos de fuentes oficiales (lluvia fuerte, crecientes y vendavales de las estaciones del IDIGER en Bogotá y de los pluviómetros del SIATA en el Valle de Aburrá), sismos (USGS), incendios detectados por satélite (NASA FIRMS), reportes verificados de vecinos y el pronóstico de lluvia de las próximas horas (Open-Meteo). Usa…

endpoint
https://atalaya.city/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is lapoliza-riesgo live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is lapoliza-riesgo free to use?
Yes — the hub reached it with no key and no payment.
What tools does lapoliza-riesgo have?
2 tools: consultar_riesgo, explicar_cobertura.
Is lapoliza-riesgo safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
355ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 2 tools
2 never probed 0 of 2 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • consultar_riesgo unknown 1h ago

    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 (Open-Meteo). 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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "lat": {
          "type": "number",
          "description": "Latitud (alternativa a lugar)."
        },
        "lon": {
          "type": "number",
          "description": "Longitud (alternativa a lugar)."
        },
        "lugar": {
          "type": "string",
          "description": "Barrio, dirección o ciudad en Colombia. Incluye la ciudad si no es Bogotá."
        },
        "radio_km": {
          "type": "number",
          "description": "Radio de búsqueda en km (0,5 a 15; por defecto 3)."
        }
      }
    }
    arguments 21 lines
  • explicar_cobertura unknown 1h ago

    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, hurto.

    mcp-tool

    {
      "type": "object",
      "required": [
        "tipo"
      ],
      "properties": {
        "tipo": {
          "type": "string",
          "description": "Tipo de riesgo (acepta sinónimos: terremoto, derrumbe, aguacero, bache, choque, robo…)."
        }
      }
    }
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id bf4ed4d2caf155a5.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/bf4ed4d2caf155a5/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/bf4ed4d2caf155a5/badge.svg)](https://brick.blue/agent/bf4ed4d2caf155a5?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
60%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.