What a Plan! — MCP Server
REMOTE · API.WHATAPLAN.NET · SCANNED SEP 24
Descubre eventos en España: filtra por texto, categoría, ubicación, precio y fecha. 38 categorías.
Available components
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 488 tokens (~162/item across 3 items; 3 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 3 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
How do I install the What a Plan! — MCP Server server?
What a Plan! — MCP Server is a hosted endpoint at https://api.whataplan.net/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 · api.whataplan.net
claude mcp add --transport http net-whataplan-api-whataplan-mcp 'https://api.whataplan.net/mcp'
{
"mcpServers": {
"net-whataplan-api-whataplan-mcp": {
"url": "https://api.whataplan.net/mcp"
}
}
} {
"servers": {
"net-whataplan-api-whataplan-mcp": {
"type": "http",
"url": "https://api.whataplan.net/mcp"
}
}
} [mcp_servers.net-whataplan-api-whataplan-mcp] url = "https://api.whataplan.net/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"net-whataplan-api-whataplan-mcp": {
"type": "remote",
"url": "https://api.whataplan.net/mcp",
"enabled": true
}
}
} openclaw mcp add net-whataplan-api-whataplan-mcp --url 'https://api.whataplan.net/mcp' --transport streamable-http
mcp_servers:
net-whataplan-api-whataplan-mcp:
url: "https://api.whataplan.net/mcp" {
"McpServers": {
"net-whataplan-api-whataplan-mcp": {
"Transport": "http",
"Url": "https://api.whataplan.net/mcp"
}
}
} assistant mcp add net-whataplan-api-whataplan-mcp -t streamable-http -u 'https://api.whataplan.net/mcp'
{
"mcpServers": {
"net-whataplan-api-whataplan-mcp": {
"type": "http",
"url": "https://api.whataplan.net/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 26 79
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
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 Sept 2026 · Probed https://api.whataplan.net/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.whataplan.net | CN=YE1,O=Let's Encrypt,C=US | 1 Aug 2026 | 30 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 597e3dc860419dd8415acdbf212fd6c02e3 |
| SANs: api.whataplan.net | ||||||
| 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 api.whataplan.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| whataplan.net. | 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 | 201 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self';base-uri 'self';font-src 'self' https: data:;form-action 'self';frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.whataplan.net/mcp | Verified | 201 | |
| http (plaintext) | http://api.whataplan.net/mcp | HTTPS enforced | 301 | https://api.whataplan.net/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 →
get_event ~62
Obtiene los detalles completos de un evento específico por su slug. Usa esta herramienta después de search_events para obtener información detallada.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Slug único del evento (ej: "concierto-rock-leon-2026"). Obligatorio. |
No output schema declared.
No examples provided.
list_categories ~38
Lista todas las categorías de planes disponibles en What a Plan! (ej: Música en Directo, Teatro, Gastronomía, Deportes, etc.)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_events ~388
Busca planes y eventos en What a Plan! usando múltiples filtros. Usa esta herramienta cuando alguien pregunte por planes, eventos, actividades, o qué hacer. Para filtrar por ubicación, proporciona coordenadas lat/lng y radio en metros (puedes determinar coordenadas desde nombres de ciudades). Ejemplos de consultas: "planes en León para niños", "conciertos gratis este fin de semana", "qué hacer mañana en Valladolid"
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Nombre o slug de categoría (ej: "Música en Directo", "musica-en-directo") |
| city | string | – | Nombre de ciudad como fallback si no puedes determinar coordenadas (menos preciso que lat/lng) |
| end_date | string | – | Fecha máxima en formato YYYY-MM-DD (ej: "2026-06-07" para fin de semana) |
| lat | number | – | Latitud del centro de búsqueda (ej: 42.5987 para León). Proporciónala SEMPRE que sepas la ubicación. |
| limit | number | – | Número máximo de resultados (default: 20, máx: 50) |
| lng | number | – | Longitud del centro de búsqueda (ej: -5.5669 para León). Proporciónala junto con lat. |
| max_price | number | – | Precio máximo (ej: 20) |
| min_price | number | – | Precio mínimo (ej: 0 para gratis) |
| radius | number | – | Radio de búsqueda en metros (default: 10000 = 10km). Usa 20000 para área metropolitana. |
| search | string | – | Palabras clave en título o descripción (ej: "niños", "rock", "gratis", "gastronomía") |
| start_date | string | – | Fecha mínima en formato YYYY-MM-DD (ej: "2026-06-05") |
No output schema declared.
No examples provided.
What is the What a Plan! — MCP Server server?
What a Plan! — MCP Server is listed in the public MCP registry as net.whataplan.api/whataplan-mcp. Descubre eventos en España: filtra por texto, categoría, ubicación, precio y fecha. 38 categorías. This page covers its hosted endpoint (https://api.whataplan.net/mcp).
Is the What a Plan! — MCP Server server safe to use?
What a Plan! — MCP Server scores 79 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 What a Plan! — MCP Server server expose?
What a Plan! — MCP Server exposes 3 tools: search_events, list_categories, get_event. Their descriptions and schemas cost roughly 488 tokens of context every time the server is loaded.
Does the What a Plan! — MCP Server server require authentication?
No. We connected to What a Plan! — MCP Server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the What a Plan! — MCP Server server still maintained?
What a Plan! — MCP Server is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.