ibangen-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| IBANGEN_API_KEY | No | API key for IBANgen. Optional for validation, required for generation and bank lookup. | |
| IBANGEN_API_BASE_URL | No | Overrides the default API base URL. | https://ibangen.com/api/v1 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_ibansA | 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. |
| generate_test_ibansA | Generate synthetic, checksum-valid test IBANs for QA and development.
|
| lookup_bankB | Resolve a BIC or domestic bank identifier to registry records with sources. Requires IBANGEN_API_KEY on a plan that includes bank intelligence. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
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.
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.
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.
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.