
Connects to the Croatian National Bank's public exchange rate API to fetch currency conversion data for the kuna and other currencies. No API key required. Part of the Pipeworx gateway ecosystem, which means you can either use it standalone or access it through their unified gateway alongside 250+ other data sources. The implementation includes an ask_pipeworx natural language interface that translates questions into the appropriate tool calls automatically. Useful if you're building financial apps with Croatian market exposure, need HNB rates for accounting systems, or want to avoid managing yet another API client when Pipeworx already handles the connection over streamable HTTP.
Croatian National Bank (Hrvatska narodna banka, HNB) exchange-rate MCP. Keyless.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
| Tool | Description |
|---|---|
hnb_exchange_rates | HNB (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_rate | HNB 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. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"hnb-hr": {
"url": "https://gateway.pipeworx.io/hnb-hr/mcp"
}
}
}
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 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
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.
MIT
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":"..."}.