Skip to main content
Glama
ibanchecker-mcp

ibanchecker-mcp

ibanchecker-mcp

npm version License: MIT Model Context Protocol

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 92 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.

Quick start: hosted remote server

The easiest path is the hosted endpoint. Nothing to install or deploy. Every tool except get_iban_format needs an API key (see API key).

https://mcp.ibanchecker.cash/mcp

Claude Code

claude mcp add --transport http ibanchecker https://mcp.ibanchecker.cash/mcp --header "Authorization: Bearer YOUR_API_KEY"

Claude Desktop (claude_desktop_config.json), via the mcp-remote bridge:

{
  "mcpServers": {
    "ibanchecker": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.ibanchecker.cash/mcp", "--header", "Authorization:${AUTH_HEADER}"],
      "env": {
        "AUTH_HEADER": "Bearer your-api-key-here"
      }
    }
  }
}

Related MCP server: veridigit

Local stdio server

Run the server locally over stdio (requires Node 18+):

{
  "mcpServers": {
    "ibanchecker": {
      "command": "npx",
      "args": ["-y", "@ibanchecker/mcp"],
      "env": {
        "IBANCHECKER_API_KEY": "your-api-key-here"
      }
    }
  }
}

Example

Calling validate_iban with DE89370400440532013000 returns:

{
  "valid": true,
  "iban": "DE89370400440532013000",
  "formatted": "DE89 3704 0044 0532 0130 00",
  "country_name": "Germany",
  "bank_name": "Commerzbank AG Cologne",
  "bic": "COBADEFFXXX",
  "bank_code": "37040044",
  "account_number": "0532013000",
  "sepa": true
}

