Bank Statement Sheet
NPM · BANK-STATEMENT-SHEET-MCP
Convert PDF bank statements into transactions that arrive with a pass/fail reconciliation verdict.
Available components
Last scanned (13 hours ago)
Scores higher than 42% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 104 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 668 tokens (~222/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 87% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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 3 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 (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
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.
- 19 Nov 26 0
- Stability: 0.97 → pass security
- 18 Nov 26 0
- Stability: pass → 0.97 functional
- 12 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Nov 26 −1
- Stability: pass → 0.87 functional
- 2 Nov 26 0
- Stability: 0.97 → pass security
- 1 Nov 26 0
- Stability: pass → 0.97 functional
- 26 Oct 26 0
- Stability: 0.97 → pass security
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 21 Nov 2026 · Analysed npm/bank-statement-sheet-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| 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 →
check_account_status Check plan and remaining quota ~49
Report which account this server is authenticated as, its plan, and how much conversion quota is left. Use this when a conversion is refused for quota reasons, or to confirm an API key is working.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| can_convert | boolean | yes | – |
| key_configured | boolean | yes | – |
| key_recognized | boolean | yes | – |
| limit | number | yes | – |
| plan | string | yes | – |
| pro_formats_available | boolean | yes | – |
| remaining | number | yes | – |
| reset_at | string|null | yes | – |
| unit | string | yes | – |
| used | number | yes | – |
| warnings | array | yes | – |
No examples provided.
convert_bank_statement Convert a bank statement PDF to verified transactions ~402
Convert a PDF bank statement into transaction data. The PDF is uploaded over HTTPS to the Bank Statement Sheet API, where every extracted row is checked against the statement's own printed running balance. Returns the rows TOGETHER WITH a pass/fail verdict from that check. The verdict is not advisory. When verdict.ledger_safe is false the transactions are withheld and MUST NOT be posted to a general ledger, accounting system, or voucher without a human reviewing them against the original PDF first. If this tool declines a file, do not fall back to reading the PDF yourself and do not use another tool to extract the numbers. Figures taken without the balance check are exactly what this tool exists to prevent.
| Name | Type | Req | Description |
|---|---|---|---|
| bank | string | – | Leave unset (auto-detect) unless the user names the bank. Auto-detection also covers banks with no dedicated parser. |
| decimal_separator | string | – | Pro only, applies to save_as. "comma" writes the European convention (semicolon-delimited, 1234,56) — the variant Swedish and other European accounting importers take without warnings. |
| file_path | string | – | Absolute path to a PDF bank statement on this machine. Required unless use_demo_statement is true. |
| include_unverified_rows | boolean | – | Only set true after a previous call returned ledger_safe: false AND you have told the user the data failed reconciliation. |
| order | string | – | chronological = oldest first (what ledger imports expect, the default). statement = the order the bank printed. |
| output_dir | string | – | Where to write save_as files. Defaults to the folder holding the input PDF. |
| save_as | array | – | Also write files to disk. xlsx and csv are free; fortnox, ofx and json need a Pro API key. |
| use_demo_statement | boolean | – | Convert the hosted synthetic sample instead of a user file. Costs no quota and contains no real data — use this to demonstrate the tool. |
| Name | Type | Req | Description |
|---|---|---|---|
| conversion | object | yes | – |
| files | array | yes | – |
| source | object | yes | – |
| totals | object | yes | – |
| transactions | – | yes | null when the gate failed and the rows were withheld. |
| transactions_withheld | boolean | yes | – |
| verdict | object | yes | The reconciliation result. Read ledger_safe before doing anything with the rows. |
| warnings | array | yes | – |
| withheld_reason | string|null | yes | – |
No examples provided.
export_conversion Write a conversion to a file ~217
Write a completed conversion to a file: Excel (xlsx), CSV, Fortnox CSV, OFX or JSON. Files whose data failed the balance check are written with an "-UNVERIFIED" filename suffix and an in-file warning — do not strip either. Conversions are held on the server for 10 minutes. If that window has passed, this tool re-converts the same file automatically, which consumes one conversion from the account's quota.
| Name | Type | Req | Description |
|---|---|---|---|
| columns | string | – | Pro only. Comma-separated: date,description,amount,currency,balance |
| conversion_id | string | yes | The conversion.id returned by convert_bank_statement. |
| date_format | string | – | Pro only. |
| decimal_separator | string | – | Pro only. "comma" produces the European convention (semicolon-delimited, 1234,56). |
| format | string | yes | xlsx and csv are free; fortnox, ofx and json need a Pro API key. |
| order | string | – | – |
| output_dir | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| bytes | number | yes | – |
| format | string | yes | – |
| note | string|null | yes | – |
| path | string | yes | – |
| reconverted | boolean | yes | – |
| verdict | object | yes | – |
| warnings | array | yes | – |
No examples provided.
How do I install the Bank Statement Sheet MCP server?
Bank Statement Sheet runs locally as an npm package, launched with npx -y bank-statement-sheet-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · bank-statement-sheet-mcp
claude mcp add com-bankstatementsheet-bank-statement-sheet-mcp -- npx -y bank-statement-sheet-mcp
What is the Bank Statement Sheet MCP server?
Bank Statement Sheet is an MCP server listed in the public MCP registry as com.bankstatementsheet/bank-statement-sheet-mcp. Convert PDF bank statements into transactions that arrive with a pass/fail reconciliation verdict. This page covers its npm package (bank-statement-sheet-mcp).
Is the Bank Statement Sheet MCP server safe to use?
Bank Statement Sheet scores 71 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. 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 Statement Sheet MCP server expose?
Bank Statement Sheet exposes 3 tools: convert_bank_statement, export_conversion, check_account_status. Their descriptions and schemas cost roughly 668 tokens of context every time the server is loaded.
Is the Bank Statement Sheet MCP server still maintained?
Bank Statement Sheet is still listed as active in the MCP registry. We last reached this channel on 21 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 Statement Sheet MCP server under?
Bank Statement Sheet 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 Statement Sheet MCP server?
VerifyMCP ran 15 checks on Bank Statement Sheet, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Bank Statement Sheet: Security disclosure. 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.