io.github.theluckystrike/categorize-transactions
REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS · SCANNED SEP 30
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 against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 98% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 16 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
How do I install the io.github.theluckystrike/categorize-transactions MCP server?
io.github.theluckystrike/categorize-transactions is a hosted endpoint at https://mcp.zovo.one/mcp/categorize-transactions, 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.
remote · mcp.zovo.one
claude mcp add --transport http theluckystrike-categorize-transactions 'https://mcp.zovo.one/mcp/categorize-transactions'
{
"mcpServers": {
"theluckystrike-categorize-transactions": {
"url": "https://mcp.zovo.one/mcp/categorize-transactions"
}
}
} {
"servers": {
"theluckystrike-categorize-transactions": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/categorize-transactions"
}
}
} [mcp_servers.theluckystrike-categorize-transactions] url = "https://mcp.zovo.one/mcp/categorize-transactions"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"theluckystrike-categorize-transactions": {
"type": "remote",
"url": "https://mcp.zovo.one/mcp/categorize-transactions",
"enabled": true
}
}
} openclaw mcp add theluckystrike-categorize-transactions --url 'https://mcp.zovo.one/mcp/categorize-transactions' --transport streamable-http
mcp_servers:
theluckystrike-categorize-transactions:
url: "https://mcp.zovo.one/mcp/categorize-transactions" {
"McpServers": {
"theluckystrike-categorize-transactions": {
"Transport": "http",
"Url": "https://mcp.zovo.one/mcp/categorize-transactions"
}
}
} assistant mcp add theluckystrike-categorize-transactions -t streamable-http -u 'https://mcp.zovo.one/mcp/categorize-transactions'
{
"mcpServers": {
"theluckystrike-categorize-transactions": {
"type": "http",
"url": "https://mcp.zovo.one/mcp/categorize-transactions"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 23 Sept 26 79
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 30 Sept 2026 · Probed https://mcp.zovo.one/mcp/categorize-transactions
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 2 Sept 2026 | 1 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ef74739bd6e575bb13db69661e215324 |
| SANs: zovo.one, mcp.zovo.one, *.mcp.zovo.one | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="mcp.zovo.one", error="invalid_token", resource_metadata="https://mcp.zovo.one/.well-known/oauth-protected-resource"
Bearer realm="mcp.zovo.one", error="invalid_token", resource_metadata="https://mcp.zovo.one/.well-known/oauth-protected-resource" | Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Protected resource metadata
| Document | https://mcp.zovo.one/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.zovo.one |
| Authorisation server | https://mcp.zovo.one |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.zovo.one/mcp/categorize-transactions | Verified | 200 | |
| http (plaintext) | http://mcp.zovo.one/mcp/categorize-transactions | HTTPS enforced | 301 | https://mcp.zovo.one/mcp/categorize-transactions |
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 ~48
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bank_delete_upload Delete an uploaded statement ~43
Delete one statement file stored for your token. The transactions already imported from it are kept; transactions_list and the summary still see them.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
bank_files List uploaded statements ~21
List the statement files stored for your token, with their sizes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
bank_upload Upload a bank statement file ~330
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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | The export as text, including the header row |
| content_base64 | string | – | The file's bytes, base64-encoded, instead of text |
| name | string | yes | 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 |
No output schema declared.
No examples provided.
category_rules Set or list category rules ~110
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.
| 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 ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | License key from checkout, MCPL1.<payload>.<signature> |
No output schema declared.
No examples provided.
license_status License status ~55
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.
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 ~115
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.
| 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 ~153
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.
| 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 | Name for the downloaded file, e.g. september. It comes back as a download link valid for one hour |
| to | string | yes | ISO date, inclusive |
No output schema declared.
No examples provided.
statement_import Import a bank CSV ~207
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 | Name of a statement uploaded with bank_upload |
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 ~89
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.
| 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 hosted endpoint (https://mcp.zovo.one/mcp/categorize-transactions).
Is the io.github.theluckystrike/categorize-transactions MCP server safe to use?
io.github.theluckystrike/categorize-transactions 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/categorize-transactions MCP server expose?
io.github.theluckystrike/categorize-transactions 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/categorize-transactions MCP server require authentication?
Yes. io.github.theluckystrike/categorize-transactions 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/categorize-transactions MCP server still maintained?
io.github.theluckystrike/categorize-transactions is still listed as active in the MCP registry. We last reached this channel on 30 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.