Skip to main content
Glama
camt-exceptions

camt-exceptions

Related Servers

Alternatives to camt-exceptions

  • A
    license
    A
    quality
    B
    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
    2
    Apache 2.0

Related Servers

  • A
    license
    A
    quality
    B
    maintenance
    Unified gateway for ISO 20022 message families, providing meta-tools to search, describe, validate, generate, and parse financial messages.
    7
    89 PyPI
    1
    Apache 2.0
  • A
    license
    A
    quality
    B
    maintenance
    Enables AI agents to parse, validate, explain, and test ISO 20022 payment messages such as pacs.008 and pacs.002, mapping validation issues to likely reject codes and generating synthetic test messages. Free-text fields are treated as untrusted data, with prompt-injection patterns flagged and XML parsing hardened against XXE.
    6
    MIT
  • A
    license
    A
    quality
    B
    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
    1
    Apache 2.0
  • A
    license
    A
    quality
    B
    maintenance
    Deterministic corporate banking, payroll, treasury, and e-invoicing MCP server supporting SEPA XML (pain.001), Peppol/EHF/XRechnung, NACHA ACH, BAI2, DATEV, ABA, BACS, CPA-005, Positive Pay, Norma 43, and Fedwire (pacs.008). Enables AI agents to generate, validate, and audit bank-ready payment and invoicing files.
    14
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    MCP server for ISO 20022 acmt.001 Account Opening (and companion acmt.* messages): message-type discovery, required-field lookup, JSON Schema introspection, IBAN/BIC/LEI validation, flat-record validation, and validated acmt XML generation.
    7
    163 PyPI
    1
    Apache 2.0

TDQS

A4.4/5.0

Scored across 4 tools

Disambiguation5/5

Each tool targets a distinct stage of the E&I message workflow: catalogue discovery (list_message_types), schema field lookup (get_required_fields), XML rendering (generate_message), and XML validation (validate_xml). Descriptions explicitly cross-reference alternatives (e.g. 'use validate_xml instead'), leaving no ambiguity.

Naming Consistency5/5

All four names follow a consistent snake_case verb_noun pattern: list_message_types, get_required_fields, generate_message, validate_xml. Verb-first, predictable, and readable throughout.

Tool Count4/5

Four tools form a tight, well-scoped workflow for a focused domain (ISO 20022 E&I message generation and validation). Slightly lean, but each tool clearly earns its place with no redundancy.

Completeness4/5

The surface covers the full lifecycle: discover valid message types, learn required fields, generate XSD-valid XML, and validate existing XML. Minor gaps exist (e.g. no batch validation or per-type example payloads), but core workflows are fully supported.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues