io.github.theluckystrike/categorize-transactions
MCPB · BANK-STATEMENT.MCPB · SCANNED SEP 21
Import a bank CSV, categorise it, summarise it per currency and reconcile it against your expenses.
Available components
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 Security23
- Malware scan not yet available for this package.Unverified
- Known CVEs were checked across the 105 of 105 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- 40 of 105 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 14 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1290 tokens (~99/item across 13 items; 12 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 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
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
mcpb · bank-statement.mcpb
Download bundleEvery 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 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +3
- Stability: unverified → 0.27 ▲ functional
- 17 Sept 26 +1
No change was recorded against any check on this day. Supply Chain Security went from 22 to 23.
- 12 Sept 26 49
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 21 Sept 2026 · Analysed mcpb/https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/bank-statement.mcpb@0.21.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
Background: How many MCP packages publish verified provenance →
Dependencies 105 packages
| Packages resolved | 105 |
|---|---|
| Stale | 40 |
| 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 →
accounts_list List accounts ~24
List the imported accounts with their bank, currency, transaction count and date range.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
category_rules Set or list category rules ~112
Set the rules that categorise transactions, or call with none to list them. Each rule matches counterparty/description: plain is a substring; regex: true compiles only if not exponential. Reapplies to uncategorised rows.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
license_activate Activate license ~42
Activate a Pro license key (format MCPL1.xxx.yyy). Verified offline and saved locally.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from the checkout confirmation page |
No output schema declared.
No examples provided.
license_status License status ~23
Show whether this server runs in free or Pro mode and where to upgrade.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
reconcile_expenses Reconcile against the expense ledger ~129
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.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Limit to one bank account |
| from | string | yes | ISO date, inclusive |
| to | string | yes | 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 |
No output schema declared.
No examples provided.
recurring_detect Subscriptions and recurring charges in the bank data ~122
Find charges that come back: same counterparty, steady amount and cadence. Reports cadence, typical amount, last/next due date, yearly cost per currency. Free: last 3 months, 5 charges; Pro: full history, every charge.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
statement_export Export bank transactions to a file ~138
Call this tool to write BANK transactions of a date range to a .csv or .json file and return the path. For "export September to <path>" once imported. Written atomically: a failed export never leaves a half file.
| Name | Type | Req | Description |
|---|---|---|---|
| account | string | – | Limit to one account |
| category | string | – | Limit to one category |
| format | string | yes | csv for a spreadsheet, json for a program |
| from | string | yes | ISO date, inclusive |
| path | string | yes | Where to write the file. ~ is expanded; the parent directory must exist |
| to | string | yes | ISO date, inclusive |
No output schema declared.
No examples provided.
statement_import Import a bank CSV ~213
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Path to the .csv file exported from the bank. ~ is expanded |
No output schema declared.
No examples provided.
statement_summary What I spent, from the bank account ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
transaction_categorize Categorise transactions by id ~73
Set the category on one or more transactions by id. Nothing is changed unless every id exists, so a typo cannot half-apply.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Category to set. Pass an empty string to clear it |
| ids | array | yes | Transaction ids, as returned by transactions_list or transactions_search |
No output schema declared.
No examples provided.
transactions_list List transactions ~151
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
transactions_search Search transactions ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | ISO date, inclusive |
| limit | integer | – | Rows returned, default 100 |
| query | string | yes | Text to look for, e.g. "spotify" or "acme" |
| to | string | – | ISO date, inclusive |
No output schema declared.
No examples provided.
What is the io.github.theluckystrike/categorize-transactions MCP server?
io.github.theluckystrike/categorize-transactions is an MCP server listed in the public MCP registry as io.github.theluckystrike/categorize-transactions. Import a bank CSV, categorise it, summarise it per currency and reconcile it against your expenses. This page covers its MCPB bundle (https://github.com/theluckystrike/mcp-servers/releases/download/v0.21.0/bank-statement.mcpb).
Is the io.github.theluckystrike/categorize-transactions MCP server safe to use?
io.github.theluckystrike/categorize-transactions scores 54 out of 100 on VerifyMCP. 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 io.github.theluckystrike/categorize-transactions MCP server expose?
io.github.theluckystrike/categorize-transactions exposes 12 tools: statement_import, transactions_list, transactions_search, category_rules, transaction_categorize, and 7 more. Their descriptions and schemas cost roughly 1,262 tokens of context every time the server is loaded.
What licence is the io.github.theluckystrike/categorize-transactions MCP server under?
io.github.theluckystrike/categorize-transactions declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.