es.embals/embalses
REMOTE · EMBALS.ES
Nivel actual e histórico de los embalses de España (MITECO/SAIH). Datos abiertos CC BY 4.0.
Available components
Last scanned (22 hours ago)
Scores higher than 70% 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 Security74
- 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1125 tokens (~187/item across 6 items; 6 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 Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 75% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 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.
- 20 Oct 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.
- 18 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 949 → 1125 ▼ functional
- Schema quality: good → excellent functional
- New tool “sequia_agricola” functional
- 17 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 710 → 949 ▼ functional
- Schema quality: excellent → good functional
- New tool “caudal_rio” functional
- 15 Oct 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.
- 13 Oct 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.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 13. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
- Stability: unverified → 0.07 ▲ functional
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://embals.es/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=embals.es | CN=WE1,O=Google Trust Services,C=US | 9 Oct 2026 | 7 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 2844cb1ab4d60ad91323d8b7ae831bf1 |
| SANs: embals.es | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of embals.es. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| es. | present | 54404 | 8 | Verified |
| embals.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://embals.es/mcp | Verified | 200 | |
| http (plaintext) | http://embals.es/mcp | HTTPS enforced | 301 | https://embals.es/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 →
buscar_embalses Buscar y ordenar embalses ~192
Lista embalses de España filtrando por nombre, provincia, comunidad autónoma o cuenca hidrográfica, ordenados por capacidad, por los más llenos o por los más vacíos. Útil para '¿qué embalses hay en Huesca?', 'los pantanos más vacíos de Andalucía' o 'embalses de la cuenca del Segura'.
| Name | Type | Req | Description |
|---|---|---|---|
| comunidad | string | – | Comunidad autónoma, p. ej. 'Cataluña', 'Comunidad Valenciana'. |
| cuenca | string | – | Cuenca hidrográfica: Ebro, Duero, Tajo, Guadiana, Guadalquivir, Júcar, Segura, Miño-Sil, Cantábrico… |
| limite | integer | – | – |
| orden | string | – | – |
| provincia | string | – | – |
| texto | string | – | Parte del nombre del embalse. |
No output schema declared.
No examples provided.
caudal_rio Caudal de un río ~208
Caudal medio semanal (m³/s) de los ríos de España en las ~120 estaciones de aforo del boletín hidrológico del MITECO, frente a lo normal para la época (mediana de la misma semana en los años anteriores, desde 2001), con la misma semana de años anteriores y los extremos de la serie. Con `nombre` da una estación ('Ebro en Zaragoza', 'Tajo en Alcántara', 'Torrelavega') o todas las de un río ('Guadalquivir'); sin él, el resumen de España o de una cuenca con los ríos más secos y más crecidos.
| Name | Type | Req | Description |
|---|---|---|---|
| cuenca | string | – | Cuenca hidrográfica, para el resumen o para acotar la búsqueda: Ebro, Duero, Tajo… |
| nombre | string | – | Río, estación o río y lugar: 'Ebro', 'Ebro en Zaragoza', 'Sil en San Esteban'. |
No output schema declared.
No examples provided.
estado_embalse Estado de un embalse ~149
Nivel actual de un embalse (pantano) de España: porcentaje de llenado, agua embalsada y capacidad en hm³, variación semanal y fecha del dato, con enlace a su ficha en embals.es. Acepta el nombre con o sin 'embalse de', 'pantano de' o 'pantà de' y sin tildes (p. ej. 'Sau', 'pantano de Yesa', 'la viñuela').
| Name | Type | Req | Description |
|---|---|---|---|
| nombre | string | yes | Nombre del embalse, p. ej. 'Sau', 'Yesa', 'Entrepeñas'. |
| provincia | string | – | Provincia, solo para desambiguar nombres repetidos. |
No output schema declared.
No examples provided.
historico_embalse Histórico de un embalse ~114
Evolución semanal de un embalse con la serie oficial del MITECO (desde 1988): últimas semanas, el nivel en la misma semana de cada año anterior, y el máximo y el mínimo del periodo. Sirve para '¿está más lleno que el año pasado?' o '¿cuándo estuvo tan bajo?'.
| Name | Type | Req | Description |
|---|---|---|---|
| anos | integer | – | Años hacia atrás. |
| nombre | string | yes | Nombre del embalse. |
| provincia | string | – | Provincia, solo para desambiguar. |
No output schema declared.
No examples provided.
resumen_agua_embalsada Agua embalsada en España, una comunidad, provincia o cuenca ~116
Total de agua embalsada y porcentaje de llenado de la reserva hídrica de España o de una comunidad autónoma, provincia o cuenca hidrográfica, con la variación semanal, los embalses más llenos y más vacíos y, para España, la comparación con el mismo momento del año pasado y la media de 10 años.
| Name | Type | Req | Description |
|---|---|---|---|
| ambito | string | – | – |
| nombre | string | – | Nombre de la comunidad, provincia o cuenca (no hace falta para España). |
No output schema declared.
No examples provided.
sequia_agricola Sequía agrícola (Copernicus) ~153
Qué parte de España, de una comunidad autónoma o de una provincia está en sequía según el Indicador Combinado de Sequía (CDI) del Observatorio Europeo de la Sequía (Copernicus): % del territorio en vigilancia (falta lluvia), aviso (también falta humedad en el suelo), alerta (además la vegetación lo acusa) o recuperación. Un dato cada diez días, con 3 a 5 semanas de retraso. Sin `lugar`, España y las provincias más afectadas.
| Name | Type | Req | Description |
|---|---|---|---|
| lugar | string | – | Provincia o comunidad: 'Jaén', 'Cataluña', 'Comunidad de Madrid'. Vacío o 'España' para el total. |
No output schema declared.
No examples provided.
How do I install the es.embals/embalses MCP server?
es.embals/embalses is a hosted endpoint at https://embals.es/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 · embals.es
claude mcp add --transport http es-embals-embalses 'https://embals.es/mcp'
What is the es.embals/embalses MCP server?
es.embals/embalses is an MCP server listed in the public MCP registry as es.embals/embalses. Nivel actual e histórico de los embalses de España (MITECO/SAIH). Datos abiertos CC BY 4.0. This page covers its hosted endpoint (https://embals.es/mcp).
Is the es.embals/embalses MCP server safe to use?
es.embals/embalses 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 es.embals/embalses MCP server expose?
es.embals/embalses exposes 6 tools: estado_embalse, buscar_embalses, resumen_agua_embalsada, historico_embalse, caudal_rio, sequia_agricola. Their descriptions and schemas cost roughly 932 tokens of context every time the server is loaded.
Does the es.embals/embalses MCP server require authentication?
No. We connected to es.embals/embalses without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the es.embals/embalses MCP server still maintained?
es.embals/embalses 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.