ibanchecker-mcp
Server Details
IBAN validation, extraction, format specs and BIC/SWIFT lookup tools for AI assistants.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- koraykoylu/ibanchecker-mcp
- GitHub Stars
- 0
- Server Listing
- ibanchecker-mcp
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: single validation, bulk validation, text extraction, country format lookup, and BIC lookup. The two validation tools are explicitly differentiated by singular vs. batch usage, and the extraction tool is positioned as a first step for unstructured text.
All tool names use consistent snake_case with verb-first patterns such as validate_iban, validate_bulk_ibans, get_iban_format, lookup_bic, and extract_ibans_from_text. The longer extraction name still follows the same readable convention without mixing naming styles.
Five tools is well-scoped for an IBAN validation service. Each tool covers a distinct operation, and there are no redundant or filler tools.
The set covers the core IBAN lifecycle: extracting candidates from text, validating singles and batches, understanding country formats, and resolving BICs to banks. No obvious operational gaps exist for the stated purpose, and unsupported inputs return structured errors rather than dead ends.
Available Tools
5 toolsextract_ibans_from_textExtract IBANs From TextARead-onlyIdempotentInspect
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 FormatARead-onlyIdempotentInspect
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/SWIFTARead-onlyIdempotentInspect
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 IBANsARead-onlyIdempotentInspect
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 IBANARead-onlyIdempotentInspect
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…
Related MCP Connectors
Cross-border payment & banking intelligence for AI agents: SWIFT/BIC, IBAN, sanctions, FX, tracking.
Validate IBANs, generate test IBANs with real bank codes, look up BICs and bank codes (IBANgen).
Resolve an IBAN to its bank: name, BIC/SWIFT, city and address, and validate IBANs.
Validate IBANs in 111 countries; bank directory checks for DE, AT, BE, FR, LU, NL, PT and ES.
Related MCP Servers
- AlicenseAqualityBmaintenanceEnables 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.6MIT
- AlicenseAqualityBmaintenanceIBAN 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.13344 npm3MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to validate IBAN, BIC, EU VAT, GTIN/EAN/UPC, and ISBN codes offline through format and check-digit checks, and retrieve related metadata.22,888 npmMIT
- AlicenseAqualityDmaintenanceVerified 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.441 npmApache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.