iso20022-bank-profile-mcp
Related Servers
Alternatives to iso20022-bank-profile-mcp
- AlicenseAqualityAmaintenanceMatches expected payments (pain.001) against observed booked entries (camt.053) for ISO 20022 cash reconciliation, providing explainable match results with scoring and classification.10386 PyPI1Apache 2.0
Related Servers
- 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.720 PyPI4MIT
- AlicenseAqualityAmaintenanceMCP server that enables AI agents to parse, validate, and reverse ISO 20022 bank statements, with tools for discovering message types and return reasons.24416 PyPI2Apache 2.0
- AlicenseAqualityDmaintenanceAn 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.73 npmMIT
- AlicenseAqualityAmaintenanceAn 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.16433 PyPI1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceA 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
- AlicenseNot gradedqualityCmaintenanceLocal-first MCP server that provides project context, verification gates, and structured tools for coding agents to discover knowledge, run diagnostics, and execute allowlisted commands within a repository.16 npmMIT
TDQS
Scored across 4 tools
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.
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.
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.
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.