Skip to main content
Glama
sebastienrousseau

pacs008-mcp

by sebastienrousseau
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to pacs008-mcp

Related Servers

  • pain001-mcp

    sebastienrousseau
    F
    license
    A
    quality
    A
    maintenance
    A 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.
    21
    1
    -

  • swift-iso20022-mcp

    techybiky
    A
    license
    A
    quality
    C
    maintenance
    An 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.
    7
    2 npm
    MIT

  • camt053-mcp

    sebastienrousseau
    F
    license
    A
    quality
    A
    maintenance
    MCP server that enables AI agents to parse, validate, and reverse ISO 20022 bank statements, with tools for discovering message types and return reasons.
    24
    1
    -

  • Pactus

    deniskarlinsky
    A
    license
    A
    quality
    C
    maintenance
    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.
    9
    2
    MIT

  • iso20022-bank-profile-mcp

    sebastienrousseau
    F
    license
    A
    quality
    A
    maintenance
    A fully local, closed-world MCP server that manages, validates, and serves bank-specific ISO 20022 clearing profiles and rule packs, enabling AI agents to discover profiles, fetch them, lint payloads against them, and validate rule-pack definitions.
    4
    1
    -

  • jPOS MCP Server

    mohisyed
    A
    license
    A
    quality
    C
    maintenance
    An MCP server that gives AI agents deterministic, verified access to ISO 8583 field specs, MTI decoding, jPOS packager XML generation, deploy descriptor validation, message building, and jPOS documentation search.
    7
    4
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.4/5.0

Scored across 16 tools

Disambiguation5/5

Every tool targets a clearly distinct resource or action: address classification/validation/repair, schema discovery, record/scheme/XML validation, generation, parsing, and MT103 conversion are all cleanly separated. Even the multiple validate_* tools are disambiguated by their arguments and stated complementary purposes.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern (validate_address, list_schemes, generate_message, parse_message, etc.). The few compound names like verify_bic_online and convert_mt103 still read predictably and do not break the overall convention.

Tool Count4/5

At 16 tools, the server sits just above the typical well-scoped 3-15 range, but the count is justified by the breadth of the pacs.008 domain: discovery, schema, address, BIC, record, scheme, XML, and migration concerns. It is slightly heavy but each tool appears to earn its place.

Completeness5/5

The surface covers the full payment-message lifecycle: schema discovery, required-field lookup, record and scheme validation, address and BIC checks, message generation, XSD validation, inbound parsing, and MT103 migration. There are no obvious dead ends or missing core operations for the stated purpose.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources