mcpField
H
Hnb Hr

Hnb Hr

Remote
pipeworx.ioFinance0Updated 2d ago

About Hnb Hr

Hnb Hr is an MCP server for Croatia’s central bank exchange rates, for AI agents and clients that need currency data quoted against the euro. It supports all-currency lookups and single-currency queries for current or historical dates and ranges.

Key features

  1. 01Look up all foreign-currency rates for a date
  2. 02Get one currency’s rate against the euro
  3. 03Query current or historical rates
  4. 04Retrieve daily rates for a date range

Use cases

  1. 01Check reference rates for foreign currencies against the euro
  2. 02Review a currency’s historical rate changes

MCP support

It exposes Croatia’s central bank exchange-rate lookup tools to MCP clients. It can connect through the Pipeworx gateway or run locally as a stdio MCP server.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://gateway.pipeworx.io/hnb-hr/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

mcp-hnb-hr

Croatian National Bank (Hrvatska narodna banka, HNB) exchange-rate MCP. Keyless.

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

Tools

ToolDescription
hnb_exchange_ratesHNB (Croatian National Bank) official exchange rates for ALL foreign currencies on a given date. Croatia is in the eurozone, so every rate is quoted AGAINST THE EURO (units of foreign currency per 1 EUR). Returns rows with valuta (3-letter ISO code), srednji_tecaj (middle/reference rate), kupovni_tecaj (buying), prodajni_tecaj (selling), datum_primjene (apply date). Omit date for the latest applicable rates. Rate values are strings with a COMMA decimal separator (e.g. "1,164900").
hnb_currency_rateHNB exchange rate for ONE foreign currency vs EUR (Croatia is in the eurozone). Pass the 3-letter ISO currency code (e.g. "USD", "GBP", "CHF"). Three modes: omit dates for the latest rate; pass date for a single historical date; pass start_date+end_date for a daily time series over that window. srednji_tecaj is the middle/reference rate. Rate values are strings with a COMMA decimal separator (e.g. "1,164900"). Dates are YYYY-MM-DD.

Quick Start

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

{
  "mcpServers": {
    "hnb-hr": {
      "url": "https://gateway.pipeworx.io/hnb-hr/mcp"
    }
  }
}
What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/hnb-hr/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 1881+ 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/hnb_exchange_rates \
  -H 'Content-Type: application/json' \
  -d '{}'

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

Standalone (no gateway account)

This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:

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

Or run it directly to confirm it starts:

npx -y @pipeworx/mcp-hnb-hr

It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call for only this pack's tools — none of the shared meta-tools the gateway connection above adds. Same source, same tools, no ask_pipeworx routing.

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 Hnb Hr data" })

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

More

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.