Pactus
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Pactus Parse this pacs.008 XML message for me."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Pactus
Pactus is an MCP server for parsing and validating ISO 20022 payment messages directly from chat. It exposes nine tools that let AI assistants inspect or validate pacs.008, pacs.002, pain.001, and camt.053 messages — the message types at the centre of the CBPR+ migration — without leaving the conversation. It is aimed at developers and bank-integration teams who need to read, debug, or explain ISO 20022 traffic during the transition away from MT messages.
Status
pip install pactus-mcp
# or
uv add pactus-mcpRelated MCP server: pain001-mcp
Quick start
git clone https://github.com/deniskarlinsky/iso20022-mcp
cd iso20022-mcp
uv sync
uv run pytestConnecting to Claude Desktop
Install via uvx for zero-setup use, or run from a local checkout for development.
Add Pactus to your Claude Desktop config:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.jsonLinux:
~/.config/Claude/claude_desktop_config.json
From PyPI (recommended)
{
"mcpServers": {
"pactus": {
"command": "uvx",
"args": ["pactus-mcp"]
}
}
}From a local clone (for development)
{
"mcpServers": {
"pactus": {
"command": "uv",
"args": ["run", "--directory", "/absolute/path/to/iso20022-mcp", "pactus-mcp"]
}
}
}Restart Claude Desktop. The Pactus tools will appear in the tools menu.
Available tools
Tool | Message type | Purpose |
| — | Health check; returns service name and version. |
|
| Parse a FI-to-FI Customer Credit Transfer. |
|
| Parse a FI-to-FI Payment Status Report. |
|
| Parse a Customer Credit Transfer Initiation. |
|
| Parse a Bank-to-Customer Account Statement. |
|
| Validate a FI-to-FI Customer Credit Transfer against its XSD. |
|
| Validate a FI-to-FI Payment Status Report against its XSD. |
|
| Validate a Customer Credit Transfer Initiation against its XSD. |
|
| Validate a Bank-to-Customer Account Statement against its XSD. |
The four parse tools return a structured Pydantic model on success, or {"error": "..."} on failure. The four validate tools return a ValidationReport listing every XSD violation with line, column, and path information — even when there are multiple errors. All tools never raise; the agent can explain what went wrong.
Tool reference
parse_pacs008
pacs.008 is the primary interbank credit transfer message and the mandatory format for all CBPR+ cross-border traffic from November 2025. It carries one or more credit transfer instructions between financial institutions, each with settlement amount, charge bearer, debtor, and creditor agents.
{
"group_header": {
"message_id": "MSG20240508001",
"creation_datetime": "2024-05-08T10:00:00",
"number_of_transactions": 1,
"settlement_method": "CLRG"
},
"transactions": [
{
"end_to_end_id": "E2E20240508001",
"transaction_id": "TX20240508001",
"settlement_amount": {"value": "1000.00", "currency": "USD"},
"charge_bearer": "SHAR",
"debtor": {"name": "Acme Corporation"},
"debtor_agent": {"bic": "CHASUS33"},
"creditor": {"name": "Global Supplies Ltd"},
"creditor_agent": {"bic": "DEUTDEDB"}
}
]
}parse_pacs002
pacs.002 is the status report sent in response to a pacs.008. It reports whether each transaction was accepted, rejected, or is in an intermediate state. Rejections carry one or more structured reason codes (e.g. AC01 incorrect account, AG01 transaction forbidden) that explain the outcome.
{
"group_header": {
"message_id": "STS20260510001",
"creation_datetime": "2026-05-10T14:30:00"
},
"original_group_info": {
"original_message_id": "MSG20240508001",
"original_message_name_id": "pacs.008.001.08",
"original_creation_datetime": "2024-05-08T10:00:00",
"group_status": "ACSC"
},
"transaction_statuses": [
{
"original_end_to_end_id": "E2E-001",
"original_transaction_id": "TX-001",
"status": "ACSC",
"status_reasons": [],
"acceptance_datetime": "2026-05-10T14:29:45"
}
]
}parse_pain001
pain.001 is the initiating message in a credit transfer flow, sent by a corporate or customer to their bank. It groups transactions into one or more PaymentInformation batches that share a debtor account, execution date, and service level. The LLM sees the full hierarchy: group header → batches → transactions.
{
"group_header": {
"message_id": "PAIN20260510-001",
"creation_datetime": "2026-05-10T09:00:00",
"number_of_transactions": 1,
"control_sum": "1500.00",
"initiating_party_name": "ACME Corp"
},
"payment_informations": [
{
"payment_information_id": "BATCH-2026-05-10-A",
"payment_method": "TRF",
"requested_execution_date": "2026-05-12",
"debtor": {"name": "ACME Corp"},
"debtor_account_iban": "DE89370400440532013000",
"debtor_agent": {"bic": "DEUTDEFFXXX"},
"charge_bearer": "SLEV",
"service_level_code": "SEPA",
"transactions": [
{
"end_to_end_id": "E2E-PAIN-001",
"amount": {"value": "1500.00", "currency": "EUR"},
"creditor": {"name": "Acme Supplier SARL"},
"creditor_account_iban": "FR1420041010050500013M02606",
"remittance_info": ["Invoice 2026-0042"]
}
]
}
]
}parse_camt053
camt.053 is the structured account statement sent by a bank to its customer. It reports opening and closing balances and individual debit/credit entries for a period, each optionally broken down to individual transaction details. It is the primary source for automated bank reconciliation.
{
"group_header": {
"message_id": "CAMT053-SINGLE-001",
"creation_datetime": "2026-05-10T08:00:00"
},
"statements": [
{
"statement_id": "STMT-2026-05-09-001",
"account_iban": "DE89370400440532013000",
"account_currency": "EUR",
"balances": [
{
"type_code": "OPBD",
"amount": {"value": "10000.00", "currency": "EUR"},
"credit_debit": "CRDT",
"balance_date": "2026-05-09"
}
],
"entries": [
{
"entry_ref": "NTRY-001",
"amount": {"value": "1500.00", "currency": "EUR"},
"credit_debit": "DBIT",
"status": "BOOK",
"booking_date": "2026-05-09",
"bank_tx_domain": "PMNT",
"bank_tx_family": "ICDT",
"bank_tx_subfamily": "ESCT"
}
]
}
]
}validate_pacs008
Validates a pacs.008.001.08 message against its XSD and returns every violation in one pass. Use this when you need to know all the errors in a message rather than just the first one the parser encounters.
{
"valid": false,
"schema_id": "pacs.008.001.08",
"violations": [
{
"line": 5,
"column": 3,
"path": "/{urn:iso:std:iso:20022:tech:xsd:pacs.008.001.08}Document/{urn:...}FIToFICstmrCdtTrf",
"message": "Element '{urn:...}WrongElement': This element is not expected.",
"domain": "SCHEMASV",
"type_name": "SCHEMAV_CVC_COMPLEX_TYPE_2_4",
"level": "ERROR"
}
]
}validate_pacs002
Validates a pacs.002.001.10 message against its XSD and returns every violation in one pass.
validate_pain001
Validates a pain.001.001.09 message against its XSD and returns every violation in one pass.
validate_camt053
Validates a camt.053.001.08 message against its XSD and returns every violation in one pass.
Security model
XXE and entity-expansion hardening: All parse and validate tools reject input containing
<!DOCTYPE>or<!ENTITY>declarations before any XML parsing occurs. This blocks XXE file-read, SSRF, and billion-laughs DoS patterns.Build integrity: Generated xsdata models are SHA-256 verified in CI on every commit (
sha256sum -c GENERATED_HASHES.txt). Regeneration is reproducible from the vendored XSDs.Supply chain: GitHub Actions workflows use SHA-pinned action references (commit-hash
@pins, not mutable tags).Distribution integrity: PyPI artifacts are published via OIDC Trusted Publishing and signed with Sigstore. SBOMs (CycloneDX and SPDX) are generated and vulnerability-scanned on every CI run; release artifacts include the SBOM.
Vulnerability disclosure: See SECURITY.md.
Architecture
Pactus uses a hexagonal layout: pactus/core/ is pure business logic with no MCP awareness, mcp_server.py is a thin FastMCP wrapper, and the generated xsdata models live in pactus/generated/ and never escape parsers.py. See architecture.md for the diagram.
Development
uv run ruff check
uv run ruff format
uv run mypy
uv run pytestThe project targets mypy --strict.
License
MIT
Available Tools
9 toolsparse_camt053A
Parse a camt.053.001.08 Bank-to-Customer Cash Management Statement.
camt.053 is the structured account statement sent by a bank to its customer. It reports balances (opening, closing, interim) and individual debit/credit entries for a period, each optionally broken down to individual transaction details. It is the primary source for automated bank reconciliation.
Returns a structured ParsedCamt053 on success, or {"error": "..."} on failure.
Inputs: xml (required). Returns: result
parse_pacs002A
Parse a pacs.002.001.10 (FI-to-FI Payment Status Report) message.
pacs.002 is the response to a pacs.008 credit transfer. It reports whether each transaction was accepted, rejected, or is in an intermediate state. Each transaction carries a status code and optionally one or more structured reason codes explaining the outcome.
Returns a structured ParsedPacs002 on success, or {"error": "..."} on failure.
Inputs: xml (required). Returns: result
parse_pacs008A
Parse a pacs.008.001.08 (FI-to-FI Customer Credit Transfer) message.
pacs.008 is the most common ISO 20022 message in cross-border payments and is required for all SWIFT cross-border traffic from November 2025. Each message carries one or more credit transfer instructions between financial institutions.
Returns a structured ParsedPacs008 with the group header (message-level metadata) and a list of transactions (each instruction). On parse or validation failure, returns {"error": "..."} so the agent can explain rather than crashing.
Inputs: xml (required). Returns: result
parse_pain001A
Parse a pain.001.001.09 Customer Credit Transfer Initiation message.
pain.001 is the initiating message in a credit transfer flow, sent by a corporate or customer to their bank. It carries one or more payment batches (PaymentInformation), each grouping transactions that share a debtor account, execution date, and service level.
Returns a structured ParsedPain001 on success, or {"error": "..."} on failure.
Inputs: xml (required). Returns: result
pingB
Health check tool. Returns service metadata.
Inputs: no named parameters. Returns: object
validate_camt053A
Validate a camt.053.001.08 message against its XSD.
Returns a structured ValidationReport listing every XSD violation found, with line/column/path information. Unlike parse_camt053, this does not stop at the first error — all violations are reported so the user can fix them in one pass.
Inputs: xml (required). Returns: result
validate_pacs002A
Validate a pacs.002.001.10 message against its XSD.
Returns a structured ValidationReport listing every XSD violation found, with line/column/path information. Unlike parse_pacs002, this does not stop at the first error — all violations are reported so the user can fix them in one pass.
Inputs: xml (required). Returns: result
validate_pacs008A
Validate a pacs.008.001.08 message against its XSD.
Returns a structured ValidationReport listing every XSD violation found, with line/column/path information. Unlike parse_pacs008, this does not stop at the first error — all violations are reported so the user can fix them in one pass.
Inputs: xml (required). Returns: result
validate_pain001A
Validate a pain.001.001.09 message against its XSD.
Returns a structured ValidationReport listing every XSD violation found, with line/column/path information. Unlike parse_pain001, this does not stop at the first error — all violations are reported so the user can fix them in one pass.
Inputs: xml (required). Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
Each tool targets a specific ISO 20022 message type and action (parse vs validate), with no overlap. The ping tool is uniquely for health checks.
All tools follow a consistent verb_messageType pattern (e.g., parse_pacs008, validate_pacs002). The naming is uniform and predictable.
9 tools cover the essential operations (parse and validate) for four common payment message types. The count is well-scoped for this domain.
The server covers the core parse and validate needs for the most frequent ISO 20022 payment messages. A minor gap is the absence of related messages like camt054 or pacs004, but the current set is sufficient for typical use.
Maintenance
Related MCP Connectors
Remote MCP server for UETR tracking and SWIFT payment tracking. Read bank-reported transfer status and manage monitoring from your AI app, within your uetr.ai plan and team rights. Connect at https://uetr.ai/mcp with OAuth or an API key. A free uetr.ai account is enough to connect. uetr.ai is an independent information service and does not move or hold funds.
Cross-border payment & banking intelligence for AI agents: SWIFT/BIC, IBAN, sanctions, FX, tracking.
MCP server for Modern Treasury — payment orders, transactions, counterparties and ledgers.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Related MCP Servers
- AlicenseAqualityBmaintenanceMCP server that enables AI agents to parse, validate, and reverse ISO 20022 bank statements, with tools for discovering message types and return reasons.2470 PyPI2Apache 2.0
- AlicenseAqualityBmaintenanceA Model Context Protocol server that exposes the pain001 ISO 20022 Customer Credit Transfer Initiation library as agent tools, enabling AI assistants to generate and validate standardized payment XML messages.30953 PyPI1Apache 2.0
- AlicenseAqualityBmaintenanceAn MCP server that exposes the pacs008 ISO 20022 FI-to-FI Customer Credit Transfer library as tools for AI agents and assistants, enabling generation, validation, and parsing of pacs.008 credit transfer XML messages.1649 PyPI1Apache 2.0
- AlicenseAqualityDmaintenanceAn MCP server that provides AI agents with tools to validate SWIFT MT and ISO 20022 MX payment messages, check BIC/IBAN correctness, and convert between MT and MX formats.76 npmMIT