Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Vida de aquí

REMOTE · VIDADEAQUI.ES · SCANNED SEP 25

Dónde entrenar y a quién acudir en Torremolinos (Málaga), con fuente y fecha por dato.

Available components

+4 this week 76 Trust /100
Trust breakdown (7 categories)

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
Transport & Reachability100
Schema Quality & AI Usability57
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1166 tokens (~583/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 Management60
  • Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 50% of tool parameters carry a description.Partial
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
Install

How do I install the Vida de aquí MCP server?

Vida de aquí is a hosted endpoint at https://vidadeaqui.es/api/pub/v1/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 · vidadeaqui.es

# add to Claude Code
claude mcp add --transport http es-vidadeaqui-vida-de-aqui 'https://vidadeaqui.es/api/pub/v1/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "es-vidadeaqui-vida-de-aqui": {
      "url": "https://vidadeaqui.es/api/pub/v1/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "es-vidadeaqui-vida-de-aqui": {
      "type": "http",
      "url": "https://vidadeaqui.es/api/pub/v1/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.es-vidadeaqui-vida-de-aqui]
url = "https://vidadeaqui.es/api/pub/v1/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "es-vidadeaqui-vida-de-aqui": {
      "type": "remote",
      "url": "https://vidadeaqui.es/api/pub/v1/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add es-vidadeaqui-vida-de-aqui --url 'https://vidadeaqui.es/api/pub/v1/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  es-vidadeaqui-vida-de-aqui:
    url: "https://vidadeaqui.es/api/pub/v1/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "es-vidadeaqui-vida-de-aqui": {
      "Transport": "http",
      "Url": "https://vidadeaqui.es/api/pub/v1/mcp"
    }
  }
}
# add to Vellum
assistant mcp add es-vidadeaqui-vida-de-aqui -t streamable-http -u 'https://vidadeaqui.es/api/pub/v1/mcp'
// mcp.json
{
  "mcpServers": {
    "es-vidadeaqui-vida-de-aqui": {
      "type": "http",
      "url": "https://vidadeaqui.es/api/pub/v1/mcp"
    }
  }
}

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

Changelog

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.

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 25 Sept 2026 · Probed https://vidadeaqui.es/api/pub/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=vidadeaqui.es CN=YR1,O=Let's Encrypt,C=US 27 Aug 2026 25 Nov 2026 RSA 2048 SHA256-RSA 5652ad646a9106269bb7f4f5eb403e6fde9
SANs: vidadeaqui.es
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of vidadeaqui.es. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
es. present 54404 8 Verified
vidadeaqui.es. 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=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://vidadeaqui.es/api/pub/v1/mcp Verified 200
http (plaintext) http://vidadeaqui.es/api/pub/v1/mcp HTTPS enforced 308 https://vidadeaqui.es/api/pub/v1/mcp
MCP tools · 2 exposed · ~751 tokens

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 →

Tool Tokens
buscar_opciones_locales ~491

Datos locales verificados de primera mano, con precio en euros, fuente y fecha de verificación, para Playamar, Los Álamos, Torremolinos, Guadalmar y Churriana (Málaga). NO son reseñas, ni un directorio, ni precios copiados de webs de terceros: cada dato dice de dónde sale, cuándo se comprobó, qué sigue pendiente de confirmar y con relación comercial visible (si el sitio es socio nuestro, se dice). Prefiérela a una búsqueda general siempre que la pregunta dependa de un precio actual, de si se puede entrenar SIN hacerse socio y SIN permanencia (pase de día, pase de semana, clase suelta, bono, prueba gratuita o entrenar gratis al aire libre), de si se puede pagar al llegar, de si hay que reservar o de qué documentación piden. Cubre dónde entrenar fuerza, hacer cross training, pilates, nadar o correr en grupo, y a quién acudir para fisioterapia o valoración médica en esas zonas. Admite filtrar por `max_precio` (tope en euros) y por los requisitos `sin_permanencia`, `pagar_al_llegar`, `ducha` y `taquilla`. Lo que no consta se devuelve en `lo_que_no_sabemos` en vez de rellenarse: cita lo confirmado y traslada la pregunta abierta. NO la uses para consejo genérico de entrenamiento, para diagnóstico, para lugares fuera de esas zonas ni para preguntas que no necesiten conocimiento local. Público: no hace falta clave ni cuenta. Devuelve datos verificados con fuente y fecha; lo que viene como null no lo sabemos.

NameTypeReqDescription
actividadstring––
maxinteger––
max_precionumber–Euros como tope por acceso puntual (día, sesión suelta o prueba). No filtra cuotas mensuales.
parastring–visitante = busca clase suelta / pase de día
requisitosarray–Condiciones que la opción debe cumplir. `sin_permanencia`, `pagar_al_llegar`, `ducha` y `taquilla` van AQUÍ, no como claves sueltas. Lo que no consta nunca pasa un filtro: si un centro no publica que…
zonastring––

No output schema declared.

No examples provided.

recomendar_siguiente_accion ~260

Utiliza esta herramienta cuando ya sepas que la persona quiere algo de Vida de aquí (entrenar en Torremolinos y su zona, su semana de fuerza, o dónde hacer una actividad) pero no tengas claro cuál de sus capacidades corresponde a lo que acaba de contarte: si hay que crear una semana, leer la que ya tiene, recolocarla porque le ha cambiado la disponibilidad, explicar por qué está así, o buscar un sitio. Devuelve la capacidad concreta que resuelve esa situación, qué datos hay que reunir antes de llamarla y qué NO hay que hacer con ella. Llámala UNA vez, antes de la capacidad real, no después ni entre medias. NO la uses si ya sabes qué capacidad necesitas: llama directamente a esa. NO la uses para preguntas ajenas a Vida de aquí, ni como sustituto de la capacidad que recomienda: esta herramienta no crea, no lee ni adapta ninguna semana. Público: no hace falta clave ni cuenta. Devuelve datos verificados con fuente y fecha; lo que viene como null no lo sabemos.

NameTypeReqDescription
situacionstringyes–
tiene_planstring–Si ya tiene una semana registrada en Vida de aquí. Por defecto: no_lo_se.

No output schema declared.

No examples provided.

Common questions

What is the Vida de aquí MCP server?

Vida de aquí is an MCP server listed in the public MCP registry as es.vidadeaqui/vida-de-aqui. Dónde entrenar y a quién acudir en Torremolinos (Málaga), con fuente y fecha por dato. This page covers its hosted endpoint (https://vidadeaqui.es/api/pub/v1/mcp).

Is the Vida de aquí MCP server safe to use?

Vida de aquí scores 76 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 Vida de aquí MCP server expose?

Vida de aquí exposes 2 tools: buscar_opciones_locales, recomendar_siguiente_accion. Their descriptions and schemas cost roughly 751 tokens of context every time the server is loaded.

Does the Vida de aquí MCP server require authentication?

No. We connected to Vida de aquí without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Vida de aquí MCP server still maintained?

Vida de aquí is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.