Skip to main content
Glama

@pipeworx/mnb-hu

Magyar Nemzeti Bank (Hungary) rates: the central bank base rate (the policy rate) with every change since 1990, and the bank's official daily exchange rates against the forint, by date or range.

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

Tools

  • mnb_hu_series_list() — currencies the bank publishes (ISO codes), the first and last date available, and what each tool serves.

  • mnb_hu_base_rate({ start_date?, end_date? }) — the base rate in force with the date it took effect, plus changes newest first (default the 10 most recent, or a date window). Percent per annum.

  • mnb_hu_exchange_rates({ currency?, date? | start_date?, end_date? }) — forints per unit of foreign currency (each rate carries its unit; JPY and some others are per 100). currency is one ISO code or a comma list. Latest by default; history by range (366 days for named currencies, 31 for all). Weekends and holidays return count: 0 with empty_reason: no_publication_on_date.

Related MCP server: Polish Business Intelligence MCP

Auth

Keyless.

Data sources

  • Magyar Nemzeti Bank, base rate — the bank's published base-rate decisions and their effective dates.

  • Magyar Nemzeti Bank, official exchange rates. Each call reads live from the bank; nothing is stored.

Things worth knowing:

  • Rates use the decimal comma on the bank's side; the pack returns numbers.

  • An unknown currency code is an error naming the code, not an empty result.

  • The base-rate list carries decision effective dates only; it has no decision-meeting text.

Quick Start

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

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

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/mnb-hu/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 2015+ 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/mnb_hu_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/mnb_hu_series_list. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.

Run it from npm

@pipeworx/mcp-mnb-hu 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/mnb-hu/mcp endpoint shown above. It needs network access; there is no offline mode.

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

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 Mnb Hu 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
      Not graded
      quality
      D
      maintenance
      Enables AI agents to query Norges Bank's open data API for exchange rates, policy rates, government securities, money market data, bank liquidity, and regional network survey data.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides access to Croatian National Bank exchange rates without needing an API key, enabling currency conversion and rate queries through natural language.
      79 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents and MCP clients to convert currency amounts, retrieve current, historical, and timeseries exchange rates, and list supported currencies from European Central Bank reference data.
      5
      MIT