Skip to main content
Glama
sebastienrousseau

iso20022-bank-profile-mcp

Related Servers

Alternatives to iso20022-bank-profile-mcp

  • F
    license
    A
    quality
    A
    maintenance
    Matches expected payments (pain.001) against observed booked entries (camt.053) for ISO 20022 cash reconciliation, providing explainable match results with scoring and classification.
    10
    37 PyPI
    1
    -

Related Servers

  • 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
  • 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
    65 PyPI
    2
    -
  • 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
  • F
    license
    A
    quality
    A
    maintenance
    An MCP server that exposes the pacs008 ISO 20022 FI-to-FI Customer Credit Transfer library as tools for AI agents and assistants, enabling generation, validation, and parsing of pacs.008 credit transfer XML messages.
    16
    36 PyPI
    1
    -
  • A
    license
    Not graded
    quality
    C
    maintenance
    A local-first MCP server for financial wire message forensics, providing read-only tools to parse, validate, and detect SR2026 address compliance in ISO 8583, SWIFT MT, and ISO 20022 messages.
    Apache 2.0

TDQS

A4.2/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: listing profiles, retrieving full details, validating a profile definition, and linting a payload against a profile. No overlap or ambiguity.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case: list_profiles, get_profile, validate_profile_definition, lint_payload. Naming is predictable and clear.

Tool Count5/5

Four tools is well-scoped for the domain: discovery, retrieval, definition validation, and payload linting. Each tool earns its place without excess or deficiency.

Completeness4/5

The tool surface covers core workflows (discovery, retrieval, validation, linting). Missing explicit create/update/delete for profiles, but validation suggests profile definition submission. Minor gap but reasonable for a read-heavy MCP.

Maintenance

ActivityActive
ResponsivenessNo issues