Tallyproof Bank Statements
REMOTE · STATEMENT-CONVERTER.ZOVO.ONE
Bank statement to spreadsheet
Available components
Last scanned (23 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 22 Oct 2026.
Category Finance and Payments
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- 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 966 tokens (~322/item across 3 items; 2 tools + 1 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
- Supports UI / widget rendering.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 22 Oct 26 73
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 22 Oct 2026 · Probed https://statement-converter.zovo.one/mcp
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 | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 5c36b5e62a8f959113a80bb74b47b8ef |
| SANs: zovo.one, statement-converter.zovo.one, *.statement-converter.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 statement-converter.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 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://statement-converter.zovo.one/mcp | Verified | 200 | |
| http (plaintext) | http://statement-converter.zovo.one/mcp | HTTPS enforced | 301 | https://statement-converter.zovo.one/mcp |
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 →
convert_bank_statement Convert bank statement ~497
Use this when the user attaches a bank or credit card statement (text PDF, or the bank's CSV/Excel export) and wants it converted to Excel or CSV: "convert bank statement to excel", "bank statement pdf to csv", "import my statement into QuickBooks", "does my statement balance". Extracts each transaction (date, description, signed amount, running balance), reconciles opening + transactions = closing to the cent, points to missing or duplicated rows, suggests categories, and returns Excel, CSV and QuickBooks CSV downloads. Does not read scanned images (needs OCR first), does not connect to bank accounts, and is not for non-financial PDFs or general PDF editing.
| Name | Type | Req | Description |
|---|---|---|---|
| account_type | string | – | auto (default): a PDF is classified from its text; pasted rows and CSV/Excel exports count as bank unless the balances or the sign pattern show a credit card (the result says so). bank: checking or s… |
| closing_balance | number | – | Closing (ending or new) balance in dollars, e.g. 5034.47. Used with opening_balance to prove the total to the cent. |
| date_order | string | – | Order of numeric dates in a CSV/Excel export: MDY (US, 09/02/2026, default) or DMY (02/09/2026). Detected automatically when a day is above 12. |
| file | object | yes | The statement to convert: a text PDF downloaded from the bank or card website, or the bank's CSV or Excel (.xlsx) transaction export, e.g. september-statement.pdf. |
| flip_signs | boolean | – | Only for CSV/Excel exports that list purchases as positive and payments as negative (common in credit card exports): true flips each amount so money out is negative. Default false. |
| opening_balance | number | – | Opening (beginning or previous) balance in dollars, e.g. 4123.55. Only needed when the file has none, such as a CSV export without a balance column, or to override. |
| statement_year | integer | – | Closing year of the statement, used for dates printed without a year when the period is not on the file, e.g. 2026 (a December-January statement uses the January year). |
| Name | Type | Req | Description |
|---|---|---|---|
| account | object | yes | – |
| categories | array | yes | Suggested categories from keyword rules; review before filing. |
| downloads | object | yes | – |
| months | array | yes | – |
| note | string | yes | – |
| period | object | yes | – |
| preview | array | yes | – |
| reconciliation | object | yes | – |
| source | object | yes | – |
| transactions | number | yes | – |
| warnings | array | yes | – |
No examples provided.
summarize_transactions Summarize transactions ~406
Use this when the user pastes or lists bank or credit card transactions (date, description, amount) and wants them reconciled, totaled by month or category, or exported: "does my statement balance", "money in and out by month", "categorize these transactions", "make a QuickBooks CSV from these". Checks opening + transactions = closing to the cent and the running balance row by row, points to the rows that break it, suggests categories, and returns Excel, CSV and QuickBooks CSV downloads. Do not use when a statement file is attached (use convert_bank_statement); does not give tax or accounting advice.
| Name | Type | Req | Description |
|---|---|---|---|
| account_type | string | – | auto (default): a PDF is classified from its text; pasted rows and CSV/Excel exports count as bank unless the balances or the sign pattern show a credit card (the result says so). bank: checking or s… |
| closing_balance | number | – | Closing (ending or new) balance in dollars, e.g. 5034.47. Used with opening_balance to prove the total to the cent. |
| opening_balance | number | – | Opening (beginning or previous) balance in dollars, e.g. 4123.55. Only needed when the file has none, such as a CSV export without a balance column, or to override. |
| statement_year | integer | – | Closing year of the statement, used for dates printed without a year when the period is not on the file, e.g. 2026 (a December-January statement uses the January year). |
| transactions | array | yes | The transactions in statement order, e.g. [{"date":"2026-09-02","description":"PAYROLL ACME INC","amount":2450}, {"date":"2026-09-03","description":"GREENLEAF MARKET","amount":-82.17}]. |
| Name | Type | Req | Description |
|---|---|---|---|
| account | object | yes | – |
| categories | array | yes | Suggested categories from keyword rules; review before filing. |
| downloads | object | yes | – |
| months | array | yes | – |
| note | string | yes | – |
| period | object | yes | – |
| preview | array | yes | – |
| reconciliation | object | yes | – |
| source | object | yes | – |
| transactions | number | yes | – |
| warnings | array | yes | – |
No examples provided.
How do I install the Tallyproof Bank Statements MCP server?
Tallyproof Bank Statements is a hosted endpoint at https://statement-converter.zovo.one/mcp, 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 · statement-converter.zovo.one
claude mcp add --transport http theluckystrike-statement-converter 'https://statement-converter.zovo.one/mcp'
What is the Tallyproof Bank Statements MCP server?
Tallyproof Bank Statements is an MCP server listed in the public MCP registry as io.github.theluckystrike/statement-converter. Bank statement to spreadsheet. This page covers its hosted endpoint (https://statement-converter.zovo.one/mcp).
Is the Tallyproof Bank Statements MCP server safe to use?
Tallyproof Bank Statements scores 73 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 Tallyproof Bank Statements MCP server expose?
Tallyproof Bank Statements exposes 2 tools: convert_bank_statement, summarize_transactions. Their descriptions and schemas cost roughly 903 tokens of context every time the server is loaded.
Does the Tallyproof Bank Statements MCP server require authentication?
No. We connected to Tallyproof Bank Statements without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Tallyproof Bank Statements MCP server still maintained?
Tallyproof Bank Statements is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.