When the API returns an error (for example a 429 rate limit, a 401 missing or bad key, or a 403 tool outside the key's plan), the tool result is flagged with isError: true and a human-readable message, so the assistant can react rather than crash.

API key

Every tool except get_iban_format needs an API key, and what a key can call follows its plan:

Tool

Free key

Free key with a verified account

Basic / Starter

Growth / Enterprise

validate_iban

yes

yes

yes

yes

validate_bulk_ibans

no

up to 10 IBANs a call

up to 100

up to 100

lookup_bic

no

yes

yes

yes

extract_ibans_from_text

no

up to 5,000 characters a call

trial with a verified account

up to 50,000

get_iban_format

yes

yes

yes

yes

get_iban_format also works without a key, up to 100 requests an hour per IP. A free key covers 100 requests a month and arrives by email in seconds: get one at ibanchecker.cash/api-docs. A free account on the same address, at ibanchecker.cash/dashboard, opens the trials. Bulk validation and extraction count one request per IBAN. See ibanchecker.cash/pricing for higher volumes. Pass the key as:

  • IBANCHECKER_API_KEY env var (stdio mode), or

  • Authorization: Bearer <key> / x-api-key header (remote mode).

Project layout

.
├── bin/stdio.mjs      # npm CLI entry (published as `ibanchecker-mcp`)
├── shared/tools.mjs   # the 5 tool definitions, shared by both transports
└── worker/            # Cloudflare Worker (the hosted remote server)
    ├── src/index.ts
    └── wrangler.toml

Both the stdio CLI and the Worker register the exact same tools from shared/tools.mjs, so there is a single source of truth.

Self-hosting the Worker

The remote server is a Cloudflare Worker built on the Agents SDK. Deploy your own:

cd worker
npm install
npx wrangler deploy

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.

License

MIT. See LICENSE.

Available Tools

5 tools
extract_ibans_from_textExtract IBANs From TextA
Read-onlyIdempotent
Inspect

Scan a free-form block of text and pull out every candidate IBAN, then validate each one.

Useful for unstructured sources such as emails, invoices, PDFs pasted as text, or chat messages where IBANs appear inline and may be split by spaces or surrounded by other words. Returns JSON with count, valid_count, invalid_count and results, one validate_iban-shaped entry per IBAN found; text containing no IBAN returns an empty list rather than an error.

Use this as the first step when the account number is buried in prose; pass the extracted IBANs to validate_bulk_ibans only if you need to re-check them separately. Input text is processed in memory and not stored. Requires an API key on the Growth plan or above; a free key whose address has a verified ibanchecker.cash account can try it with up to 5,000 characters per call. Each IBAN found counts as one request.

Inputs: text (required).

get_iban_formatGet Country IBAN FormatA
Read-onlyIdempotent
Inspect

Return the IBAN format specification for a country, covering 92 supported IBAN-using countries.

Returns JSON describing the country's total IBAN length, the BBAN layout (bank code, branch code, and account number positions and lengths), an example IBAN, and the SEPA-membership flag. Use this to understand or display how a country's IBAN is structured, to build input masks, or to explain a validation failure, not to validate a specific number (use validate_iban for that). An unsupported or unknown country code returns an error result describing the problem. Works without an API key, up to 100 requests an hour per IP.

Inputs: country_code (required).

lookup_bicLook Up Bank by BIC/SWIFTA
Read-onlyIdempotent
Inspect

Look up a financial institution by its BIC (Business Identifier Code, also called SWIFT code) and return the matching bank's details.

Accepts an 8-character (head office) or 11-character (branch) BIC. Returns JSON with bic, bic8, bank_name, city, country_code, country_name, sepa, the institution type and its status. Use this to resolve a BIC to a human-readable bank, to confirm a SWIFT code is real, or to enrich a validated IBAN with institution details. An unknown or malformed BIC returns an error result rather than a guess; codes are never fabricated. Requires an API key on the Basic plan or above, or a free key whose address has a verified ibanchecker.cash account.

Inputs: bic (required).

validate_bulk_ibansValidate Multiple IBANsA
Read-onlyIdempotent
Inspect

Validate a batch of up to 100 IBANs in one call, applying the same ISO 13616 checks as validate_iban (country, length, BBAN structure, MOD-97).

Returns JSON with count, valid_count, invalid_count and results, one entry per IBAN in input order, each shaped like a validate_iban result.

Use this instead of calling validate_iban in a loop when checking a list (e.g. a payment file or a column of supplier accounts). Split inputs larger than 100 into multiple calls. Account numbers are validated in memory and never stored. Requires an API key on the Basic plan or above; a free key whose address has a verified ibanchecker.cash account can try it with up to 10 IBANs per call. Each IBAN counts as one request.

Inputs: ibans (required).

validate_ibanValidate IBANA
Read-onlyIdempotent
Inspect

Validate a single International Bank Account Number (IBAN) against the official ISO 13616 structure for its country.

What it checks: the country code, total length for that country, the national BBAN structure, and the MOD-97 check digits. When the bank/branch code maps to a known institution, the response also includes the bank name, BIC/SWIFT code, and country.

Returns JSON with valid (boolean), iban, formatted, country, country_name, check_digits, bban, and, when the bank is recognized, bank_name, bic, bank_code, bank_city, sepa and national_check_valid. An invalid IBAN still returns a result, with valid: false, an error message and an error_code (e.g. INVALID_CHECKSUM, INVALID_LENGTH, UNKNOWN_COUNTRY); it does not throw.

Use this when you have one account number to verify. For many IBANs prefer validate_bulk_ibans; to pull IBANs out of prose use extract_ibans_from_text first. No account data is stored; validation runs in memory and is discarded. Requires an API key; a free key from ibanchecker.cash/api-docs covers 100 requests a month.

Inputs: iban (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.7/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: single validation, bulk validation, text extraction, format specification, and BIC lookup. The descriptions explicitly guide when to use one over another, such as preferring bulk over looping single validation.

    Naming Consistency5/5

    All tool names use snake_case with a consistent verb_noun structure (validate_iban, validate_bulk_ibans, get_iban_format, lookup_bic). The longer extract_ibans_from_text still follows the same readable pattern.

    Tool Count5/5

    Five tools is well-scoped for an IBAN validation service. Each tool covers a distinct operation and none feels redundant or excessive.

    Completeness4/5

    The core validation lifecycle is well covered: single, bulk, extraction from text, format lookup, and BIC resolution. A minor gap is the lack of a tool to enumerate all supported countries or list banks by country, but agents can work around this via format lookups.

    Maintenance

    ActivitySlowing
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      IBAN validation across 89 countries, BIC/SWIFT and Swiss clearing lookup, batch validation, payment-reference, postal-address and Swiss QR-bill checks for AI agents. Connect via MCP or the REST API. Includes free quotas, paid credits and a Pro subscription. SEPA and country-risk indicators support payment-data checks; they do not confirm account ownership or replace beneficiary AML/KYC screening.
      13
      344 npm
      3
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Verified validation of structured identifiers — IBAN, payment cards, ISBN-13 and VIN — for AI agents. Runs the real checksum algorithms (mod-97, Luhn, mod-10, ISO 3779) instead of letting the model guess, and returns structured results with clear errors.
      4
      41 npm
      Apache 2.0
    • F
      license
      Not graded
      quality
      B
      maintenance
      Validates International Bank Account Numbers (IBANs) through a Cloudflare-hosted MCP server, enabling agents to check IBAN validity via natural language.
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to validate IBANs, generate synthetic checksum-valid test IBANs, and look up bank registry records by BIC or domestic identifier, with optional paid capabilities for bank, BIC, and SEPA Instant/VoP reachability.
      6
      MIT