Skip to main content
Glama
sebastienrousseau

iso20022-bank-profile-mcp

Related Servers

Alternatives to iso20022-bank-profile-mcp

  • A
    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
    386 PyPI
    1
    Apache 2.0

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
    20 PyPI
    4
    MIT
  • A
    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
    416 PyPI
    2
    Apache 2.0
  • A
    license
    A
    quality
    D
    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
    3 npm
    MIT
  • A
    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
    433 PyPI
    1
    Apache 2.0
  • 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.5/5.0

Scored across 4 tools

Disambiguation5/5

Each tool targets a distinct action-resource pair: list_profiles (summaries), get_profile (full rule bodies), lint_payload (payload validation), and validate_profile_definition (profile/rule-pack validation). The descriptions explicitly cross-reference when to use each tool and clarify boundaries, eliminating overlap.

Naming Consistency5/5

All tool names use a consistent snake_case verb_noun pattern: list_profiles, get_profile, lint_payload, validate_profile_definition. There is no mixing of conventions or vague verbs, making the set highly predictable.

Tool Count5/5

Four tools is well-scoped for a focused ISO 20022 profile server. Each tool has a clear, non-redundant role in discovery, retrieval, payload linting, and definition validation, so every tool earns its place.

Completeness3/5

The surface covers read and validation workflows (list, get, lint, validate_definition) but lacks any operation to register, update, or delete profiles or rule packs. This is a notable gap because the descriptions mention registering new custom bank profiles and importing external rule packs, yet no such tool exists.

Maintenance

ActivityActive
ResponsivenessNo issues