This MCP server provides IBAN and US bank-account test-data tools for validation, generation, and registry lookups, with some tools free and others requiring an API key/plan.
Validate up to 10 IBANs per call for country format, length, and MOD-97 checksum; paid keys add bank, BIC, and SEPA Instant / VoP reachability.
Generate synthetic, checksum-valid test IBANs, optionally with a reproducible seed; bank targeting requires a paid key.
Look up banks by BIC or domestic identifier with source-backed registry records, requiring a bank-intelligence plan.
Generate 1–10 synthetic US routing/account test rows with a free API key and optional seed.
Validate 1–10 US routing numbers through the metered registry API, requiring explicit approval of up to one credit per distinct number.
Look up a 9-digit US routing number with entitlement gates and explicit approval of one API credit.
All generated data is test-only; valid IBANs or routing references do not prove account existence or payment eligibility, and metered calls should not be automatically retried.
Adds SEPA Instant and Verification of Payee reachability checks to IBAN validation on paid plans.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@ibangen-mcp is DE89370400440532013000 a valid IBAN?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Official MCP server for IBANgen, the IBAN generator and validator for payment testing.
MCP server that gives AI agents IBANgen tools for IBAN and US bank account test data.
Tool | Key needed | What it does |
| No (10 IBANs per call, small daily allowance per IP) | Country format, length and MOD-97 checksum. Paid keys add bank, BIC and SEPA Instant / VoP reachability. |
| No for country-level IBANs (10 a day per IP); a key for more and for bank targeting | Synthetic, checksum-valid test IBANs; optional |
| Yes (bank-intelligence plan) | BIC or domestic identifier to registry records with sources. |
| Yes (free key is sufficient) | 1–10 US routing/account test rows; optional reproducible seed; no paid reveal or targeting. |
| Yes (qualifying registry plan) | 1–10 routing numbers through the existing metered registry API; requires explicit approval of up to one API credit per distinct number. |
| Yes (existing API entitlement gates) | Source-backed routing lookup; requires explicit approval of one API credit. |
For assistants without MCP, the same product map is published as plain text at https://ibangen.com/llms.txt and https://ibangen.com/llms-full.txt.
Generated IBANs are test data only. A valid IBAN does not prove that an account exists. US account numbers are synthetic; routing references do not establish live ACH, Fedwire or account eligibility. The metered US tools do not replace the free web preview and do not bypass bank metadata gates. They never automatically retry a transport failure, because a credit may already have been consumed.
Add https://ibangen.com/api/mcp as a custom connector in ChatGPT, Claude, Cursor or VS Code
(Streamable HTTP, no key needed to start; send Authorization: Bearer <API key> for paid-plan limits).
It offers validate_ibans, generate_test_ibans, bank_test_ibans (free sample IBANs, BIC and bank
code of one bank), iban_format and calculate_iban.
claude mcp add --transport http ibangen https://ibangen.com/api/mcpRelated MCP server: veridigit
pip install ibangen-mcp{
"mcpServers": {
"ibangen": {
"command": "ibangen-mcp",
"env": { "IBANGEN_API_KEY": "optional_for_validation_and_10_ibans_a_day" }
}
}
}Cursor uses the same block in .cursor/mcp.json. Get a free key (100 API calls a month) at https://ibangen.com/account?focus=api.
The same API is also sold on RapidAPI (IBAN plus US bank account and routing test data).
IBANGEN_API_BASE_URL overrides the default https://ibangen.com/api/v1.
Generate synthetic, checksum-valid test IBANs for QA and development.
country is a country name such as "Germany" or "UK". seed makes the output
repeatable. Without IBANGEN_API_KEY up to 10 country-level IBANs a day per IP
(bank fields hidden); a free key gives 100 API calls a month. bank targets one
bank and needs a paid key. Output is test data only and must never be used for payments.
Inputs: country (required), bank, seed, quantity. Returns: result
Generate 1–10 free US routing/account test rows using an API key.
Accounts are synthetic; routing references do not establish live payment eligibility. No bank reveal, paid targeting or profile generation is requested. A seed makes results reproducible. Never use these values for payments.
Inputs: seed, quantity.
Resolve a BIC or domestic bank identifier to registry records with sources.
Requires IBANGEN_API_KEY on a plan that includes bank intelligence.
Inputs: value (required), identifier_type.
Look up a 9-digit US routing number with the existing API entitlement gates.
Ask the user to approve one API credit before confirm_api_credit=True. Preserve leading zeros. Registry evidence does not prove account existence or current ACH/Fedwire eligibility. Do not automatically retry a failed metered call.
Inputs: routing_number (required), confirm_api_credit.
Validate IBANs: country format, length and MOD-97 checksum.
Works without an API key for up to 10 IBANs per call (small daily allowance per IP). With IBANGEN_API_KEY set, paid plans also return the bank, BIC and SEPA Instant / Verification of Payee reachability. A valid result does not prove that an account exists.
Inputs: ibans (required). Returns: result
Check 1–10 US routing numbers against the existing metered registry API.
Requires a qualifying API key/plan. Ask the user to approve spending up to one API credit per distinct number before setting confirm_api_credits=True. Returns source observations, not account existence or proof of ACH eligibility. This is not the free web preview. Do not automatically retry a failed call.
Inputs: routing_numbers (required), confirm_api_credits.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 6 tools
Most tools target distinct resources, but lookup_us_routing_number and validate_us_routing_numbers overlap heavily—both check US routing numbers against the same registry, differing mainly in singular vs. batch input and naming. lookup_bank and lookup_us_routing_number are also both registry lookups that an agent could plausibly confuse when choosing a tool.
All tools follow a verb_noun pattern (validate_*, lookup_*, generate_*), which is predictable. However, qualifier ordering is inconsistent (generate_test_ibans vs. generate_us_test_accounts) and singular/plural forms vary across the related US routing tools.
Six tools is well-scoped for IBAN validation, test data generation, US routing lookups, and bank intelligence. Each tool has a distinct role and the set is neither thin nor bloated.
The surface covers validation, generation, and lookup for the core IBAN and US routing domains, including test data workflows. Minor gaps exist, such as no dedicated BIC validation or country/list support tool, but agents can work around these via existing endpoints.
IBAN validation, extraction, format specs and BIC/SWIFT lookup tools for AI assistants.
Cross-border payment & banking intelligence for AI agents: SWIFT/BIC, IBAN, sanctions, FX, tracking.
Utility data for AI agents: IBAN, EU holidays, VAT rates, time zones, ECB FX. Pay per call.
Validate IBANs in 111 countries; bank directory checks for DE, AT, BE, FR, LU, NL, PT and ES.
