{
  "markdown": "# @pipeworx/bis\n\nBIS (Bank for International Settlements) MCP — central-bank and global-financial\nstatistics over the BIS SDMX v2 API. No auth.\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Tools\n\n- `bis_credit_gap(country, start_period?, end_period?, limit?)` — credit-to-GDP\n  ratio, its long-run HP-filter trend, and the gap between them, per quarter,\n  for one country. The gap is the Basel III reference indicator for the\n  countercyclical capital buffer. Accepts a country name or ISO alpha-2 code;\n  44 economies plus the euro area aggregate (`XM`).\n- `list_curated_flows(topic?)` — pre-vetted dataflow refs by topic (rates, fx,\n  banking, debt, credit, property, derivatives, prices).\n- `search_dataflows(query, limit?)` — keyword search over the full BIS dataflow\n  registry; returns `flow_ref`s ready for `fetch_dataset`.\n- `fetch_dataset(flow_ref, key?, start_period?, end_period?, limit?)` — tidy\n  rows from any BIS dataflow.\n\n## Auth\n\nNone. BIS publishes these statistics openly and applies no key or quota.\n\n## Notes on the upstream API\n\n- **`flow_ref` carries a version and the version is not always `1.0`.** BIS\n  re-versions dataflows in place (`WS_TC` is `2.0`), and a stale version returns\n  an empty result rather than an error. Take refs from `list_curated_flows` or\n  `search_dataflows` instead of assuming one.\n- **Keys are positional over the flow's own dimensions**, dot-separated — e.g.\n  `Q.US...` on `WS_CREDIT_GAP`, whose key is\n  `FREQ.BORROWERS_CTY.TC_BORROWERS.TC_LENDERS.CG_DTYPE`. Leave a position empty\n  to not filter on it. When a key matches nothing, `fetch_dataset` names the\n  flow's actual dimensions back to you.\n- **Rows carry both the code and its meaning.** Every coded column arrives with\n  a `<COLUMN>_label` companion (`CG_DTYPE: \"C\"` /\n  `CG_DTYPE_label: \"Credit-to-GDP gaps (actual-trend)\"`), because BIS's coded\n  values are opaque on their own.\n- The banking and debt-securities flows are multi-megabyte unbounded — pass\n  `start_period` / `end_period`.\n\n## Data sources\n\n- API: https://stats.bis.org/api/v2/\n- API docs: https://stats.bis.org/api-doc/v2/\n- Browse: https://stats.bis.org\n- Credit-to-GDP gaps: https://www.bis.org/statistics/c_gaps.htm\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"bis\": {\n      \"url\": \"https://gateway.pipeworx.io/bis/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/bis/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1476+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Bis data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n",
  "bytes": 4282,
  "sha": "b60d61ec80d0f6155568b27066d77cd5916a921cd10d217233a0803cb4a23234",
  "repo_slug": "pipeworx-io/mcp-bis",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_bis_a2ab6bb0/readme"
}