ISO 20022 Payment Evidence & Investigation MCP
Related Servers
Alternatives to ISO 20022 Payment Evidence & Investigation MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceMCP server that enables AI agents to parse, validate, and reverse ISO 20022 bank statements, with tools for discovering message types and return reasons.24190 PyPI2Apache 2.0
- AlicenseAqualityBmaintenanceA 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.301,471 PyPI1Apache 2.0
- AlicenseAqualityDmaintenancePactus 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.917 PyPI2MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to explain, scrub and check ISO 20022 payment messages and SSI files entirely on the local machine, including CBPR+ readiness hints, lifecycle triage, IBAN/BIC validation and payment-vs-SSI checks against the user's own licensed reference data. Runs as a local stdio MCP server with no network calls, telemetry or bundled vendor data.MIT
- AlicenseAqualityBmaintenanceAn 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.1684 PyPI1Apache 2.0
- AlicenseAqualityBmaintenanceUnified gateway for ISO 20022 message families, providing meta-tools to search, describe, validate, generate, and parse financial messages.789 PyPI1Apache 2.0
TDQS
Scored across 6 tools
Each tool has a distinct role: parse converts XML to JSON, validate applies business rules, explain produces a plain-language summary, and investigate correlates two messages. The only mild overlap is between explain_message and investigate_payment, both of which surface status/reasons, but the descriptions make the boundary (single message vs. correlation of two) reasonably clear.
All six tools follow a consistent snake_case verb_noun pattern: explain_message, generate_test_message, lookup_code, investigate_payment, parse_message, validate_message. No mixed conventions or vague standalone verbs.
Six tools is well-scoped for an ISO 20022 payment investigation server, with each tool covering a distinct stage of the parse-validate-explain-investigate workflow. Nothing feels redundant or missing at the count level.
The surface covers the core lifecycle for pacs.008/pacs.002: parse, validate, explain, generate test data, look up codes, and investigate. Minor gaps exist—no support for related message types like pacs.004 returns or camt.056 recalls, and no batch/report export—but the stated scope is well covered.