StatementSure
NPM · STATEMENTSURE-MCP
Bank statement PDFs to verified QuickBooks, Xero, OFX, CSV and Excel files. Runs locally.
Available components
Last scanned (15 hours ago)
Scores higher than 36% 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 Security89
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects uuid 8.3.2, reached via exceljs > uuid. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 256 of 276 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
- 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 843 tokens (~210/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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 13 Oct 26 +29
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- 12 Oct 26 33
First indexed and scored.
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 18 Oct 2026 · Analysed npm/statementsure-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-w5hq-g745-h8pq | CVE-2026-41907 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 256 packages
| Packages resolved | 256 |
|---|---|
| Deprecated | 6 |
| Stale | 101 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
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_statements Check bank statements ~140
Read bank or credit card statement PDFs and check that they balance. Returns the bank, account, period, opening/closing balances, totals, each balance check, rows that need a look, and the pages an export would use. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| accountType | string | – | Override the detected account type. |
| dateOrder | string | – | Override the detected date order, e.g. DMY for 03/04 = 3 April. |
| files | array | yes | Absolute paths of statement PDFs on this computer. Several statements from one account can go together. |
| password | string | – | Password for protected PDFs (the same one for every file). |
No output schema declared.
No examples provided.
export_statements Export statements to a file ~359
Write the statements' transactions to an import file next to the PDFs (or in outDir). Formats: xlsx = Excel (.xlsx) (Transactions + summary sheet); csv = CSV (Any spreadsheet or accounting tool); qbo = QuickBooks (.qbo) (QuickBooks Desktop & Online bank upload); qb-csv = QuickBooks Online CSV (3-column Date, Description, Amount); xero = Xero CSV (Xero bank statement import); ofx = OFX (Quicken, Xero, Wave, most finance apps). csv and xlsx put all statements in one file; the import formats (qbo, qb-csv, xero, ofx) write one file per account, because each import goes into one bank account. separate = one file per statement. Statements with no transactions are skipped. Uses free monthly pages like get_transactions.
| Name | Type | Req | Description |
|---|---|---|---|
| accountType | string | – | Override the detected account type. |
| dateOrder | string | – | Override the detected date order, e.g. DMY for 03/04 = 3 April. |
| files | array | yes | Absolute paths of statement PDFs on this computer. Several statements from one account can go together. |
| flipSigns | boolean | – | Multiply amounts by -1 (some tools want card charges positive). |
| format | string | yes | Export format. |
| intuBid | string | – | Intuit bank ID for .qbo files, if QuickBooks rejects the default. |
| outDir | string | – | Absolute folder for the export. Default: the folder of the first PDF. |
| password | string | – | Password for protected PDFs (the same one for every file). |
| separate | boolean | – | Write one export per statement instead of one combined file. |
No output schema declared.
No examples provided.
get_transactions Get statement transactions ~175
Return every transaction (date, description, signed amount, running balance, flags) from statement PDFs, for categorizing, reconciling or entering into accounting software. Money in is positive, money out negative. Uses free monthly pages (statements that don't balance are free; repeats of a file this month are free).
| Name | Type | Req | Description |
|---|---|---|---|
| accountType | string | – | Override the detected account type. |
| dateOrder | string | – | Override the detected date order, e.g. DMY for 03/04 = 3 April. |
| files | array | yes | Absolute paths of statement PDFs on this computer. Several statements from one account can go together. |
| flipSigns | boolean | – | Multiply amounts by -1 (some tools want card charges positive). |
| password | string | – | Password for protected PDFs (the same one for every file). |
No output schema declared.
No examples provided.
usage Free pages left ~22
How many free statement pages are left this month for exports and transaction lists.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the StatementSure MCP server?
StatementSure runs locally as an npm package, launched with npx -y statementsure-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 · statementsure-mcp
claude mcp add com-statementsure-statementsure -- npx -y statementsure-mcp
What is the StatementSure MCP server?
StatementSure is an MCP server listed in the public MCP registry as com.statementsure/statementsure. Bank statement PDFs to verified QuickBooks, Xero, OFX, CSV and Excel files. Runs locally. This page covers its npm package (statementsure-mcp).
Is the StatementSure MCP server safe to use?
StatementSure scores 62 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 18 October 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 StatementSure MCP server expose?
StatementSure exposes 4 tools: check_statements, get_transactions, export_statements, usage. Their descriptions and schemas cost roughly 696 tokens of context every time the server is loaded.
Is the StatementSure MCP server still maintained?
StatementSure is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.