_ registry / mcp streamable-http · checked 59m ago

embals-es

https://embals.es

Registry code: b57bef9efc512a5e

api record

Datos del agua embalsada en España (embals.es): nivel actual de cada embalse o pantano, totales por comunidad, provincia y cuenca, y la serie histórica semanal oficial del MITECO desde 1988. Usa estado_embalse para un embalse concreto, buscar_embalses para listas y rankings, resumen_agua_embalsada para totales y historico_embalse para comparar con otros años. Los datos son semanales (boletín hidrológico del MITECO): indica siempre la fecha del dato. Licencia CC BY 4.0: cita embals.es y enlaza la URL que acompaña a cada resultado.

endpoint
https://embals.es/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 embals-es live?
Yes — it answered the hub's last check (checked 59m ago). It answered 100% of checks over the last 30 days.
Is embals-es free to use?
Yes — the hub reached it with no key and no payment.
What tools does embals-es have?
4 tools: historico_embalse, estado_embalse, buscar_embalses, resumen_agua_embalsada.
Is embals-es 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
203ms

last good check

priced tools
0

of 4 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

_ what it can do 4 tools
2 open 2 never probed 2 of 4 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.

  • buscar_embalses open 59m ago

    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'.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "orden": {
          "enum": [
            "capacidad",
            "mas_llenos",
            "mas_vacios"
          ],
          "type": "string",
          "default": "capacidad"
        },
        "texto": {
          "type": "string",
          "description": "Parte del nombre del embalse."
        },
        "cuenca": {
          "type": "string",
          "description": "Cuenca hidrográfica: Ebro, Duero, Tajo, Guadiana, Guadalquivir, Júcar, Segura, Miño-Sil, Cantábrico…"
        },
        "limite": {
          "type": "integer",
          "default": 10,
          "maximum": 50,
          "minimum": 1
        },
        "comunidad": {
          "type": "string",
          "description": "Comunidad autónoma, p. ej. 'Cataluña', 'Comunidad Valenciana'."
        },
        "provincia": {
          "type": "string"
        }
      },
      "additionalProperties": false
    }
    arguments 36 lines
  • resumen_agua_embalsada open 59m ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "ambito": {
          "enum": [
            "espana",
            "comunidad",
            "provincia",
            "cuenca"
          ],
          "type": "string",
          "default": "espana"
        },
        "nombre": {
          "type": "string",
          "description": "Nombre de la comunidad, provincia o cuenca (no hace falta para España)."
        }
      },
      "additionalProperties": false
    }
    arguments 20 lines
  • historico_embalse unknown never probed

    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?'.

    mcp-tool

    {
      "type": "object",
      "required": [
        "nombre"
      ],
      "properties": {
        "anos": {
          "type": "integer",
          "default": 10,
          "maximum": 38,
          "minimum": 1,
          "description": "Años hacia atrás."
        },
        "nombre": {
          "type": "string",
          "description": "Nombre del embalse."
        },
        "provincia": {
          "type": "string",
          "description": "Provincia, solo para desambiguar."
        }
      },
      "additionalProperties": false
    }
    arguments 24 lines
  • estado_embalse unknown 59m ago

    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').

    mcp-tool

    {
      "type": "object",
      "required": [
        "nombre"
      ],
      "properties": {
        "nombre": {
          "type": "string",
          "description": "Nombre del embalse, p. ej. 'Sau', 'Yesa', 'Entrepeñas'."
        },
        "provincia": {
          "type": "string",
          "description": "Provincia, solo para desambiguar nombres repetidos."
        }
      },
      "additionalProperties": false
    }
    arguments 17 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 b57bef9efc512a5e.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b57bef9efc512a5e/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/b57bef9efc512a5e/badge.svg)](https://brick.blue/agent/b57bef9efc512a5e?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
80%

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.