Skip to main content
Glama

@pipeworx/bde-es

Banco de España (Spain) reference rates and financial indicators: the mortgage-market reference rates (IRPH, IRS, public-debt yield), Euribor, the legal and late-payment interest rates, the average rate on new housing loans, and the euro exchange rates (monthly averages), with history.

Part of Pipeworx — an MCP gateway connecting AI agents to 1957+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Euro-area policy rates (deposit facility, main refinancing) are set by the European Central Bank: use the ecb pack for those.

Tools

  • bde_es_series_list() — the series served, each with its key, label, unit and frequency.

  • bde_es_latest({ series? }) — latest published value, the period it refers to and the direction of change. series is one key or a comma list; omit for all.

  • bde_es_series({ series, start_date?, end_date? }) — history of one series, oldest first (default last 24 months; full history back to the series start). A window with nothing in it returns count: 0 with an empty_reason; an unknown series is an error naming it.

Related MCP server: Market Intel MCP

Auth

Keyless.

Data sources

  • Banco de España, statistical series. Each call reads live from the bank; nothing is stored.

Things worth knowing:

  • Every series here is monthly: the period is the first day of the reference month, and the newest value lags by up to a month.

  • Exchange rates are monthly averages of the daily euro reference rates, per euro (for example USD per EUR).

  • series also accepts a raw Banco de España series code; the curated keys are the ones with checked labels and units.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "bde-es": {
      "url": "https://gateway.pipeworx.io/bde-es/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/bde-es/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — ask_pipeworx, discover_tools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

This is deliberate, not multiplexing by accident. The meta-tools are what let a scoped connection answer a question this pack does not cover — via ask_pipeworx, which routes across the whole catalog — without you adding a second MCP server. There is currently no way to mount a pack endpoint without them; if the extra schemas cost you more context than the routing is worth, connect to the full gateway once rather than to several pack endpoints.

Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1957+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

No MCP client? Call it over HTTP

curl -X POST https://gateway.pipeworx.io/v1/tools/bde_es_series_list \
  -H 'Content-Type: application/json' \
  -d '{}'

No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/bde_es_series_list. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Run it from npm

@pipeworx/mcp-bde-es is a local stdio bridge to the Pipeworx gateway: your MCP client starts it with npx, and it forwards every call to the same https://gateway.pipeworx.io/bde-es/mcp endpoint shown above. It needs network access; there is no offline mode.

{
  "mcpServers": {
    "bde-es": {
      "command": "npx",
      "args": ["-y", "@pipeworx/mcp-bde-es"]
    }
  }
}

Without a key it calls anonymously, capped at 50 calls a day. A free account raises that to 200 a day: get a key at https://pipeworx.io/signup and add "env": { "PIPEWORX_API_KEY": "<your key>" } to the server entry. The key is sent as a Bearer token, the same way a hosted connection sends it, so calls are metered and billed exactly as they are there.

It lists only this pack's tools by default. Set PIPEWORX_META_TOOLS=1 to also list ask_pipeworx and the other gateway-wide tools.

Behind an HTTPS proxy: Node's built-in fetch does not read HTTPS_PROXY by default. Newer Node releases honour it when NODE_USE_ENV_PROXY=1 is set; check your Node version's documentation.

Using with ask_pipeworx

Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:

ask_pipeworx({ question: "your question about Bde Es data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Provides live and historical foreign-exchange rates from the European Central Bank via Frankfurter API, enabling currency conversion, rate lookup, and trend analysis without API keys.
      5
      5 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides access to Chilean economic indicators (dolar, UF, IPC, etc.) via the mindicador.cl API, enabling queries for current values, historical series, and specific dates.
      MIT