Native Shell
Native Shell: AI-generated UI, native in your app, on every platform. Apps on iOS, Android, macOS, Windows and Linux, GPUI apps and web pages load signed, sandboxed TSX modules at run time and draw th
Modern API documentation for IBAN generation, validation, bank statement risk scoring, AI profile generation, bulk datasets, test cases, plan limits, and quality scoring.
Developer toolsPythonGitHub @offx366OnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
MCP server for IBANgen: validate IBANs, generate synthetic test IBANs and look up banks (SWIFT/BIC) from Claude, Cursor and other AI agents.
Taken from the repository README
Loading the full README.
Read the full README ↗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.
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/mcp
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.