swift-iso20022-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_mt_messageA | Validates a SWIFT MT103 (customer credit transfer) or MT202 (FI transfer) message body against mandatory-field rules, field-format rules (dates, currency, BIC, charges code), and IBAN checksums. Use this before submitting or forwarding an MT message, or when an agent needs to check a message it generated or received is well-formed. |
| validate_mx_messageA | Validates an ISO 20022 MX message (pacs.008 or pacs.009 XML) for structural issues: missing MsgId, malformed currency codes, invalid BICFI values, invalid IBAN checksums, and unstructured-address usage flagged against SWIFT's November 2026 CBPR+ structured-address requirement. Not a full XSD validator — use for a fast pre-check before schema validation. |
| validate_bicA | Checks whether a string is a structurally valid BIC (8 or 11 characters: 4-letter bank code, 2-letter country code, 2-char location code, optional 3-char branch code). |
| validate_ibanA | Checks whether a string is a structurally valid IBAN and passes the ISO 7064 mod-97 checksum. |
| convert_mt103_to_pacs008A | Parses a SWIFT MT103 message and maps its fields to the equivalent ISO 20022 pacs.008 fields (MsgId, IntrBkSttlmDt, IntrBkSttlmAmt, Ccy, ChrgBr, Dbtr/Cdtr name and account). Returns a simplified field map plus notes on anything that couldn't be confidently mapped — not a full XML generator, intended for agents that need a quick MT-to-MX field bridge. |
| convert_mt202_to_pacs009A | Parses a SWIFT MT202 (General Financial Institution Transfer) message and maps its fields to the equivalent ISO 20022 pacs.009 fields (MsgId, EndToEndId, IntrBkSttlmDt, IntrBkSttlmAmt, Ccy, InstgAgt/InstdAgt/IntrmyAgt1 BICs). Unlike MT103, MT202 moves money bank-to-bank so there is no customer-level Dbtr/Cdtr — only institution BICs. Returns notes on anything not confidently mapped. |
| convert_pacs008_to_mt103A | Parses an ISO 20022 pacs.008 XML message and maps its fields back to SWIFT MT103 field tags (:20:, :23B:, :32A:, :50K:, :59:, :71A:). Useful during the SWIFT MT/MX coexistence period when a downstream system still expects MT format. Deliberately conservative — only maps fields it can extract with confidence and flags the rest in the notes array rather than guessing. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/techybiky/swift_mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server