Iso20022 Bridge Mcp

io.github.CSOAI-ORGPublished by GitHub account CSOAI-ORGv0.1.2Updated Oct 30, 2026

ISO 20022 / SWIFT finance bridge — parse, validate, modernise, govern (DORA/NIS2/AML).

VerifiedSTDIODesktop onlyFinanceSecurity & Monitoring

Overview

AI-generated overview

Local MCP server that parses, validates, modernises and governance-checks ISO 20022 and SWIFT MT payment messages.

What you can do
  • Parse ISO 20022 XML messages to extract message type and key payment fields such as amount, currency, parties, agents and end-to-end ID
  • Validate messages for well-formedness and required fields
  • Map messages to flat modern JSON for downstream systems
  • Run payment governance checks covering AML and sanctions surface, large-value thresholds and DORA, NIS2, FATF, PSD2 and ISO 20022 frameworks, with results attestable on the CSOAI ledger
When to use it
Useful when an assistant has to inspect, check or convert ISO 20022 pacs, pain or camt messages and SWIFT MT payment data, or when a payment needs a compliance-style review before being handed to another system.
Requirements
Runs as a local stdio process on the user's machine, installed from the PyPI package iso20022-bridge-mcp and started with Python. No authentication, environment variables or headers are declared. Desktop only; not executable in a web context.
Before you install
Payment messages carry sensitive financial and party data, and governance results are described as attestable on the CSOAI ledger, so consider what leaves your machine. The manifest declares no credentials, but review the package before running it locally. Treat validation and AML/sanctions output as advisory, not a compliance determination.

Installation

In SourceWeft

  1. Open Iso20022 Bridge Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

ISO 20022 / SWIFT Bridge MCP

mcp-name: io.github.CSOAI-ORG/iso20022-bridge-mcp

Part of the CSOAI Layer-0 legacy-bridge family (sibling of cobol-bridge-mcp). Bridges the financial-messaging legacy world — ISO 20022 (pacs/pain/camt) and SWIFT MT — to ONE OS / CSOAI, and governs every payment.

Tools

  • parse_iso20022(xml) — message type + key payment fields (amount, currency, debtor/creditor, agents, EndToEndId).
  • validate_iso20022(xml) — well-formedness + required-field checks.
  • map_to_modern(xml) — flat modern JSON for downstream systems.
  • govern_payment(xml) — AML/sanctions surface, large-value thresholds, frameworks (ISO 20022 · DORA · NIS2 · FATF · PSD2); attestable on the CSOAI ledger.

Run

bash
pip install -e .python server.py        # stdio MCP server

The win: legacy payment message → CSOAI governance/attestation → ONE OS, without disruption. Pairs with dora-compliance-mcp + dora-nis2-crosswalk-mcp.

Source: README.md at commit 088eb23

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.