Contents
Getting started
- Install — PyPI, source and Docker
- Requirements — toolchain floor, platforms
Power your agent
การติดตั้งจากผู้เผยแพร่ ไม่ใช่เอนด์พอยต์ของ PlugMCP
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
Getting started
Generate and validate ISO 20022 payment files (pain.001 v03-v12, pain.008) from CSV, SQLite, JSON, or Parquet. XSD and SEPA scheme validation, pain.002 and camt.053 parsers and builders, plus a CLI, REST API, MCP server, and LSP server for editor diagnostics. 🐍
The Pain001 ecosystem
Library reference
docs/COMPARISON.mddocs/BENCHMARKS.mdOperational
python -m pip install pain001
Latest release: v0.0.75: ISO 20022 pain.001 and pain.008 files generated from CSV, SQLite, JSON, JSON Lines and Parquet and validated against the official XSD, for Python 3.11+, released with the whole pain001 suite at one version.
Optional extras: api, parquet, redis, mcp, lsp, gpg, otel,
fast (libxml2 validation), upload (SFTP) and rules (CEL policies), for
example python -m pip install "pain001[rules,upload]".
# Development checkout
git clone https://github.com/sebastienrousseau/pain001.git
cd pain001
poetry install --all-extras --with dev,docs
# Published container (CLI and REST API)
docker pull ghcr.io/sebastienrousseau/pain001:latest
Docker runs as a non-root user. Mount a writable directory at /data and use
-w /data; generate -t pain.001.001.03 -d payments.csv -o output writes into
an output directory, not a filename. No distro package or standalone native
binary is claimed; see packaging.
Python 3.11 or newer; CI tests Python 3.11–3.14 on Linux. Development uses Python 3.12 and Poetry. Optional integrations require their extras and, for GPG, the system GnuPG executable. No distro-system-Python compatibility is claimed. See toolchain policy.
pain001 init pain.001.001.03 -o payments.csv
pain001 validate -t pain.001.001.03 -d payments.csv
pain001 generate -t pain.001.001.03 -d payments.csv -o output
Run in a fresh writable directory. The scaffold uses bundled synthetic data; replace it with your own records before a real payment workflow. Generation validates the rendered XML against the bundled XSD before writing it. A dry run checks data but is not a bank acceptance guarantee.
Core, MCP, LSP, XLSX and MT101 packages follow the coordinated version policy;
see suite policy.
The new plugin scaffold and mockbank start separately at unreleased 0.0.1.
Issue acceptance status distinguishes branch work from
released packages. Companion packages are independently installed.
This matrix describes the repository's scope, not an independently benchmarked comparison with competitors.
See docs/COMPARISON.md for the evidence and complete matrix.
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.
generate_xml_string.
Streaming produces one file per chunk with recomputed control totals.pain001 versions and inspect metadata
with pain001 inspect. Inputs, templates and schemas are described in the
user guide and input-column reference.anti-duplicate; see SCHEMES.md.
CEL rules (added in 0.0.71) apply before generation through CLI
and REST. Account currency is never inferred from an IBAN.suggest_record_fix via MCP for review-only corrections. IBANs, BICs,
amounts and currencies are refused, not guessed; see
correction decisions.pain001 serve, MCP with pain001 mcp, or the CSV language server
with pain001-lsp-builtin, after installing the corresponding extras.openapi.json; see the
public API reference.Use pain001 generate --help, pain001 upload --help, and
pain001 plugins --help for the current command options rather than a copied
flag list. YAML, TOML and INI configuration and profiles are described in
configuration.
PAIN001_API_KEY enables API authentication; configure rate limits and shared
job storage before multi-replica deployments. PAIN001_DISABLE_PLUGINS disables
named plugins, and OTEL_ENABLED enables optional tracing. See
OPERATIONS.md and the deployment cookbook.
Never commit keys, credentials or real payment data.
The numbered examples cover generation, input formats, REST, MCP, streaming, schemes, parsers and corpus access; CI executes them. The Quick Start above is also exercised directly by a documentation regression test.
poetry install --all-extras --with dev,docs
poetry run make check
poetry run make type
poetry run python scripts/render_readme.py --check
poetry run make docs
The coverage floor is 100% line and branch. make check runs lint,
coverage, security, complexity ceilings and corpus checks; make type is a separate required gate.
Pull requests also run mutation testing, benchmarks, SDK and container checks.
See DEVELOPMENT.md for the complete gate map and
CONTRIBUTING.md for signed commits and DCO.
README layout is generated from the portfolio template vendored at
docs/readme-template.md, with evidence in docs/readme-values.json.
Edit the values and regenerate with scripts/render_readme.py; CI checks drift.
No fixed test count is advertised because it changes with the branch.
Report security problems privately, never in a public issue.
Untrusted inbound XML uses hardened parsing and rendered XML is XSD-validated.
The build uses locked dependencies and audited CI installation inputs. Actions
are SHA-pinned except the explicitly accepted SLSA generator v2.1.0 references
required for upstream provenance verification; see the security audit.
Atheris and Hypothesis exercise validation paths; no OSS-Fuzz integration is claimed.
The maintainer-approved solo workflow requires PRs, status checks, conversation resolution and administrator enforcement, but zero mandatory approving reviews and no mandatory CODEOWNER approval. This is not independent review and does not resolve historical review findings. See governance.
Report vulnerabilities according to SECURITY.md.
Also see architecture, support, release process, changelog, issue acceptance and security audit.
Versions advance one step at a time on the 0.0.x line, with 0.1.0 after
0.0.999; only the maintainer opens a release. The current release
is 0.0.75; publication requires approved release PRs and signed release tags.
Generated XML changes for identical input, required fields, CLI/REST/MCP contracts and plugin contracts are breaking changes. They must be announced one release ahead; deprecated interfaces remain for at least one release with a warning. Golden files guard byte-exact output. Coordinated suite releases follow ADR-0001. Toolchain changes follow ADR-0004, not incidental dependency updates.
Dual-licensed under Apache-2.0 OR MIT, at your option. See LICENSE. Dependencies retain their own licences.
Generate and validate ISO 20022 payment files (pain.001 v03-v12, pain.008) from CSV, SQLite, JSON, or Parquet. XSD and SEPA scheme validation, pain.002 and camt.053 parsers and builders, plus a CLI, R
ภาพรวม
Generate and validate ISO 20022 payment files (pain.001 v03-v12, pain.008) from CSV, SQLite, JSON, or Parquet. XSD and SEPA scheme validation, pain.002 and camt.053 parsers and builders, plus a CLI, REST API, MCP server, and LSP server for editor diagnostics. 🐍
เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
Pain001 ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-10-28 Generate and validate ISO 20022 payment files (pain.001 v03-v12, pain.008) from CSV, SQLite, JSON, or Parquet. XSD and SEPA scheme validation, pain.002 and camt.053 parsers and builders, plus a CLI, REST API, MCP server, and LSP server for editor diagnostics. 🐍