
Pain001 Mcp
io.github.sebastienrousseauPublished by GitHub account sebastienrousseauv0.0.78Updated Nov 7, 2026
ISO 20022 payment files for agents: generate, validate, and convert pain.001, pain.008, MT101.
Overview
Generates, validates and converts ISO 20022 payment files (pain.001, pain.008, MT101) as MCP tools for an AI assistant.
- What you can do
- Validate and generate ISO 20022 payment XML files
- Inspect and work with payment identifiers and migrate between formats
- Parse bank reports and access a corpus of payment data
- Suggest review-only record fixes, refusing to guess financial fields
- List and project unreleased faces (unreleased tools)
- When to use it
- Useful when an assistant needs to draft, check or convert ISO 20022 credit transfer and direct debit files, or inspect bank report data, during payment-file development or testing.
- Requirements
- Local Python package (pain001-mcp) requiring Python 3.11 or newer; stdio is the default transport, with optional HTTP/SSE transports configured via command-line options. No accounts, keys or environment variables are declared.
Installation
In SourceWeft
- Open Pain001 Mcp in the dashboard and add it to a workspace.
- 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
pain001-mcp
Expose pain001 validation, generation and inspection as MCP tools.
[Build] [Registry] [Docs] [OpenSSF Scorecard] [License: Apache-2.0 OR MIT] [Python 3.11 or newer]
Contents
Getting started
- Install — PyPI and source
- Requirements — toolchain floor, platforms
- Quick Start — use the installed companion
The pain001-mcp ecosystem
- The pain001-mcp ecosystem — core and this companion
Library reference
- Capabilities at a glance — the current surface by theme
- Ecosystem comparison — short matrix; full table at
docs/COMPARISON.md - Benchmarks — headline numbers; full table at
docs/BENCHMARKS.md - Features — module-level capability list
- Configuration — core options
- Examples — runnable example index
Operational
- When not to use pain001-mcp — limitations
- Development — make targets, fuzzing, CI
- Security — guarantees and compliance
- Documentation — all reference docs
- Stability guarantees — SemVer axis, output stability, minimum toolchain discipline
- License
Install
As a Python library
Published packages and development branches are distinct. Test unreleased
changes on this companion's feat/v<next-version> branch against the matching core
branch. No PyPI release or version bump is part of this work.
Requirements
Python 3.11 or newer. CI tests 3.11–3.14 on Linux. See toolchain policy; no distro-system-Python claim is made.
Quick Start
The second command starts the stdio MCP server and waits for a client.
Configure your client to launch pain001-mcp. Use generated help for optional
HTTP/SSE transports; secure network access before exposing any listener.
The pain001-mcp ecosystem
This independently installed companion delegates payment behavior to core. Coordinated versioning does not imply branch changes have been released.
Capabilities at a glance
Ecosystem comparison
This matrix describes the repository's scope, not an independently benchmarked comparison with competitors.
See docs/COMPARISON.md for the evidence and complete matrix.
Benchmarks
CI smoke-runs benchmarks. No hardware-independent throughput or latency promise is made; use the generated run report for measurements.
See docs/BENCHMARKS.md for methodology and full results.
Features
The authoritative tool catalogue is generated from the server.
It covers validation, identifiers, generation, migration, bank-report parsing,
corpus access, review-only record fixes (suggest_record_fix) and the unreleased
faces (list_faces, project_face). Suggestions require review; financial
fields are refused, never guessed. Test unreleased tools with the matching core
feature branch. In-tree core MCP is a separate smaller surface.
Configuration
Run pain001-mcp --help for transport, host and port options. Stdio is default.
See the tool catalogue for request shapes rather than a copied
tool count.
Examples
Run the self-checking scripts under examples/. Tests cover valid and malformed inputs and integration with the core contract.
When not to use pain001-mcp
Not a bank, settlement engine or autonomous payment approver. Review outputs before use. Transport support is not bank certification.
Development
Coverage is gated at 100% line and branch. See CONTRIBUTING.md
and DEVELOPMENT.md. README is generated from the canonical
layout and docs/readme-values.json; CI rejects drift.
Security
Treat requests as untrusted. Protect HTTP listeners and avoid real secrets in logs. Tools may read authorized input paths. Corrections never patch IBANs, BICs, amounts or currencies.
Report vulnerabilities according to SECURITY.md.
Documentation
What is pain.001? · User manual · API reference · Developer guide · Family map
Stability guarantees
Versions advance in coordinated 0.0.1 steps with core. The maintainer opens
releases; this branch does not bump versions. Contract and output changes need
compatibility review. No stronger platform or stability guarantee is implied.
MCP Registry
mcp-name: io.github.sebastienrousseau/pain001-mcp
License
Dual-licensed under Apache-2.0 OR MIT, at your option. See LICENSE. Dependencies retain their own licences.
Source: README.md at commit 31889fa
Tools
0Version history
6- v0.0.78LatestNov 7, 2026
- v0.0.75Oct 29, 2026
- v0.0.74Oct 23, 2026
- v0.0.73Oct 4, 2026
- v0.0.72Sep 29, 2026
- v0.0.70Sep 16, 2026
Score
50% 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