Pain001 MCP server

Read from the package source without running it. The installed server may list more.

• convert_mt101

  Convert a legacy SWIFT MT101 message into pain.001-ready records.

• generate_message

  Generate a validated ISO 20022 pain XML message from in-memory records.

• generate_message_async

  Generate validated pain XML off the event loop, for large batches.

• generate_message_from_file

  Generate validated pain XML from a CSV file on the local disk.

• get_corpus_coverage

  Return the schema coverage verdict of one message type's coverage set.

• get_corpus_file

  Return the XML of one validated example file from the market corpus.

• get_corpus_provenance

  Return the provenance sidecar of one example file.

• get_input_schema

  Return the full JSON Schema for a message type's flat input record.

• get_required_fields

  List only the required input field names for a pain message type.

• inspect_template

  Return the CSV column headers the message type's bundled template uses.

• list_corpus_files

  List the example files pain001 ships: market scenarios and coverage sets.

• list_message_types

  List every supported ISO 20022 pain message type and its human name.

• list_supported_formats

  List the on-disk data formats the pain001 loader can read.

• migrate_records

  Migrate flat payment records between two pain.001 schema versions.

• parse_camt053

  Parse a camt.053 bank-statement XML file on disk into structured data.

• parse_pain002

  Parse a pain.002 payment-status report file on disk into structured data.

• sanitize_to_iso20022_charset

  Sanitise one free-text field to a SWIFT / ISO 20022 character set.

• validate_identifier

  Validate a single financial identifier (IBAN or BIC).

• validate_payment_scheme

  Validate records against a payment-scheme rulebook (e.g. SEPA).

• validate_records

  Validate flat records against a message type's input JSON Schema.

• validate_xml_against_schema

  Validate a raw pain.001 / pain.008 XML string against its official XSD.

• Code scan4 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 0 days ago15/15
• Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Pain001: common questions

Is Pain001 MCP server safe?

Yes, by our scan: it is graded A (92/100). Read the Pain001 safety report

How do I install Pain001?

It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.

Does Pain001 need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Pain001 maintained?

The last commit was in the last day (2026-09-19). The latest release is v0.0.70.

What can I use instead of Pain001?

Servers from other publishers that do the same job: PipRail MCP server, Churnkey MCP server and POPCORN MCP server. Compare all Pain001 alternatives.