Eight vendor-neutral MCP servers to generate, validate, reconcile and settle ISO 20022 payments from natural language. Runs anywhere, owned by no bank, installed in one line.
ONE SUITE, THE WHOLE PAYMENT LIFECYCLE
GENERATE & VALIDATE
One gateway routes across the families — pain.001 initiation, pacs.008 transfers, camt.053 statements, acmt.001 account management. An agent asks in plain terms; it gets back XSD-validated XML, with legacy SWIFT MT→MX conversion and the November 2026 structured-address toolkit built in.
RECONCILE & RESOLVE
Did the money arrive, and which invoice does it belong to? reconcile-mcp matches camt.053 statements against expected pain.001 payments — exact, partial, split and batch — with an explainable reason for every match. When a payment goes wrong, camt-exceptions cancels and resolves it, XSD-valid.
BRIDGE AGENT PAYMENTS
Agent-payment protocols authorise a payment; they don't emit the bank message that settles it. ap2-iso20022 turns a signed Google AP2 or Coinbase x402 mandate into a wire-valid pain.001 or pacs.008 — with spending-cap, expiry and authorisation guardrails. It transforms and validates; it never moves money.
THE ISO 20022 MCP SUITE
Vendor-neutral, Python-native, installed in one line — no account to open. Start with the gateway, or install just the server for the job in front of you. Every one is live on PyPI and the official MCP registry, Apache-2.0, at 100% branch-test coverage.
One agent-friendly surface across every family. Seven meta-tools (search, list_families, list_servers, describe, validate, generate, parse) that route to the dedicated servers, so an agent sees a handful of verbs instead of sixty. Light core; families install as extras.
pip install "iso20022-mcp[all]" · Learn more
Customer credit transfer initiation (pain.001), with schema discovery, IBAN/BIC and XSD validation, cross-version migration, and a legacy MT101 → pain.001 converter. The outgoing-payment workhorse.
pip install pain001-mcp · Learn more
FI-to-FI credit transfers (pacs.008), payment returns (pacs.004) and status reports (pacs.002). Includes the November 2026 structured-address cliff toolkit and a legacy MT103 → pacs.008 converter.
pip install pacs008-mcp · Learn more
3Apache-2.0last commit 3w ago
Bank-to-customer statements (camt.053/052): parse entries and balances into structured data, validate, and convert legacy MT94x. The inbound side of the ledger.
pip install camt053-mcp · Learn more
Match camt.053 statement entries against expected pain.001 payments: exact, short/over, one-to-many (split settlement) and many-to-one (batch credit), each with an explainable score and reasons. Ships a sandbox test-mode — try it with zero real data.
pip install reconcile-mcp · Learn more
Exceptions & Investigations, the least-tooled corner of ISO 20022. Generate XSD-valid camt.056 payment cancellation requests (recall a duplicate or erroneous wire) and camt.029 resolution-of-investigation messages.
pip install camt-exceptions · Learn more
Bridge Google AP2 and Coinbase x402 agent-payment mandates into wire-valid pain.001 / pacs.008 records, with spending-cap, expiry and authorisation guardrails. Transforms and validates only — never moves money.
pip install ap2-iso20022 · Learn more
Account management messaging (acmt.001): open, maintain and verify bank accounts from plain data, validated against the bundled schema.
pip install acmt001-mcp · Learn more
Turn bank statements in MT94x, BAI2 and OFX into structured data. Built for messy real-world files and audit requirements — the on-ramp for legacy formats.
pip install bankstatementparser-mcp · Learn more
How do I try it right now?
Run the gateway with no install and no account: uvx --from "iso20022-mcp[all]" iso20022-mcp. Ask it to search "cancel a payment" and it points you at camt.056; ask it to generate and you get XSD-valid XML back. Under sixty seconds from nothing to a validated message.
Which server do I need?
Start with the gateway (iso20022-mcp) and let it route — or install just the one for the job: initiate a payment with pain001-mcp, settle interbank with pacs008-mcp, read statements with camt053-mcp, reconcile with reconcile-mcp, cancel/resolve with camt-exceptions, bridge an agent mandate with ap2-iso20022.
Is it safe to give an agent?
Yes, by design. Every generator validates against the official bundled XSD before returning; the AP2 bridge only transforms and validates and never moves money; and reconcile-mcp is read-only matching. Producing a message is deliberately separate from sending it, so the money-movement step stays a human-guarded action. Apache-2.0, 100% branch-tested.
Why is this different from a banking API?
Banking platforms sell you an account and their rails. This is the vendor-neutral message layer underneath any bank — the ISO 20022 engine, reconciliation and exceptions that every institution still has to build. It runs on your own infrastructure and is tied to no balance sheet.
Does it help with the ISO 20022 migration?
Directly. MT retires between 2025 and 2028, and structured addresses become mandatory in November 2026. The suite ships the MT→MX converters (MT103/MT101/MT94x) and the structured-address classify/validate/repair/batch toolkit, so you can migrate one message at a time.
OPEN SOURCE · APACHE-2.0 · ON PYPI + THE MCP REGISTRY
Eight servers, the whole ISO 20022 payment lifecycle, vendor-neutral and installable in one line. No account to open, no bank to trust — just the message engine everyone else has to build.