Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Bis

NPM · @PIPEWORX/MCP-BIS · 2 COMPONENTS

BIS MCP — Bank for International Settlements statistics (no auth)

82 Trust /100

Last scanned (21 hours ago)

Scores higher than 72% of npm servers

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-bis). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 4 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 722 tokens (~180/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 1 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 31 Oct 26 +16
    • Malware scan: unverified → pass ▲ security
  • 30 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
    • Security disclosure: unverified → fail ▼ functional
    • Stability: unverified → 0.03 ▲ functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 29 Oct 26 80

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Analysed npm/@pipeworx/mcp-bis@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-bis
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-bis/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3601471839
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:fec32b89036ea39e3edd5134e03b3ebf4532982901ce5e72a965f0ecd200dd0b3709e86c879ec6dd07eae789fa86023fd61728b3dd94a9864ac94a258

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~671 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
bis_credit_gap ~240

Credit-to-GDP gap for one country from the BIS early-warning indicators: the credit-to-GDP ratio, its long-run one-sided HP-filter trend, and the gap between them in percentage points of GDP. The gap is the Basel III common reference point for setting the countercyclical capital buffer and a standard banking-crisis early-warning signal, so a large positive gap means private non-financial credit is running above its long-run trend and a negative gap means it is running below. Quarterly, 44 economies plus the euro area aggregate, history back to the 1960s for the longest series. Accepts a country name or an ISO alpha-2 code.

NameTypeReqDescription
countrystringyesCountry name or ISO alpha-2 code, e.g. "United States" or "US". "Euro area" returns the XM aggregate.
end_periodstring–Inclusive end, e.g. "2025-Q4"
limitnumber–Max quarters returned, most recent first (default 20)
start_periodstring–Inclusive start, e.g. "2020" or "2020-Q1"

No output schema declared.

No examples provided.

fetch_dataset ~258

Fetch tidy rows from a BIS dataflow. flow_ref is "BIS,<id>,<version>" and the VERSION IS NOT ALWAYS 1.0 — "BIS,WS_CBPOL,1.0" (central bank policy rates), "BIS,WS_XRU,1.0" (US-dollar exchange rates), but "BIS,WS_TC,2.0" (total credit). BIS re-versions flows in place, so a guessed version returns no data rather than an error; take the exact ref from list_curated_flows or search_dataflows instead of assuming one. The key string is a dot-separated dimension filter (e.g., "D.US" — frequency.country). ALWAYS pass start_period / end_period ("2020", "2020-Q1", "2020-01"): the big banking and debt flows are multi-megabyte and an unbounded request can time out.

NameTypeReqDescription
end_periodstring–Inclusive end
flow_refstringyesSDMX dataflow reference
keystring–Dot-separated dimension key (empty for all)
limitnumber–Cap rows (default 5000)
start_periodstring–Inclusive start

No output schema declared.

No examples provided.

list_curated_flows ~76

List BIS dataflow refs we have pre-vetted, grouped by topic (rates, fx, banking, debt, credit, property, derivatives, finance). Use the flow_ref with fetch_dataset. For everything else use search_dataflows or browse https://stats.bis.org.

NameTypeReqDescription
topicstring–Optional topic filter

No output schema declared.

No examples provided.

search_dataflows ~97

Search the BIS SDMX dataflow registry by keyword against dataflow name and ID. Returns matched flow_refs (e.g., 'BIS,WS_CBPOL_D,1.0') ready to pass to fetch_dataset, capped at limit (default 25, max 100).

NameTypeReqDescription
limitnumber–Max results (default 25, max 100)
querystringyesKeyword (matches dataflow name)

No output schema declared.

No examples provided.

Install

How do I install the Bis MCP server?

Bis runs locally as an npm package, launched with npx -y @pipeworx/mcp-bis. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-bis

# add to Claude Code
claude mcp add pipeworx-io-bis -- npx -y @pipeworx/mcp-bis
Common questions

What is the Bis MCP server?

Bis is an MCP server listed in the public MCP registry as io.github.pipeworx-io/bis. BIS MCP, Bank for International Settlements statistics (no auth). This page covers its npm package (@pipeworx/mcp-bis).

Is the Bis MCP server safe to use?

Bis scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Bis MCP server expose?

Bis exposes 4 tools: list_curated_flows, search_dataflows, fetch_dataset, bis_credit_gap. Their descriptions and schemas cost roughly 671 tokens of context every time the server is loaded.

Is the Bis MCP server still maintained?

Bis is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Bis MCP server under?

Bis declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.