kontozack-mcp
Related Servers
Alternatives to kontozack-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceConverts customer-supplied PDF bank statements into checked Excel, CSV, or JSON with balance validation. Runs locally with your own MainBook API key or against MainBook's hosted endpoint, and it never connects to bank accounts.5MIT
- AlicenseAqualityDmaintenanceConverts PDF bank statements into structured data (Markdown, JSON, CSV, JSONL) with verified transactions and balance checks, enabling agents to audit numbers.59 npmMIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to parse and analyze PDF invoices, including text, field, and table extraction, OCR for scanned documents, ZUGFeRD support, compliance validation, and batch processing via MCP.-
- AlicenseAqualityBmaintenanceEnables parsing and filtering of mBank CSV operation exports locally. Supports data aggregation and querying through natural language, running entirely offline with no network calls.31MIT
- AlicenseNot gradedqualityBmaintenanceEnables importing and reconciling Mexican bank statement PDFs and files into an auditable SQLite ledger, with tools to preview, review, and commit transactions via Claude.MIT
- AlicenseBqualityAmaintenanceEnables local MCP-based accounting operations for Billy: receipt import with provenance, reviewed bookkeeping drafts, payments, and bank reconciliation.2147 npm1MIT
TDQS
Scored across 3 tools
Each tool has a distinct primary outcome: structured parse, CSV export, and validation-only. However, parse_bank_statement already returns proof-calculation validation checks, so it partially overlaps with validate_bank_statement, and all three re-parse the same PDF, which could cause selection confusion.
All three tools follow a clean verb_noun snake_case pattern: parse_bank_statement, export_bank_statement_csv, validate_bank_statement. The shared domain suffix makes the pattern predictable and readable.
Three tools is on the lean side but each maps to a genuine need (parse, export, validate) for a narrow PDF-parsing domain. Nothing is redundant enough to warrant trimming, though the surface is thin.
The parse/export/validate lifecycle is covered, but only SumUp statements and only one export format (German CSV) are supported; no other bank formats, no alternate output formats, and no listing of supported statements despite the description pointing to more formats externally.