Skip to main content
Glama
README.md
# ibangen-mcp

<!-- mcp-name: io.github.offx366/ibangen-mcp -->

Official MCP server for [IBANgen](https://ibangen.com), the IBAN generator and validator for payment testing.

MCP server that gives AI agents three IBANgen tools:

| 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` | Yes | Synthetic, checksum-valid test IBANs; optional `seed` and bank targeting. |
| `lookup_bank` | Yes (bank-intelligence plan) | BIC or domestic identifier to registry records with sources. |

Generated IBANs are test data only. A valid IBAN does not prove that an account exists.

## Install

```bash
pip install ibangen-mcp
```

## Claude Desktop / Claude Code

```json
{
  "mcpServers": {
    "ibangen": {
      "command": "ibangen-mcp",
      "env": { "IBANGEN_API_KEY": "your_key_optional_for_validation" }
    }
  }
}
```

Cursor uses the same block in `.cursor/mcp.json`. Get a key at https://ibangen.com/apidoc#auth.

`IBANGEN_API_BASE_URL` overrides the default `https://ibangen.com/api/v1`.

TDQS

A3.9/5.0

Scored across 3 tools

Disambiguation4/5

Each tool has a distinct primary purpose: registry lookup by BIC/identifier, IBAN validation, and synthetic test data generation. The only minor overlap is that validate_ibans also returns bank/BIC data on paid plans, which slightly blurs the line with lookup_bank, but the core intents are clearly separable.

Naming Consistency5/5

All three tools follow a clean verb_noun snake_case pattern: lookup_bank, validate_ibans, generate_test_ibans. The convention is uniform and self-explanatory with no mixed styles.

Tool Count4/5

Three tools is on the lean side but reasonable for a focused IBAN/bank-intelligence utility. Each tool earns its place (validate, lookup, generate), though the surface is thin enough that it borders on minimal.

Completeness4/5

Core workflows—validating IBANs, resolving bank records, and generating test data—are covered, giving a coherent lifecycle for the domain. Minor gaps exist, such as IBAN parsing/component extraction or standalone BIC validation, but agents can work around these.