ibanforge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Server port (default: 3000) |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_iban | Validate a single IBAN number and retrieve the associated BIC/SWIFT code and bank information. Use this tool when you need to validate one IBAN at a time — for example, verifying a payment recipient before a wire transfer, checking a bank account provided by a user, or confirming IBAN format during onboarding. Returns: validity status, country, bank code, BIC/SWIFT, bank name, BBAN structure, SEPA membership & schemes (SCT/SDD/SCT_INST) with VoP requirement, issuer classification (bank/digital_bank/emi/payment_institution) with institution name, and composite risk indicators (issuer_type, country_risk, test_bic, sepa_reachable, vop_coverage). Supports 75+ countries including all SEPA countries (EU, Switzerland, UK, Norway, etc.). Example input: 'CH56 0483 5012 3456 7800 9' (spaces are stripped automatically) Example output: { valid: true, country: { code: 'CH', name: 'Switzerland' }, bic: 'CRESCHZZ80A', ... } Cost: $0.005 USDC per call via x402 micropayment on Base L2. For multiple IBANs, prefer batch_validate_iban (60% cheaper per IBAN). |
| batch_validate_iban | Validate up to 100 IBANs in a single call. Much more economical than individual calls ($0.002/IBAN vs $0.005/IBAN — 60% cheaper). Use this tool when you need to validate multiple IBANs at once — for example, processing a CSV of supplier accounts, validating a payment batch before submission, running KYC checks on a list of customers, or auditing an accounts-payable file. Returns an array of results in the same order as the input, each containing: validity, country, BIC, bank name, SEPA info & schemes, issuer classification, and risk indicators. Example input: ['CH56 0483 5012 3456 7800 9', 'DE89370400440532013000', 'FR7630006000011234567890189'] Cost: $0.002 USDC per IBAN (e.g. 10 IBANs = $0.020, 50 IBANs = $0.100, 100 IBANs = $0.200) For a single IBAN, use validate_iban instead. |
| lookup_bic | Look up a BIC/SWIFT code and return full institution details, country, city, and LEI regulatory data. Use this tool when you have a BIC/SWIFT code and need to identify the bank behind it — for compliance checks, payment routing validation, correspondent banking lookups, or KYC enrichment. Returns: validity, institution name, country, city, branch info, LEI identifier, LEI status. Supports BIC8 (e.g. 'UBSWCHZH') and BIC11 (e.g. 'UBSWCHZH80A') formats. Database: 39,000+ institutions from GLEIF with LEI enrichment. Example input: 'BNPAFRPP' → BNP Paribas, France, Paris Example input: 'UBSWCHZH80A' → UBS AG, Switzerland, Zurich (branch 80A) Cost: $0.003 USDC per call via x402 micropayment on Base L2. Tip: if you already have an IBAN, use validate_iban instead — it resolves the BIC automatically. |
| compliance_check | Run a full compliance check on an IBAN: sanctions screening, SEPA reachability, VoP participation, and composite risk scoring. Use this tool when you need to assess the compliance risk of a payment recipient — for example, verifying an IBAN is not associated with a sanctioned country or bank, checking if a bank participates in SEPA Instant (SCT Inst) or Verification of Payee (VoP), or producing a structured risk score for AML/KYC workflows. Returns: IBAN validation result + compliance bundle:
Example input: 'CH56 0483 5012 3456 7800 9' Example output: { valid: true, compliance: { sanctions: { country_sanctioned: false, ... }, risk_score: 10, risk_level: 'low', ... } } Cost: $0.02 USDC per call via x402 micropayment on Base L2. |
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
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/cammac-creator/ibanforge'
If you have feedback or need assistance with the MCP directory API, please join our Discord server