Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.theluckystrike/bank-statement-pdf

REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS

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

−13 this week 81 Trust /100

Last scanned (14 hours ago)

Scores higher than 79% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Recent critical change

Authorization (17 Nov 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability82
  • 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 1985 tokens (~116/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 Management96
  • Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 0 breaking changes, 1 auth/transport breaks, 0 additions. See how to fix → Fail
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 Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 17 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 17 Nov 26 −13
    • Authorization: pass → fail ▼ critical
    • Stability: pass → fail ▼ security
  • 12 Nov 26 0
    • Stability: 0.97 → pass security
  • 11 Nov 26 +1

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

  • 10 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 8 Nov 26 0
    • Stability: 0.97 → pass security
  • 7 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Stability: pass → 0.97 functional
  • 6 Nov 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
  • 2 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “bank_delete_upload” is now declared destructive security
    • Tool “bank_upload” is now declared destructive security
    • Destructive annotations: All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
Diagnostics

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 Nov 2026 · Probed https://mcp.zovo.one/mcp/bank-statement-pdf

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 31 Oct 2026 29 Jan 2027 ECDSA 256 ECDSA-SHA256 39e1adfa4eb6500e0e3d48868766e3e9
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. DS published 64939 8 Verified
zovo.one. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=15552000; includeSubDomains; preload
x-content-type-options nosniff

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/bank-statement-pdf Verified 200
http (plaintext) http://mcp.zovo.one/mcp/bank-statement-pdf HTTPS enforced 301 https://mcp.zovo.one/mcp/bank-statement-pdf
MCP tools · 15 exposed · ~1,762 tokens

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 →

Tool Tokens
accounts_list ~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 ~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.

NameTypeReqDescription
namestringyes–

No output schema declared.

No examples provided.

bank_files ~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 ~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.

NameTypeReqDescription
contentstring–The export as text, including the header row
content_base64string–The file's bytes, base64-encoded, instead of text
namestringyesName to refer to this statement by: 1-64 characters of letters, digits, underscore or dash, e.g. "september"
urlstring–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 ~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.

NameTypeReqDescription
reapply_allboolean–Also overwrite categories set by an earlier rule or by hand. Default false: only uncategorised transactions are touched
rulesarray–The complete rule list; it replaces the stored one. Omit to list the current rules

No output schema declared.

No examples provided.

license_activate ~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.

NameTypeReqDescription
keystringyesLicense key from checkout, MCPL1.<payload>.<signature>

No output schema declared.

No examples provided.

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

NameTypeReqDescription
accountstring–Limit to one bank account
fromstringyesISO date, inclusive
tostringyesISO date, inclusive
window_daysinteger–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 ~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.

NameTypeReqDescription
accountstring–Limit to one account
min_occurrencesinteger–Occurrences required before a charge counts as recurring, default 2
monthsinteger–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 ~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.

NameTypeReqDescription
accountstring–Limit to one account
categorystring–Limit to one category
formatstringyescsv for a spreadsheet, json for a program
fromstringyesISO date, inclusive
pathstringyesName for the downloaded file, e.g. september. It comes back as a download link valid for one hour
tostringyesISO date, inclusive

No output schema declared.

No examples provided.

statement_import ~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.

NameTypeReqDescription
accountstring–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
bankstring–Bank profile. Default "auto": the headers decide. "generic" skips profile detection and uses the header heuristics alone
currencystring–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
overwriteboolean–Delete every transaction already stored for this account before importing, instead of merging. Use it when the bank reissued a corrected export
pathstringyesName of a statement uploaded with bank_upload

No output schema declared.

No examples provided.

statement_summary ~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.

NameTypeReqDescription
accountstring–Limit the summary to one account
fromstring–ISO date, inclusive. Default: the start of the current month
group_bystring–Default category
tostring–ISO date, inclusive. Default: today
topinteger–Groups returned per currency, largest net first. Default 25

No output schema declared.

No examples provided.

transaction_categorize ~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.

NameTypeReqDescription
categorystringyesCategory to set. Pass an empty string to clear it
idsarrayyesTransaction ids, as returned by transactions_list or transactions_search

No output schema declared.

No examples provided.

transactions_list ~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.

NameTypeReqDescription
accountstring–Limit to one account, as named at import
categorystring–Only transactions in this category
fromstring–ISO date YYYY-MM-DD, inclusive. Default: the start of the current month
limitinteger–Rows returned, default 200. Totals always cover the whole range
tostring–ISO date YYYY-MM-DD, inclusive. Default: today
uncategorizedboolean–Only transactions with no category yet

No output schema declared.

No examples provided.

transactions_search ~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.

NameTypeReqDescription
fromstring–ISO date, inclusive
limitinteger–Rows returned, default 100
querystringyesText to look for, e.g. "spotify" or "acme"
tostring–ISO date, inclusive

No output schema declared.

No examples provided.

Install

How do I install the io.github.theluckystrike/bank-statement-pdf MCP server?

io.github.theluckystrike/bank-statement-pdf is a hosted endpoint at https://mcp.zovo.one/mcp/bank-statement-pdf, 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

# add to Claude Code
claude mcp add --transport http theluckystrike-bank-statement-pdf 'https://mcp.zovo.one/mcp/bank-statement-pdf'
Common questions

What is the io.github.theluckystrike/bank-statement-pdf MCP server?

io.github.theluckystrike/bank-statement-pdf is an MCP server listed in the public MCP registry as io.github.theluckystrike/bank-statement-pdf. 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-pdf).

Is the io.github.theluckystrike/bank-statement-pdf MCP server safe to use?

io.github.theluckystrike/bank-statement-pdf scores 81 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-pdf MCP server expose?

io.github.theluckystrike/bank-statement-pdf 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-pdf MCP server require authentication?

No. We connected to io.github.theluckystrike/bank-statement-pdf without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.theluckystrike/bank-statement-pdf MCP server still maintained?

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

What did VerifyMCP test on the io.github.theluckystrike/bank-statement-pdf MCP server?

VerifyMCP ran 13 checks on io.github.theluckystrike/bank-statement-pdf, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.