pain001-mcp
The pain001-mcp server exposes the pain001 ISO 20022 payment library as MCP tools, enabling AI agents to generate, validate, parse, and manage ISO 20022 payment messages across 16 tools.
Message Discovery & Schema Inspection
list_message_types— List all supported ISO 20022 pain message types (e.g.,pain.001.001.09)get_required_fields— Retrieve required input field names for a specific message typeget_input_schema— Fetch the full JSON Schema for a message type's flat input recordinspect_template— Inspect the CSV column layout for a given message typelist_supported_formats— List supported input formats (CSV, SQLite, JSON, JSONL, Parquet)
Payment Message Generation
generate_message— Generate a validated ISO 20022 pain XML message from flat recordsgenerate_message_async— Async variant for large batches, running in a worker threadgenerate_message_from_file— Generate a pain XML message by loading records directly from a CSV file
Validation
validate_records— Validate flat payment records against a message type's input JSON Schemavalidate_identifier— Validate financial identifiers (IBAN via mod-97, or BIC)validate_xml_against_schema— Validate raw XML against its bundled XSD without writing to diskvalidate_payment_scheme— Validate records against a payment scheme rulebook (SEPA SCT, SEPA SDD, SEPA Instant, cross-border CT)
Parsing Bank Messages
parse_camt053— Parse a camt.053 bank statement XML into structured data (with optional XSD validation)parse_pain002— Parse a pain.002 payment-status report XML into structured data (with optional XSD validation)
Data Migration & Transformation
migrate_records— Migrate flat payment records between pain.001 schema versions (e.g.,pain.001.001.03→pain.001.001.09), with a summary of renamed, derived, or dropped fieldssanitize_to_iso20022_charset— Transliterate free-text fields to the ISO 20022 Latin character set (e.g.,é→e)
Generates and validates SEPA payment initiation messages (pain.001 for credit transfers, pain.008 for direct debits) and applies scheme rulebooks (SEPA SCT, SDD, INST, B2B) via dedicated tools.
Click on "Install 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., "@pain001-mcpGenerate a credit transfer XML for EUR 1000 to DE89370400440532013000"
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.
Contents
Getting started
What is pain001-mcp? — the problem it solves
Install — PyPI, virtualenv, Docker
Quick start — register with Claude Desktop in 30 seconds
Library reference
Tools — the 17 tools, one resource, one prompt
Using the tools — call them in-process from Python
The pain001 suite — core lib, MCP server, LSP server
Operational
When not to use pain001-mcp — honest boundaries
Development — gates, make targets
Security — sandboxing posture
Documentation — examples, guides
Contributing — how to get changes in
License — Apache-2.0
Related MCP server: Pactus
What is pain001-mcp?
The Model Context Protocol (MCP) is
an open standard that lets AI agents discover and call external tools in
a uniform way. pain001-mcp is the MCP server that turns the
pain001 ISO 20022
payment library into 16 first-class agent tools — so an assistant can
generate and validate pain.001 Customer Credit Transfer Initiation
and pain.008 Customer Direct Debit Initiation messages (the
standardised payment instructions behind SEPA and cross-border credit
transfers) directly from a conversation.
Every tool is a thin, typed wrapper over the pain001 public API
(validators, schema loaders, generate_xml_string, parsers, the version
mapper, the ISO 20022 charset sanitiser), so all interfaces behave
identically to the CLI, REST API, and in-tree MCP server. Tools return
JSON-serialisable data; on a validation error they return an
{"error": ...} payload rather than raising.
Concern | How pain001-mcp handles it |
Transport | stdio (FastMCP default); zero config beyond the client manifest |
Schema fidelity | Tools delegate to |
Identifier validation |
|
Cross-version mapping |
|
Charset compliance |
|
Error surface | Validation failures return structured |
Install
Channel | Command | Notes |
PyPI |
| Pulls in |
Source |
| For development |
Docker (GHCR) |
| Multi-arch (linux/amd64, linux/arm64); runs |
Requires Python 3.10 or later. Works on macOS, Linux, and Windows.
python -m venv venv
source venv/bin/activate # macOS/Linux
venv\Scripts\activate # Windows
python -m pip install -U pain001-mcpQuick start
Register the server with any MCP client (Claude Desktop shown):
{
"mcpServers": {
"pain001": { "command": "pain001-mcp" }
}
}That's it. Restart the client and the 17 tools are available to the agent. To check the server starts cleanly before wiring an editor:
pain001-mcp --help
# -> usage: pain001-mcp [-h] ...The server speaks LSP-style JSON-RPC over stdin/stdout — it is meant to be launched by an MCP client, not used interactively.
Tools
All 17 tools delegate to the pain001 public API, so they behave
identically to the CLI and REST API.
Tool | Purpose |
| List the supported |
| Required input fields for a message type |
| Full input JSON Schema for a message type |
| Template metadata + accepted formats for a message type |
| Validate flat records against a message type |
| Same as above, JSON-RPC-friendly signature |
| Run a scheme rulebook ( |
| Validate an IBAN or BIC |
| Validate an XML payload against its bundled XSD without writing to disk |
| Generate a payment XML file from records + a path |
| Generate a validated XML message and return the string |
| Async variant of |
| Render directly from a CSV path on disk |
| List the data formats |
| Parse a |
| Parse a |
| Migrate flat records between pain.001 schema versions |
| Transliterate text to the ISO 20022 Latin set |
| Convert a legacy SWIFT MT101 (Request for Transfer) into pain.001 records (one per transaction) |
Plus one resource and one prompt:
Kind | Name | Purpose |
Resource |
| Read-only access to the bundled XSD for any supported message type |
Prompt |
| Guided multi-step prompt that walks an agent through building a valid batch |
Using the tools
You can invoke the tools in-process — without a transport — straight through the FastMCP instance. This mirrors what an agent receives over stdio:
import asyncio
from pain001_mcp.server import server
# A single flat payment record satisfying pain.001.001.09.
record = [
{
"id": "MSG-0001",
"date": "2026-01-15T10:30:00",
"nb_of_txs": 1,
"ctrl_sum": 100.00,
"initiator_name": "Acme Embedded Finance Ltd",
"payment_information_id": "PMT-INFO-0001",
"payment_method": "TRF",
"batch_booking": False,
"service_level_code": "SEPA",
"requested_execution_date": "2026-01-20",
"debtor_name": "Acme Embedded Finance Ltd",
"debtor_account_IBAN": "DE89370400440532013000",
"debtor_agent_BIC": "DEUTDEFFXXX",
"charge_bearer": "SLEV",
"payment_id": "PAY-0001",
"payment_amount": 100.00,
"currency": "EUR",
"creditor_agent_BIC": "NWBKGB2LXXX",
"creditor_name": "National Westminster Bank",
"creditor_account_IBAN": "GB29NWBK60161331926819",
"remittance_information": "Invoice 0001",
}
]
async def main() -> None:
async def call(name, args):
result = await server.call_tool(name, args)
content = result[0] if isinstance(result, tuple) else result
return content[0].text if content else ""
# 1. Validate an identifier.
print(await call("validate_identifier",
{"kind": "iban", "value": "DE89370400440532013000"}))
# -> {"kind": "iban", "value": "DE89370400440532013000", "valid": true}
# 2. Sanitise text to the ISO 20022 Latin set.
print(await call("sanitize_to_iso20022_charset",
{"value": "Café Müller"}))
# -> {"value": "Café Müller", "sanitised": "Cafe Muller",
# "was_valid": false, "changed": true}
# 3. Generate a validated Customer Credit Transfer Initiation.
xml = await call("generate_message",
{"message_type": "pain.001.001.09", "records": record})
print(xml[:46])
# -> <?xml version="1.0" encoding="UTF-8"?>
# <Document ...
asyncio.run(main())The runnable version of this snippet lives in
examples/01_mcp_tools.py. See the
examples/ folder for a validation pipeline
(02_validate_pipeline.py) and a
bank-reply parser walkthrough
(03_parse_bank_replies.py).
The pain001 suite
pain001-mcp is part of a set of independently installable packages
built around the pain001
library — pick whichever ones your stack needs:
Package | Role |
Core library + CLI + FastAPI REST API | |
MCP server for AI agents (this package) | |
Language Server Protocol server for editors |
flowchart LR
A["MCP client<br/>(Claude Desktop, IDE, agent)"] -->|stdio| B["pain001-mcp"]
B -->|delegates to| C["pain001"]
C -->|render + validate| D["ISO 20022 pain.001 XML"]When not to use pain001-mcp
You're not driving an MCP-aware agent. Use the CLI (
pain001 …) or the REST API (pain001 serve) directly — both expose the same surface with less indirection.You need editor diagnostics, not agent tools. Use
pain001-lsp— it speaks the Language Server Protocol to VS Code, Neovim, Helix, Emacs, etc.You need to extend the tool surface in-tree. The companion
pain001[mcp]extra exposes the same FastMCP instance and is easier to fork inside an organisation's pain001 install.
Development
pain001-mcp uses Poetry and
mise.
git clone https://github.com/sebastienrousseau/pain001-mcp.git
cd pain001-mcp
mise install
poetry installA Makefile orchestrates the quality gates (kept in lockstep with CI):
Target | What it runs |
| All gates (REQUIRED before commit) |
|
|
|
|
|
|
|
|
Current state (v0.0.54): 54 tests passing, 100% line + branch
coverage against a 100% enforced floor, mypy --strict clean,
interrogate 100%.
Security
No filesystem writes from tools.
generate_messagereturns the XML as a string; onlygenerate_payment_filewrites, and only to a caller-supplied path.XML parsing of
camt.053andpain.002is routed throughdefusedxml(via the corepain001library); XXE and entity expansion are rejected.Validation failures are returned as structured
{"error": ...}payloads — never as stack traces — so the agent never sees an internal path leak.Dependencies are pinned via
poetry.lockand audited bypip-auditand Bandit in CI.
To report a vulnerability, please use GitHub private vulnerability reporting rather than a public issue.
Documentation
Runnable examples:
examples/Release history: CHANGELOG.md
Core library docs: docs.pain001.com
MCP specification: modelcontextprotocol.io
Contributing
Contributions are welcome — see the
contributing instructions.
Thanks to all the
contributors
who have helped build pain001-mcp.
Related MCP Servers
Part of the ISO 20022 MCP Suite — open-source, Apache-2.0 licensed MCP servers for banking and financial-services AI agents:
Server | Purpose |
Generate, validate, parse & scheme-check ISO 20022 pacs.008 FI-to-FI credit transfers + Nov-2026 address linting | |
Parse & reconcile ISO 20022 camt.053 bank-to-customer statements — CBPR+/HVPS+ ready | |
Generate & validate ISO 20022 acmt account-management messages | |
Parse bank statements (BAI2, MT940/MT942, CAMT.053, OFX, CSV) into structured transactions | |
Lossless YAML 1.2 parsing, formatting & validation (Rust, 100% spec compliance) |
MCP Registry
mcp-name: io.github.sebastienrousseau/pain001-mcp
License
Licensed under the Apache License, Version 2.0. Any contribution submitted for inclusion shall be licensed as above, without additional terms.
Maintenance
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/sebastienrousseau/pain001-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server