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)→ structuredpacs.008records. - Validate.
validate_records("pacs.008.001.08", records)andvalidate_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 isstructured,hybrid,unstructuredormixed_invalid. - Repair & validate.
repair_address(address)extractsTwnNm(town name),Ctry(ISO country code) andPstCdfrom free-text lines into compliant structured or hybrid form, thenvalidate_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)andnormalize_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-textMT199/MT292messages. - Resolve. When the response comes back,
generate_message("camt.029", record)with a confirmation code (e.g.CNCLcancelled,RJCRrejected) → 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 vianormalize_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)→ apain.001record; hand it topain001-mcp · generate_messagefor 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.