# StatementSure (npm · statementsure-mcp)

Bank statement PDFs to verified QuickBooks, Xero, OFX, CSV and Excel files. Runs locally.

- Trust score: 62/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- npm · `statementsure-mcp`: 62/100 (this document), [markdown](https://verifymcp.io/servers/com-statementsure-statementsure/statementsure-mcp.md), [page](https://verifymcp.io/servers/com-statementsure-statementsure/statementsure-mcp)

## Channel facts

- Registry: `npm`
- Package: `statementsure-mcp`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Supply Chain Security**: 89/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects uuid 8.3.2, reached via exceljs > uuid. A fixed version is available.
  - No install/post-install scripts declared.
  - Dependency health was assessed across the 256 of 276 dependencies we could resolve, so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - 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.
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add com-statementsure-statementsure -- npx -y statementsure-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-statementsure-statementsure": {
      "command": "npx",
      "args": [
        "-y",
        "statementsure-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-statementsure-statementsure": {
      "command": "npx",
      "args": [
        "-y",
        "statementsure-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-statementsure-statementsure -- npx -y statementsure-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-statementsure-statementsure": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "statementsure-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-statementsure-statementsure --command npx --arg -y --arg statementsure-mcp
```

### Hermes

```yaml
mcp_servers:
  com-statementsure-statementsure:
    command: "npx"
    args: ["-y", "statementsure-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-statementsure-statementsure": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "statementsure-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-statementsure-statementsure -t stdio -c npx -a -y statementsure-mcp
```

### Other

```json
{
  "mcpServers": {
    "com-statementsure-statementsure": {
      "command": "npx",
      "args": [
        "-y",
        "statementsure-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-13 (score 62, +29)

- [security improvement] 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).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] 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

### 2026-10-12 (score 33)

First indexed and scored.

## MCP tools (4)

### `check_statements` (~140 tokens)

Check bank statements

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.

Input parameters:

- `accountType` (string): Override the detected account type.
- `dateOrder` (string): Override the detected date order, e.g. DMY for 03/04 = 3 April.
- `files` (array, required): 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).

### `get_transactions` (~175 tokens)

Get statement transactions

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).

Input parameters:

- `accountType` (string): Override the detected account type.
- `dateOrder` (string): Override the detected date order, e.g. DMY for 03/04 = 3 April.
- `files` (array, required): 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).

### `export_statements` (~359 tokens)

Export statements to a file

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.

Input parameters:

- `accountType` (string): Override the detected account type.
- `dateOrder` (string): Override the detected date order, e.g. DMY for 03/04 = 3 April.
- `files` (array, required): 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, required): 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.

### `usage` (~22 tokens)

Free pages left

How many free statement pages are left this month for exports and transaction lists.

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-statementsure-statementsure/statementsure-mcp#diagnostics

## Score history

- 2026-10-18: 62
- 2026-10-17: 62
- 2026-10-16: 62
- 2026-10-15: 62
- 2026-10-14: 62
- 2026-10-13: 62
- 2026-10-12: 33

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/statementsure-mcp
- Socket report: https://socket.dev/npm/package/statementsure-mcp
- Repository: https://github.com/alhogeiri2025/statementsure-mcp
- Website: https://statementsure.com/?ref=mcp-registry
- Changelog RSS feed: https://verifymcp.io/servers/com-statementsure-statementsure/statementsure-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-statementsure-statementsure/statementsure-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-statementsure-statementsure/statementsure-mcp