Sebastien Rousseau
Aerial view of illuminated financial district at night

ISO 20022 MCP Suite: recipes.

Five end-to-end flows an agent runs entirely through the suite: from a legacy MT103 to a validated wire, from a bank statement to a reconciled ledger.

Five flows an agent runs end to end, entirely through the published servers. Each is a short chain of tool calls: no glue code, every step validated. New here? Read the quickstart first, or the tool reference.

RECIPE 01 · MIGRATE

A legacy MT103 becomes a validated pacs.008.

  • Convert. pacs008-mcp · convert_mt103(mt_text) → structured pacs.008 records.
  • Validate. validate_records("pacs.008.001.08", records) and validate_payment_scheme("CBPR+", records) → schema + rail checks pass.
  • Generate. generate_message("pacs.008.001.08", records) → XSD-valid XML, ready for the network.

The same shape works for convert_mt101 → pain.001 and convert_mt940/convert_mt942 → camt.053/camt.052. Migrate one message type at a time.

RECIPE 02 · STRUCTURED & HYBRID ADDRESSES

Remediate unstructured postal addresses for the 2026-2027 CBPR+ gates.

  • Classify. pacs008-mcp · classify_address(address) → identifies whether a party address is structured, hybrid, unstructured or mixed_invalid.
  • Repair & validate. repair_address(address) extracts TwnNm (town name), Ctry (ISO country code) and PstCd from free-text lines into compliant structured or hybrid form, then validate_address(repaired, policy="cbpr_2026") confirms compliance.
  • Audit the statement. camt053-mcp · check_cbpr_readiness(xml) → verifies an entire inbound or outbound statement against the November 2026 and November 2027 structured-address rules.

RECIPE 03 · RECONCILE

A statement, matched to what you expected.

  • Normalise both sides. reconcile-mcp · normalize_camt053(statement) and normalize_pain001(payments) → canonical observed + expected records.
  • Match. reconcile(expected, observed) → exact matches, short/over payments (with the delta), split settlements and batch credits, each with a reason.
  • Explain the edge case. explain_match(expected, observed) → the per-signal score for anything that needs a human.

No data yet? run_sandbox_scenario("month_end") reconciles a realistic mixed close in one call.

RECIPE 04 · CANCEL & RESOLVE (2027 E&I)

Recall a duplicate wire, then close the investigation case.

  • Cancel. camt-exceptions · generate_message("camt.056", record) (standalone CLI: uvx --from camt-exceptions camt-exceptions-mcp) with the original payment references and a cancellation reason (e.g. DUPL) → an XSD-valid FI-to-FI Payment Cancellation Request replacing legacy free-text MT199/MT292 messages.
  • Resolve. When the response comes back, generate_message("camt.029", record) with a confirmation code (e.g. CNCL cancelled, RJCR rejected) → the Resolution of Investigation.

RECIPE 05 · BRIDGE AN AGENT PAYMENT

An AP2 or x402 mandate becomes a wire-valid pain.001.

  • Normalise. ap2-iso20022 · normalize_ap2(mandate) (standalone CLI: uvx --from ap2-iso20022 ap2-iso20022-mcp) → a canonical mandate (works for Coinbase x402 too via normalize_x402).
  • Guardrail. check_mandate(mandate, as_of) → required fields present, within the spending cap, not expired, signed. Stop here if it fails.
  • Convert, then generate. to_pain001(mandate) → a pain.001 record; hand it to pain001-mcp · generate_message for wire-valid XML. The bridge never moves money; sending stays a separate, human-guarded step.

ONE SUITE · THE WHOLE LIFECYCLE

Compose your own.

These five chain the servers end to end; the gateway lets an agent discover and run any of them from natural language.

Quickstart · Tool reference · The suite