Atalaya · Riesgos en Colombia (La Póliza.io)
REMOTE · LAPOLIZA.IO
Atalaya: riesgos activos por zona en Colombia (IDIGER, USGS, reportes) y qué seguros responden.
Available components
Last scanned (17 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 24 Oct 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 Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 513 tokens (~256/item across 2 items; 2 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 Management13
- Stability observed for 4 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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.
- 22 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.
- 21 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Stability: unverified → 0.03 ▲ functional
- 20 Oct 26 71
First indexed and scored.
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 24 Oct 2026 · Probed https://lapoliza.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lapoliza.io | CN=YE1,O=Let's Encrypt,C=US | 17 Sept 2026 | 16 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5f9a6937bd859269b3b1d48358dc1d1da3b |
| SANs: lapoliza.io, www.lapoliza.io | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 lapoliza.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690, 57355 | 8, 8 | Verified |
| lapoliza.io. | 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://unpkg.com https://cdnjs.cloudflare.com https://lapoliza.io blob:; report-uri /report-csp-violation |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://lapoliza.io/mcp | Verified | 200 | |
| http (plaintext) | http://lapoliza.io/mcp | HTTPS enforced | 301 | https://lapoliza.io/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 ~244
Devuelve los riesgos activos alrededor de un lugar de Colombia: eventos en vivo de fuentes oficiales (lluvia fuerte, crecientes y vendavales de la red IDIGER, solo Bogotá), sismos recientes del USGS (todo el país) y reportes ciudadanos verificados (inundaciones, granizo, huecos, vías bloqueadas, árboles o cables caídos, deslizamientos, incendios). Acepta un lugar en texto ("Suba, Bogotá", "calle 80 con Boyacá", "Chía") o coordenadas. No contiene datos personales. Úsala cuando alguien pregunte si hay riesgo, lluvia, inundación, sismo o problemas en una zona, o antes de orientar sobre un seguro para un lugar concreto.
| 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 ~134
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.
| 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.
How do I install the Atalaya · Riesgos en Colombia (La Póliza.io) MCP server?
Atalaya · Riesgos en Colombia (La Póliza.io) is a hosted endpoint at https://lapoliza.io/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 · lapoliza.io
claude mcp add --transport http io-lapoliza-riesgo 'https://lapoliza.io/mcp'
What is the Atalaya · Riesgos en Colombia (La Póliza.io) MCP server?
Atalaya · Riesgos en Colombia (La Póliza.io) is an MCP server listed in the public MCP registry as io.lapoliza/riesgo. Atalaya: riesgos activos por zona en Colombia (IDIGER, USGS, reportes) y qué seguros responden. This page covers its hosted endpoint (https://lapoliza.io/mcp).
Is the Atalaya · Riesgos en Colombia (La Póliza.io) MCP server safe to use?
Atalaya · Riesgos en Colombia (La Póliza.io) scores 72 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 Atalaya · Riesgos en Colombia (La Póliza.io) MCP server expose?
Atalaya · Riesgos en Colombia (La Póliza.io) exposes 2 tools: consultar_riesgo, explicar_cobertura. Their descriptions and schemas cost roughly 378 tokens of context every time the server is loaded.
Does the Atalaya · Riesgos en Colombia (La Póliza.io) MCP server require authentication?
No. We connected to Atalaya · Riesgos en Colombia (La Póliza.io) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Atalaya · Riesgos en Colombia (La Póliza.io) MCP server still maintained?
Atalaya · Riesgos en Colombia (La Póliza.io) is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.