Bank Of Canada
NPM · @PIPEWORX/MCP-BANK-OF-CANADA · 2 COMPONENTS
Bank of Canada Valet API MCP. Keyless. Dates are YYYY-MM-DD.
Available components
Last scanned (2 hours ago)
Scores higher than 91% of npm servers
Category Finance and Payments
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-bank-of-canada). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 22 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 571 tokens (~114/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
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 22 Nov 2026 · Analysed npm/@pipeworx/mcp-bank-of-canada@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-bank-of-canada |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-bank-of-canada/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3601377671 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:d492203b8d5c677dbe590308d2345cfd37fefa77153db67ade39547db1e356c77835e0bf70457797ac054188fb79eff82b649178e4e64b873df7d9621 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get_group_observations ~123
Observations for every series in a named group in one call. Useful groups: FX_RATES_DAILY (daily exchange rates for all currencies vs CAD). Use recent=N or a start_date/end_date window.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | – | Window end, YYYY-MM-DD (optional). |
| group | string | yes | Group name, e.g. "FX_RATES_DAILY". |
| recent | integer | – | Return the N most recent observations. Ignored if start_date is given. |
| start_date | string | – | Window start, YYYY-MM-DD. |
No output schema declared.
No examples provided.
get_observations ~184
Time-series observations for one or more Bank of Canada series. Pass comma-separated series names. Well-known: FXUSDCAD (USD/CAD daily avg rate), FXEURCAD (EUR/CAD), V39079 (target for the overnight rate / policy rate), V41690973 (Total CPI). Choose either recent=N latest points OR a start_date/end_date window.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | – | Window end, YYYY-MM-DD (optional, defaults to latest). |
| recent | integer | – | Return the N most recent observations. Ignored if start_date is given. |
| series | string | yes | Comma-separated series names, e.g. "FXUSDCAD" or "FXUSDCAD,FXEURCAD". |
| start_date | string | – | Window start, YYYY-MM-DD, e.g. "2026-01-01". |
No output schema declared.
No examples provided.
list_groups ~74
Discover available series groups. Optionally filter by a case-insensitive substring matched against group label/description, e.g. "exchange" or "lending".
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results to return (default 50). |
| query | string | – | Substring to match against label/description (case-insensitive). |
No output schema declared.
No examples provided.
list_series ~83
Discover available series. Optionally filter by a case-insensitive substring matched against series label/description, e.g. "exchange rate" or "CPI". Omit query to list all (large).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results to return (default 50). |
| query | string | – | Substring to match against label/description (case-insensitive). |
No output schema declared.
No examples provided.
series_info ~51
Metadata for a single series: label and description. e.g. "FXUSDCAD" or "V39079".
| Name | Type | Req | Description |
|---|---|---|---|
| series | string | yes | Series name, e.g. "FXUSDCAD". |
No output schema declared.
No examples provided.
How do I install the Bank Of Canada MCP server?
Bank Of Canada runs locally as an npm package, launched with npx -y @pipeworx/mcp-bank-of-canada. 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-bank-of-canada
claude mcp add pipeworx-io-bank-of-canada -- npx -y @pipeworx/mcp-bank-of-canada
What is the Bank Of Canada MCP server?
Bank Of Canada is an MCP server listed in the public MCP registry as io.github.pipeworx-io/bank-of-canada. Bank of Canada Valet API MCP. Keyless. Dates are YYYY-MM-DD. This page covers its npm package (@pipeworx/mcp-bank-of-canada).
Is the Bank Of Canada MCP server safe to use?
Bank Of Canada scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 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 Bank Of Canada MCP server expose?
Bank Of Canada exposes 5 tools: get_observations, get_group_observations, series_info, list_series, list_groups. Their descriptions and schemas cost roughly 515 tokens of context every time the server is loaded.
Is the Bank Of Canada MCP server still maintained?
Bank Of Canada is still listed as active in the MCP registry. We last reached this channel on 22 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 Bank Of Canada MCP server under?
Bank Of Canada declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Bank Of Canada MCP server?
VerifyMCP ran 16 checks on Bank Of Canada, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.