StatementKit - bank statement normalizer MCP Server

by workers-zenith-ops-statementkit Your server? Claim it

answering

StatementKit - bank statement normalizer is answering right now. Last checked 3 min ago. It exposes 5 tools.

Normalize bank statements (CSV, camt, MT940, OFX, QIF) to JSON, analyze, export.

Uptime history 7 days of history

7 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

137 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check StatementKit - bank statement normalizer every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add statementkit --transport http https://statementkit.zenith-ops.workers.dev/mcp

Settings → Connectors → Add custom connector, then paste this address

https://statementkit.zenith-ops.workers.dev/mcp

~/.codex/config.toml

[mcp_servers.statementkit]
url = "https://statementkit.zenith-ops.workers.dev/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "statementkit": {
      "url": "https://statementkit.zenith-ops.workers.dev/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "statementkit": {
      "type": "http",
      "url": "https://statementkit.zenith-ops.workers.dev/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

parse

parse_statement

Paid ($0.005): Parses a bank statement (CSV from any bank, camt.052/053/054, MT940, OFX/QFX, QIF) into normalized JSON: accounts, balances and signed transactions with ISO dates, counterparty, reference and OCR number. Deterministic, no AI, nothing stored. JSON body up to 1000 KB. Failed calls (4xx/5xx) are not settled. Without a payment header the result is the x402 payment requirements.

parse_statement_demo

Free demo: parse a statement (max 24 KB) into normalized JSON; returns the first 100 transactions plus an analysis preview. Rate limited to 20 calls per hour.

analyze

analyze_statement

Paid ($0.01): Parses a statement and adds analysis: monthly totals, top counterparties, recurring payments, suspected duplicates, largest transactions and balance reconciliation. Set include_transactions=false to receive only the analysis. JSON body up to 1000 KB. Failed calls (4xx/5xx) are not settled. Without a payment header the result is the x402 payment requirements.

convert

convert_statement

Paid ($0.005): Parses a statement and exports it as normalized CSV, an hledger journal, a SIE4 file (experimental) or JSON. The converted file is returned as a string in the content field. JSON body up to 1000 KB. Failed calls (4xx/5xx) are not settled. Without a payment header the result is the x402 payment requirements.

formats

list_formats

List the supported statement formats, CSV column synonyms, limits and prices. Free.

Endpoints

URL	Transport	State	Latency	Checked
https://statementkit.zenith-ops.workers.dev/mcp	streamable-http	answering	106 ms	3 min ago

Alternatives to StatementKit - bank statement normalizer

same job, measured the same way

MainBook Bank Statement Converter

by mainbook

Convert PDF bank statements to checked Excel, CSV or JSON with balance validation.

172 installs/wk 4 tools answering

Bank Statement to CSV (Tanod)

by tanod

Bank statement PDFs become CSV or JSON transactions with dates, amounts and balances.

1 tools answering

PDF Extract MCP

by diyaluo

Digital PDF invoices/bank statements to CSV, JSON or Excel with automatic PII redaction.

local only

BankConv

by wassim

Convert PDF bank statements into transactions, CSV, OFX, QFX, QBO or Xero CSV.

8 installs/wk local only

StatementSure

by statementsure

Bank statement PDFs to verified QuickBooks, Xero, OFX, CSV and Excel files. Runs locally.

20 installs/wk local only

Advanced Excel

by antonio-castellon

Normalize messy lab Excel and CSV exports into structured tables.

451 installs/wk local only

PivotBank

by pivotbank

Convert bank statement PDFs to Excel, CSV, OFX or QBO, every row checked against the balances.

4 tools answering

PDF & Office Tools (Tanod)

by tanod

Bank statement PDF to CSV, OCR, Office to PDF, PDF to Word, any file to Markdown, merge and split.

40 tools answering

StatementKit - bank statement normalizer — questions

Answers built from our own checks of this server.

What can StatementKit - bank statement normalizer do?

It exposes 5 tools, read directly from the server on our last check. Among them: analyze_statement, convert_statement, list_formats, parse_statement, parse_statement_demo. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is StatementKit - bank statement normalizer working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 137 ms. The bar chart above shows every period we have measured.

How do I connect StatementKit - bank statement normalizer?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does StatementKit - bank statement normalizer need an API key?

No. StatementKit - bank statement normalizer completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is StatementKit - bank statement normalizer?

It answers our handshake in 137 ms on average, which is faster than 90% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.