IBAN validation, BIC/SWIFT lookup, Swiss clearing, SEPA compliance, issuer classification and risk indicators for AI agents. 121k+ BIC entries (38k+
Ibanforge MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. IBAN validation, BIC/SWIFT lookup, Swiss clearing, SEPA compliance, issuer classification and risk indicators for AI agents. 121k+ BIC entries (38k+ LEI-enriched via GLEIF; additional rows from SWIFT directory, Bundesbank, SIX, NBP, EBA.
Add to your MCP config (~/Library/Application Support/Claude/claude_desktop_config.json for Claude Desktop):
Once Ibanforge is connected, these are the calls the assistant has available:
validate_iban — User mentions an IBAN, a bank account, or a SEPA paymentbatch_validate_iban — List of IBANs, CSV cleanup, customer DB dedup, payout list triagelookup_bic — User already has a BIC/SWIFT — backed by 121k+ BIC entries (39k+ LEI-enriched via GLEIF)lookup_ch_clearing — Swiss BC-Nummer / IID — the deepest Swiss clearing data in any public API: full SIX BankMaster rail participation (SIC, euroSIC, CHF instant) +check_compliance — Pre-flight risk triage before a SEPA / cross-border payment (sanctions + FATF + VoP)Railway — The Railway tool exposed by this serverBeing a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
You will need 2 environment variables: IBANFORGE_API_KEY, FACILITATOR_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the payments and commerce options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Ibanforge's toolset — validate_iban, batch_validate_iban, lookup_bic and 3 more — is a fair guide to whether it matches your workflow. It is maintained by cammac-creator; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| validate_iban | User mentions an IBAN, a bank account, or a SEPA payment |
| batch_validate_iban | List of IBANs, CSV cleanup, customer DB dedup, payout list triage |
| lookup_bic | User already has a BIC/SWIFT — backed by 121k+ BIC entries (39k+ LEI-enriched via GLEIF) |
| lookup_ch_clearing | Swiss BC-Nummer / IID — **the deepest Swiss clearing data in any public API**: full SIX BankMaster rail participation (SIC, euroSIC, CHF instant) + QR-IID |
| check_compliance | Pre-flight risk triage before a SEPA / cross-border payment (sanctions + FATF + VoP) |
| Railway | The Railway tool exposed by this server. |
{
"mcpServers": {
"ibanforge": {
"command": "npx",
"args": ["-y", "ibanforge-mcp"]
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| IBANFORGE_API_KEY | Credential the server authenticates with. | Yes |
| FACILITATOR_URL | Endpoint or connection string the server talks to. | Yes |
Payments infrastructure meets AI — customers, invoices, subscriptions and current API docs from Stripe's server.
Build for Shopify with current APIs — the official Dev MCP server for schema-accurate storefront and admin code.
Give your AI assistant a supervised window into your Interactive Brokers account — balances, positions, live quotes and orders.
Invoices, payments and disputes through PayPal's official server — commerce operations by conversation.
Enables querying and listing Azure resources and costs directly from an MCP client.
Empowers LLMs with Bitcoin Lightning Network payment capabilities via the ZBD API.