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.

Bundesbank De

NPM · @PIPEWORX/MCP-BUNDESBANK-DE · 2 COMPONENTS

Deutsche Bundesbank (Germany's central bank) statistics MCP.

+3 this week 82 Trust /100

Last scanned (12 hours ago)

Scores higher than 72% of npm servers

Category Data and Analytics

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-bundesbank-de). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 5 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 662 tokens (~220/item across 3 items; 3 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 Management23
  • Stability observed for 7 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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.

  • 4 Nov 26 +1

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

  • 2 Nov 26 +1

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

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

    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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-bundesbank-de@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-bundesbank-de
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-bundesbank-de/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3606613155
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:08ee0355db67ddf34ac606da2409db7ac807de8f5b281122d16f36ff33a51cb2345df02933f03d66dde69c76c7324cf7730967d70340181113468358a

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 · 3 exposed · ~607 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
dataflow_structure ~175

Get the data structure definition (DSD) for a dataflow: its dimensions and the valid codes for each, which you need to build a series key for get_series. Returns SDMX 2.1 structure XML. The DSD id differs from the dataflow id (e.g. dataflow BBEX3 uses DSD "BBK_ERX"). Pass the dataflow id (flowRef) and this tool resolves the DSD for you; the dimensions appear in <DimensionList> in key order. Set withCodes=true (default) to inline the codelists (references=children).

NameTypeReqDescription
flowRefstringyesDataflow id whose structure you want, e.g. "BBEX3".
withCodesboolean–Include the referenced codelists (valid dimension values). Default true.

No output schema declared.

No examples provided.

get_series ~285

Pull observations for a Bundesbank series as SDMX-JSON. flowRef is the dataflow id (e.g. "BBEX3"); key is a dot-separated SDMX dimension filter in key order (e.g. "D.USD.EUR.BB.AC.000" = daily USD/EUR reference rate). Use dataflow_structure to discover the dimensions/codes for a flow. Leave a dimension empty to wildcard it (e.g. "D..EUR.BB.AC.000"). Filter by lastNObservations (most recent N) or a startPeriod/endPeriod date range (YYYY, YYYY-MM, or YYYY-MM-DD).

NameTypeReqDescription
detailstring–SDMX detail level: "full" (default), "dataonly", "serieskeysonly", or "nodata".
endPeriodstring–Inclusive end period (YYYY, YYYY-MM, or YYYY-MM-DD).
flowRefstringyesDataflow id, e.g. "BBEX3".
keystringyesDot-separated SDMX dimension filter, e.g. "D.USD.EUR.BB.AC.000". Empty segments wildcard a dimension.
lastNObservationsnumber–Return only the most recent N observations.
startPeriodstring–Inclusive start period (YYYY, YYYY-MM, or YYYY-MM-DD).

No output schema declared.

No examples provided.

list_dataflows ~147

List the available Bundesbank statistics dataflows (each is a series collection you can query with get_series). Returns SDMX 2.1 structure XML listing every dataflow id + name under agency BBK. Well-known flows: BBEX3 (exchange rates), BBK01 (legacy single time series), BBSIS (interest rates), BBBK1/BBBK2 (banking statistics), BBDB1 (balance of payments). Pass a flowRef to fetch just that one dataflow (includes its DataStructure reference).

NameTypeReqDescription
flowRefstring–Optional. A single dataflow id (e.g. "BBEX3") to fetch instead of the full list.

No output schema declared.

No examples provided.

Install

How do I install the Bundesbank De MCP server?

Bundesbank De runs locally as an npm package, launched with npx -y @pipeworx/mcp-bundesbank-de. 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-bundesbank-de

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

What is the Bundesbank De MCP server?

Bundesbank De is an MCP server listed in the public MCP registry as io.github.pipeworx-io/bundesbank-de. Deutsche Bundesbank (Germany's central bank) statistics MCP. This page covers its npm package (@pipeworx/mcp-bundesbank-de).

Is the Bundesbank De MCP server safe to use?

Bundesbank De scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 Bundesbank De MCP server expose?

Bundesbank De exposes 3 tools: list_dataflows, dataflow_structure, get_series. Their descriptions and schemas cost roughly 607 tokens of context every time the server is loaded.

Is the Bundesbank De MCP server still maintained?

Bundesbank De is still listed as active in the MCP registry. We last reached this channel on 5 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 Bundesbank De MCP server under?

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