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
} |
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. |
| generate_us_test_accountsA | 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. |
| validate_us_routing_numbersA | 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. |
| lookup_us_routing_numberA | 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. |
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 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.