About ibangen-mcp
ibangen-mcp is an MCP server for payment-testing workflows that need IBAN validation, synthetic account data, or bank lookups. Its tools cover both IBANs and US routing and account test data, with API-key requirements varying by operation.
Key features
- 01Validate IBAN format and checksum
- 02Generate synthetic test IBANs
- 03Look up bank registry records
- 04Generate US test account data
- 05Validate and look up US routing numbers
Use cases
- 01Check IBANs before payment-test runs
- 02Create reproducible synthetic IBAN samples
- 03Retrieve bank details from a BIC
- 04Prepare US routing and account test data
MCP support
It exposes IBAN and US bank-data tools to MCP clients. Some operations need an API key, and metered US lookups require explicit credit approval.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
uvx ibangen-mcpIBANGEN_API_KEYSecretIBANgen API key; optional for validation, required for generation and bank lookupLocal servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
3Saved tool list · updated 3w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| ibans | array | Yes |
Details
From the project READMEibangen-mcp
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 |
|---|---|---|
validate_ibans | 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. |
generate_test_ibans | No for country-level IBANs (10 a day per IP); a key for more and for bank targeting | Synthetic, checksum-valid test IBANs; optional seed and bank targeting (paid key). |
lookup_bank | Yes (bank-intelligence plan) | BIC or domestic identifier to registry records with sources. |
generate_us_test_accounts | Yes (free key is sufficient) | 1–10 US routing/account test rows; optional reproducible seed; no paid reveal or targeting. |
validate_us_routing_numbers | 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. |
lookup_us_routing_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.
Install
pip install ibangen-mcp
Claude Desktop / Claude Code
{
"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.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.