LabscoMCP early access ↗
cammac-creatorMCP SERVER

IBANforge

Validate a European IBAN and get the bank behind it, resolve a BIC or a Swiss clearing number, and run a pre-flight compliance check before a SEPA payment leaves.

by cammac-creator ↗Payments, Billing & SubscriptionsCommunity

LABSCO SUMMARY

Enrichment is what makes validation useful — a structurally valid IBAN at the wrong bank passes every checksum test there is.

The IBAN check digit catches typos and nothing else, which means a validated IBAN still tells you almost nothing about whether the payment will arrive where intended. Returning the institution behind it lets the number be checked against the counterparty you think you are paying, and classifying an EMI rather than a bank is a compliance signal a local mod-97 check can never produce. Including Swiss clearing numbers is a specific and useful gap-fill, since those sit outside the BIC system.

What it is

A European banking-identifier service: IBAN validation with enrichment, batch validation, BIC and Swiss clearing-number resolution, and a compliance pre-flight for outgoing payments. Each tool carries its own price, and there are three ways to pay — a free monthly key, a paid account, or per-call payment from an agent's own wallet with no key at all.

What you get

  • validate_iban does more than check the checksum — it returns the bank behind the number, SEPA reachability, issuer classification and a risk read, at $0.005 a call.
  • batch_validate_iban handles up to 100 IBANs in one call at $0.002 each, which is materially cheaper than validating them one at a time.
  • lookup_bic resolves a BIC or SWIFT code to the institution with its name, country, city, address and LEI, at $0.003.
  • lookup_ch_clearing resolves a Swiss BC-Nummer or IID into the institution with its SIC, euroSIC and instant-payment rail participation and QR-IID — a national identifier that sits outside the BIC system entirely.
  • check_compliance runs the pre-flight before a SEPA or cross-border transfer: sanctions, FATF, instant-payment reachability, verification of payee and a risk score, at $0.02.
  • A free structure-only check exists alongside the paid ones — checksum and format with no database lookup — for when you only want to catch a typo.

Requirements

No key to start: without one the server uses the public demo surface. An optional free key, minted with just an email address and set as IBANFORGE_API_KEY, carries 200 requests a month. Point a client at the hosted endpoint or run the npm package locally. There is a third route for agents: the API is x402-native, so a wallet on Base can discover the catalogue and prices, get a payment challenge, pay in USDC and retry, with no key and no human in the loop.

Setup effort

One command — npx -y ibanforge-mcp

See installation options