mcp-registry/io.github.theluckystrike/bank-statement-csv-categorize-reconcile-ledger · v0.22.6
As of 2026-10-26 02:58 UTC, the Theluckystrike Bank Statement Csv Categorize Reconcile Ledger MCP server is down with a Glimind reliability score of 24/100 (grade F). Over the last 30 days it answered 30.5% of Glimind's liveness checks. It had 912 outages in 90 days, with a median recovery of 40 minutes.
Import a bank CSV, categorise it, summarise it per currency and reconcile it against your expenses.
Point your MCP client at this streamable-http endpoint: https://mcp.zovo.one/mcp/bank-statement
The endpoint did not complete an MCP handshake.
Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →
Reachable 30.5% of the time over the last 30 days; median recovery 40 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
1 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
3 of 15 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.theluckystrike%2Fbank-statement-csv-categorize-reconcile-ledger/fixes
{
"name": "bank_delete_upload",
"description": "Delete one statement file stored for your token. The transactions already imported from it are kept; transactions_list and the summary still see them.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"maxLength": 70,
"minLength": 1
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": true,
"idempotentHint": true
},
"title": "Delete an uploaded statement"
}{
"name": "bank_files",
"description": "List the statement files stored for your token, with their sizes.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "List uploaded statements"
}{
"name": "bank_upload",
"description": "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",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"name"
],
"properties": {
"url": {
"type": "string",
"description": "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"
},
"name": {
"type": "string",
"maxLength": 70,
"minLength": 1,
"description": "Name to refer to this statement by: 1-64 characters of letters, digits, underscore or dash, e.g. \"september\""
},
"content": {
"type": "string",
"description": "The export as text, including the header row"
},
"content_base64": {
"type": "string",
"description": "The file's bytes, base64-encoded, instead of text"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
},
"title": "Upload a bank statement file"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.theluckystrike/bank-statement-csv-categorize-reconcile-ledger"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.theluckystrike/bank-statement-csv-categorize-reconcile-ledger"}) over MCP.
statement_import ~382 tokensbank_upload ~352 tokenscategory_rules ~320 tokensstatement_export ~289 tokenstransactions_list ~283 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.theluckystrike%2Fbank-statement-csv-categorize-reconcile-ledger?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.theluckystrike%2Fbank-statement-csv-categorize-reconcile-ledger?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.theluckystrike%2Fbank-statement-csv-categorize-reconcile-ledger.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.theluckystrike%2Fbank-statement-csv-categorize-reconcile-ledger.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.theluckystrike%2Fbank-statement-csv-categorize-reconcile-ledger?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:18036f577298cf3c…, first seen 2026-10-17, included at leaf 2452 of 74,962. Version history · verify what your client received.
Compare: most reliable finance servers · most reliable files servers · most reliable knowledge servers · most reliable security servers · most reliable other servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 02:58 UTC, the Theluckystrike Bank Statement Csv Categorize Reconcile Ledger MCP server is down with a Glimind reliability score of 24/100 (grade F). Over the last 30 days it answered 30.5% of Glimind's liveness checks. It had 912 outages in 90 days, with a median recovery of 40 minutes.
Theluckystrike Bank Statement Csv Categorize Reconcile Ledger MCP server advertises 15 tools, including accounts_list, bank_delete_upload, bank_files, bank_upload, category_rules.
Point your MCP client at this streamable-http endpoint: https://mcp.zovo.one/mcp/bank-statement
Glimind scanned all 15 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.