Every server speaks the same contract: JSON records in, validated JSON or XSD-checked XML out, with an {"error": …} payload rather than an exception when something is wrong. Below is what each exposes. New to the suite? Start with the quickstart.
iso20022-mcp · THE GATEWAY
One surface, all families.
search(query)— find message types and suite servers by use-case ("cancel a payment").list_families()·list_servers()— the families and the full suite map, with install status.describe(message_type)— required fields + input schema for a type.validate(message_type, records)·generate(message_type, records)·parse(message_type, xml)— routed to the family's backing server; camt.056/camt.029 route to camt-exceptions.
pain001-mcp · INITIATE
Customer credit transfers.
list_message_types·get_required_fields·get_input_schema— discover pain.001 shapes.validate_records·validate_identifier·validate_xml_against_schema·validate_payment_scheme— pre-flight checks (IBAN/BIC, XSD, SEPA/CBPR rulebooks).generate_message·generate_message_from_file·build_payment_batch— produce validated pain.001.migrate_records·sanitize_to_iso·convert_mt— cross-version migration, charset sanitisation, MT101 → pain.001.
pacs008-mcp · SETTLE
FI-to-FI transfers, returns, status.
list_message_types·list_schemes·get_scheme·get_required_fields·get_input_schema— pacs.008/.004/.002 discovery.validate_records·validate_scheme·validate_xml·generate_message·parse_message— the generate/validate/parse core.convert_mt103— legacy MT103 → pacs.008.classify_address·validate_address·repair_address·validate_addresses— the November 2026 structured-address cliff toolkit.
camt053-mcp · READ STATEMENTS
Bank-to-customer statements.
list_message_types·get_required_fields·get_input_schema·validate_records·validate_statement— camt.053/052 discovery + validation.parse_statement·list_entries·filter_entries— parse and query booked entries.convert_mt940·convert_mt942— legacy MT94x → camt.list_return_reasons·generate_reversal·check_cbpr_readiness— reason-code lookup, reversing entries, Nov-2026 CBPR+ readiness.
reconcile-mcp · RECONCILE
Statements against expected payments.
reconcile(expected, observed, options)— exact, short/over, one-to-many and many-to-one matching with an explainable score and reasons.explain_match(expected, observed)— the per-signal breakdown for a single pair (a tuning aid).normalize_pain001(document)·normalize_camt053(document)— adapt parsed output into canonical records.list_sandbox_scenarios·load_sandbox_scenario·run_sandbox_scenario— deterministic test-mode; try it with zero real data.
camt-exceptions · RESOLVE
Cancellation & investigation.
list_message_types·get_required_fields— supported E&I types (camt.056, camt.029) and their fields.generate_message(message_type, record)— a validated E&I message, checked against the bundled official XSD before it is returned.validate_xml(message_type, xml)— validate raw XML against the message's XSD.
ap2-iso20022 · BRIDGE
Agent mandate → bank rail.
normalize_ap2(payload)·normalize_x402(payload)— a Google AP2 or Coinbase x402 mandate into a canonical mandate.check_mandate(mandate, as_of)— guardrails: required fields, spending cap, expiry, authorisation proof.to_pain001(mandate)·to_pacs008(mandate)— records that feed pain001 / pacs008 for wire-valid XML. Never moves money.
acmt001-mcp · ACCOUNTS
Account management.
list_message_types·get_required_fields·get_input_schema·validate_records·validate_identifier·generate_message— open, maintain and verify accounts (acmt.001), validated against the bundled schema.
CONSISTENT ACROSS ALL EIGHT SERVERS
Same contract, every server.
JSON in; validated JSON or XSD-checked XML out; a structured error rather than an exception. Read-only, idempotent, closed-world hints so your client can reason about safety.