The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Ibanchecker MCP listing page.
MCP (Model Context Protocol) server for ibanchecker.cash. Gives AI assistants like Claude five finance tools backed by the ibanchecker.cash validation engine:
| Tool | What it does |
|---|---|
validate_iban | Validate a single IBAN: country, length, national BBAN structure, MOD-97 check digits, and bank details when available |
validate_bulk_ibans | Validate up to 100 IBANs in one call |
extract_ibans_from_text | Find and validate every IBAN inside a block of text (emails, invoices, spreadsheets) |
get_iban_format | IBAN format specification for any of 90 supported countries |
lookup_bic | Look up a bank by BIC/SWIFT code |
No IBAN data is logged or stored; validation runs in memory on Cloudflare's edge. See the security page for details.
The easiest path is the hosted endpoint. Nothing to install or deploy.
Claude Code
Claude Desktop (claude_desktop_config.json), via the mcp-remote bridge:
Run the server locally over stdio (requires Node 18+):
Calling validate_iban with DE89370400440532013000 returns:
When the API returns an error (for example a 429 rate limit or 401 bad key), the tool result is flagged with isError: true and a human-readable message, so the assistant can react rather than crash.
The underlying REST API has a free tier (1,000 requests/month). Get a key at ibanchecker.cash/api-docs and pass it as:
IBANCHECKER_API_KEY env var (stdio mode), orAuthorization: Bearer <key> / x-api-key header (remote mode).Both the stdio CLI and the Worker register the exact same tools from shared/tools.mjs, so there is a single source of truth.
The remote server is a Cloudflare Worker built on the Agents SDK. Deploy your own:
Remove the routes block in worker/wrangler.toml (or point it at your own domain) and optionally set a server-wide key with npx wrangler secret put IBANCHECKER_API_KEY.
MIT. See LICENSE.