camt053-mcp
Related Servers
Alternatives to camt053-mcp
- FlicenseAqualityAmaintenanceGenerates and validates ISO 20022 Exceptions & Investigations payment cancellation messages (camt.056) with XSD validation.41-
Related Servers
- AlicenseAqualityCmaintenanceAn 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.715MIT
- FlicenseAqualityAmaintenanceA 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.41-
- FlicenseAqualityAmaintenanceAn 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.161-
- FlicenseAqualityAmaintenanceA 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.211-
- AlicenseAqualityCmaintenanceAn 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.74MIT
- AlicenseAqualityCmaintenancePactus 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.92MIT
TDQS
Scored across 24 tools
Each tool targets a distinct resource or action, with parse, validate, convert, list/filter, reverse, export, classify, CBPR, and rulebook tools cleanly separated. The only mild risk is distinguishing convert_mt942 from convert_mt940_to_camt053 and validate_records from validate_statement, but the descriptions remove the ambiguity.
Nearly every tool follows a consistent snake_case verb_noun pattern such as list_*, get_*, validate_*, and generate_*. The minor deviation is convert_mt942 lacking the explicit target suffix that convert_mt940_to_camt053 includes.
At 24 tools the server sits in the heavy 16–25 band, and while the broad scope covers migration, validation, CBPR, rulebook lookup, export, and classification, several small list-lookup and constant-returning helpers inflate the count. The size is defensible but borders on over-scoping for a single MCP server.
The core statement workflow is well covered: parsing, validating, listing/filtering entries, detecting anomalies, generating reversals, exporting journals, classifying entries, and checking CBPR readiness. A minor gap is that get_input_schema and validate_records prepare flat records for generation, but no tool directly consumes those records since generate_reversal takes XML instead.