
Connects Claude to the Bank for International Settlements public API for querying global banking and financial statistics. No authentication required. The server is part of Pipeworx's gateway system, which means you can either hit this BIS endpoint directly or access it through their larger gateway covering 250+ data sources. Includes an ask_pipeworx natural language interface that routes your question to the appropriate tool automatically instead of calling specific endpoints. Useful when you need authoritative central banking data, currency statistics, or international financial indicators without manual API wrangling. Runs over streamable HTTP, so it works with any MCP client that supports remote connections.
BIS (Bank for International Settlements) MCP — central-bank and global-financial statistics over the BIS SDMX v2 API. No auth.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
bis_credit_gap(country, start_period?, end_period?, limit?) — credit-to-GDP
ratio, its long-run HP-filter trend, and the gap between them, per quarter,
for one country. The gap is the Basel III reference indicator for the
countercyclical capital buffer. Accepts a country name or ISO alpha-2 code;
44 economies plus the euro area aggregate (XM).list_curated_flows(topic?) — pre-vetted dataflow refs by topic (rates, fx,
banking, debt, credit, property, derivatives, prices).search_dataflows(query, limit?) — keyword search over the full BIS dataflow
registry; returns flow_refs ready for fetch_dataset.fetch_dataset(flow_ref, key?, start_period?, end_period?, limit?) — tidy
rows from any BIS dataflow.None. BIS publishes these statistics openly and applies no key or quota.
flow_ref carries a version and the version is not always 1.0. BIS
re-versions dataflows in place (WS_TC is 2.0), and a stale version returns
an empty result rather than an error. Take refs from list_curated_flows or
search_dataflows instead of assuming one.Q.US... on WS_CREDIT_GAP, whose key is
FREQ.BORROWERS_CTY.TC_BORROWERS.TC_LENDERS.CG_DTYPE. Leave a position empty
to not filter on it. When a key matches nothing, fetch_dataset names the
flow's actual dimensions back to you.<COLUMN>_label companion (CG_DTYPE: "C" /
CG_DTYPE_label: "Credit-to-GDP gaps (actual-trend)"), because BIS's coded
values are opaque on their own.start_period / end_period.Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"bis": {
"url": "https://gateway.pipeworx.io/bis/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/bis/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 Bis data" })
The gateway picks the right tool and fills the arguments automatically.
MIT