# io.github.theluckystrike/bank-statement-csv-categorize-reconcile-ledger (remote · mcp.zovo.one)

Import a bank CSV, categorise it, summarise it per currency and reconcile it against your expenses.

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.zovo.one`: 82/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-bank-statement-csv-categorize-reconcile-ledger/mcp-bank-statement.md), [page](https://verifymcp.io/servers/theluckystrike-bank-statement-csv-categorize-reconcile-ledger/mcp-bank-statement)
- mcpb · `bank-statement.mcpb`: 50/100, [markdown](https://verifymcp.io/servers/theluckystrike-bank-statement-csv-categorize-reconcile-ledger/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-bank-state.md), [page](https://verifymcp.io/servers/theluckystrike-bank-statement-csv-categorize-reconcile-ledger/https-github-com-theluckystrike-mcp-servers-releases-download-v0-22-0-bank-state)

## Channel facts

- Endpoint: `https://mcp.zovo.one/mcp/bank-statement`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.22.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-09-20.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 84/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1842 tokens (~108/item across 17 items; 15 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 98% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "bank_upload" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 16 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.

## Install

### How do I install the io.github.theluckystrike/bank-statement-csv-categorize-reco… MCP server?

io.github.theluckystrike/bank-statement-csv-categorize-reco… is a hosted endpoint at https://mcp.zovo.one/mcp/bank-statement, so there is nothing to install locally. 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 --transport http theluckystrike-bank-statement-csv-categorize-rec 'https://mcp.zovo.one/mcp/bank-statement'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-bank-statement-csv-categorize-rec": {
      "url": "https://mcp.zovo.one/mcp/bank-statement"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-bank-statement-csv-categorize-rec": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/bank-statement"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-bank-statement-csv-categorize-rec]
url = "https://mcp.zovo.one/mcp/bank-statement"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-bank-statement-csv-categorize-rec": {
      "type": "remote",
      "url": "https://mcp.zovo.one/mcp/bank-statement",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-bank-statement-csv-categorize-rec --url 'https://mcp.zovo.one/mcp/bank-statement' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-bank-statement-csv-categorize-rec:
    url: "https://mcp.zovo.one/mcp/bank-statement"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-bank-statement-csv-categorize-rec": {
      "Transport": "http",
      "Url": "https://mcp.zovo.one/mcp/bank-statement"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-bank-statement-csv-categorize-rec -t streamable-http -u 'https://mcp.zovo.one/mcp/bank-statement'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-bank-statement-csv-categorize-rec": {
      "type": "http",
      "url": "https://mcp.zovo.one/mcp/bank-statement"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-09-19 (score 82, +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.

### 2026-09-17 (score 81, +1)

- [functional] Server version: 0.21.0 → 0.22.0

### 2026-09-14 (score 80, +1)

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

### 2026-09-12 (score 79, +8)

- [security improvement] Judged manipulation: unverified → pass
- [functional improvement] Schema quality: unverified → good

### 2026-09-11 (score 71, −7)

- [security regression] Judged manipulation: pass → unverified
- [security] Tool “license_activate” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: good → unverified
- [functional] New prompt “upgrade_to_pro”
- [functional] New resource “pricing”

### 2026-09-10 (score 78, +1)

- [security] Tool “license_status” rewrote its description, which is the text the model reads
- [security] Tool “license_activate” rewrote its description, which is the text the model reads
- [security] Tool “category_rules” rewrote its description, which is the text the model reads
- [security] Tool “accounts_list” rewrote its description, which is the text the model reads
- [security] Tool “transaction_categorize” rewrote its description, which is the text the model reads
- [security] Tool “recurring_detect” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “license_activate” reworded the description of “key”

### 2026-09-09 (score 77, +41)

- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: 0
- [functional] First check of Tool coverage: 98
- [functional] First check of Schema quality: pass
- [functional] First check of Schema quality: good

### 2026-09-04 (score 36)

First indexed and scored.

## MCP tools (15)

### `statement_import` (~207 tokens)

Import a bank CSV

Call this tool to read a bank CSV into the local ledger. Columns detected from headers (date, description, amount, currency, balance); amounts use the file's locale; stored lines skipped. Returns detected/stored/skipped.

Input parameters:

- `account` (string): Name for this account, e.g. "business EUR". Default: the file name without its extension. Later imports of the same account are deduplicated against it
- `bank` (string): Bank profile. Default "auto": the headers decide. "generic" skips profile detection and uses the header heuristics alone
- `currency` (string): Currency for rows where the file names none. Defaults to the shared business profile's default_currency, else EUR; the response says which it used
- `overwrite` (boolean): Delete every transaction already stored for this account before importing, instead of merging. Use it when the bank reissued a corrected export
- `path` (string, required): Name of a statement uploaded with bank_upload

### `transactions_list` (~151 tokens)

List transactions

List stored transactions in a date range, optionally for one account or category, or only the ones no rule has categorised yet. Totals are reported per currency and never added across currencies.

Input parameters:

- `account` (string): Limit to one account, as named at import
- `category` (string): Only transactions in this category
- `from` (string): ISO date YYYY-MM-DD, inclusive. Default: the start of the current month
- `limit` (integer): Rows returned, default 200. Totals always cover the whole range
- `to` (string): ISO date YYYY-MM-DD, inclusive. Default: today
- `uncategorized` (boolean): Only transactions with no category yet

### `transactions_search` (~102 tokens)

Search transactions

Find transactions whose description, counterparty, category or account contains the query. Case-insensitive substring search, never a regex, so a query with brackets in it cannot hang the server.

Input parameters:

- `from` (string): ISO date, inclusive
- `limit` (integer): Rows returned, default 100
- `query` (string, required): Text to look for, e.g. "spotify" or "acme"
- `to` (string): ISO date, inclusive

### `category_rules` (~110 tokens)

Set or list category rules

Read the category rules, or pass rules to REPLACE the whole list. A plain match is a substring; a regex compiles only if it cannot backtrack exponentially. An empty match is refused. Free: 5 rules.

Input parameters:

- `reapply_all` (boolean): Also overwrite categories set by an earlier rule or by hand. Default false: only uncategorised transactions are touched
- `rules` (array): The complete rule list; it replaces the stored one. Omit to list the current rules

### `transaction_categorize` (~89 tokens)

Categorise transactions by id

Set or clear the category on transactions by id, for a one-off no rule is worth writing for. Every id is checked first, so one unknown id refuses the whole call. category_rules matches by text instead.

Input parameters:

- `category` (string, required): Category to set. Pass an empty string to clear it
- `ids` (array, required): Transaction ids, as returned by transactions_list or transactions_search

### `statement_summary` (~133 tokens)

What I spent, from the bank account

What was spent/received in a date range per the BANK ACCOUNT, grouped by category, month, account or counterparty. For "what did I spend in August" once imported. Totals are per currency, never summed or converted.

Input parameters:

- `account` (string): Limit the summary to one account
- `from` (string): ISO date, inclusive. Default: the start of the current month
- `group_by` (string): Default category
- `to` (string): ISO date, inclusive. Default: today
- `top` (integer): Groups returned per currency, largest net first. Default 25

### `reconcile_expenses` (~129 tokens)

Reconcile against the expense ledger

Match bank debits against mcp-expense-tracker entries: same currency and amount, date within a few days. Reports matches, unmatched bank lines, expenses never hitting the bank. Read-only. Free: 31 days; Pro: any range.

Input parameters:

- `account` (string): Limit to one bank account
- `from` (string, required): ISO date, inclusive
- `to` (string, required): ISO date, inclusive
- `window_days` (integer): Allowed gap between the expense date and the bank date, default 3. A card payment usually settles a day or two after the receipt

### `recurring_detect` (~115 tokens)

Subscriptions and recurring charges in the bank data

Find charges that come back: debits grouped by counterparty and currency with a steady amount and interval, with cadence, typical amount, next due date and annual cost. Free: 3 months, 5 charges.

Input parameters:

- `account` (string): Limit to one account
- `min_occurrences` (integer): Occurrences required before a charge counts as recurring, default 2
- `months` (integer): How far back to look, default 3. Two occurrences are enough to see a cadence, three make it certain

### `statement_export` (~153 tokens)

Export bank transactions to a file

Export the BANK transactions of a date range (a month, a quarter, a year) as .csv or .json and return a download link valid for one hour. This is the tool for "export September" once a statement has been imported. Nothing partial is ever written.

Input parameters:

- `account` (string): Limit to one account
- `category` (string): Limit to one category
- `format` (string, required): csv for a spreadsheet, json for a program
- `from` (string, required): ISO date, inclusive
- `path` (string, required): Name for the downloaded file, e.g. september. It comes back as a download link valid for one hour
- `to` (string, required): ISO date, inclusive

### `accounts_list` (~48 tokens)

List accounts

List the imported accounts: bank, currencies, transaction count, first and last date, and the closing balance when the file carried one. Start here for the account names transactions_list and statement_export take.

### `license_status` (~55 tokens)

License status

Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.

### `license_activate` (~76 tokens)

Activate license

Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.

Input parameters:

- `key` (string, required): License key from checkout, MCPL1.<payload>.<signature>

### `bank_upload` (~330 tokens)

Upload a bank statement file

Send a bank export to this hosted endpoint. There is no filesystem here, so instead of a path you upload the file once with bank_upload and then pass its name as `path` to statement_import. Give exactly one of content (the export as text, header row included - this is the normal case for a CSV), content_base64 (the file's bytes, which keeps a UTF-16 export from Excel readable) or url. url: fetch a public file instead of pasting base64 (recommended above about 10 KB): the url is fetched here with a 10 second timeout, at most 3 redirects, public http(s) hosts only, and a 1 MB cap; the fetched file has to be delimited text, so a PDF statement is refused rather than stored. Uploads are kept for your token between calls; bank_files lists them and bank_delete_upload removes one. The request body cap is 256 KB, so a large export pasted as text has to be split by month.

Input parameters:

- `content` (string): The export as text, including the header row
- `content_base64` (string): The file's bytes, base64-encoded, instead of text
- `name` (string, required): Name to refer to this statement by: 1-64 characters of letters, digits, underscore or dash, e.g. "september"
- `url` (string): url: fetch a public file instead of pasting base64 (recommended above about 10 KB). Public http(s) only; private, link-local and this endpoint's own zone are refused

### `bank_files` (~21 tokens)

List uploaded statements

List the statement files stored for your token, with their sizes.

### `bank_delete_upload` (~43 tokens)

Delete an uploaded statement

Delete one statement file stored for your token. The transactions already imported from it are kept; transactions_list and the summary still see them.

Input parameters:

- `name` (string, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-bank-statement-csv-categorize-reconcile-ledger/mcp-bank-statement#diagnostics

## Score history

- 2026-09-20: 82
- 2026-09-19: 82
- 2026-09-18: 81
- 2026-09-17: 81
- 2026-09-16: 80
- 2026-09-15: 80
- 2026-09-14: 80
- 2026-09-13: 79
- 2026-09-12: 79
- 2026-09-11: 71
- 2026-09-10: 78
- 2026-09-09: 77
- 2026-09-08: 36
- 2026-09-07: 36
- 2026-09-06: 36
- 2026-09-05: 36
- 2026-09-04: 36

## Common questions

### What is the io.github.theluckystrike/bank-statement-csv-categorize-reco… MCP server?

io.github.theluckystrike/bank-statement-csv-categorize-reco… is an MCP server listed in the public MCP registry as io.github.theluckystrike/bank-statement-csv-categorize-reco…. Import a bank CSV, categorise it, summarise it per currency and reconcile it against your expenses. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/bank-statement).

### Is the io.github.theluckystrike/bank-statement-csv-categorize-reco… MCP server safe to use?

io.github.theluckystrike/bank-statement-csv-categorize-reco… scores 82 out of 100 on VerifyMCP. 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 io.github.theluckystrike/bank-statement-csv-categorize-reco… MCP server expose?

io.github.theluckystrike/bank-statement-csv-categorize-reco… exposes 15 tools: statement_import, transactions_list, transactions_search, category_rules, transaction_categorize, and 10 more. Their descriptions and schemas cost roughly 1,762 tokens of context every time the server is loaded.

### Does the io.github.theluckystrike/bank-statement-csv-categorize-reco… MCP server require authentication?

Yes. io.github.theluckystrike/bank-statement-csv-categorize-reco… asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the io.github.theluckystrike/bank-statement-csv-categorize-reco… MCP server still maintained?

io.github.theluckystrike/bank-statement-csv-categorize-reco… is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.zovo.one/mcp/bank-statement
- Authorisation metadata: https://mcp.zovo.one/.well-known/oauth-protected-resource/mcp/bank-statement
- Repository: https://github.com/theluckystrike/mcp-servers
- Website: https://mcp.zovo.one/s/bank-statement
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-bank-statement-csv-categorize-reconcile-ledger/mcp-bank-statement.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-bank-statement-csv-categorize-reconcile-ledger/mcp-bank-statement.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-bank-statement-csv-categorize-reconcile-ledger/mcp-bank-statement