io.github.offx366/ibangen-mcp
REMOTE · IBANGEN.COM · 2 COMPONENTS
Validate IBANs, generate test IBANs with real bank codes, look up BICs and bank codes (IBANgen).
Available components
Last scanned (7 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 595 tokens (~119/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 68
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://ibangen.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ibangen.com | CN=WE1,O=Google Trust Services,C=US | 1 Nov 2026 | 30 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 5b746558b4131072135065c85ae4f33b |
| SANs: ibangen.com, *.ibangen.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ibangen.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| ibangen.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ibangen.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://ibangen.com/api/mcp | HTTPS enforced | 301 | https://ibangen.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
bank_test_ibans Test IBANs for one bank ~84
A bank's BIC, domestic bank code and free sample test IBANs that carry the bank's real code, plus the bank page and the Bank Target Pack link for up to 250 IBANs of that bank.
| Name | Type | Req | Description |
|---|---|---|---|
| bank | string | yes | Bank name, BIC or domestic bank code |
| country | string | yes | Country name or ISO code |
No output schema declared.
No examples provided.
calculate_iban Calculate an IBAN ~122
Build an IBAN from national bank details (bank code, branch code, account number). Adds the IBAN check digits and, where the country has them, the national check digits such as the French RIB key or the Italian CIN. Use iban_format to see which parts a country needs.
| Name | Type | Req | Description |
|---|---|---|---|
| account_number | string | yes | – |
| bank_code | string | – | – |
| branch_code | string | – | – |
| check_digits | string | – | National check digits, only where they are not computed |
| country | string | yes | Country name or ISO code |
No output schema declared.
No examples provided.
generate_test_ibans Generate test IBANs ~132
Generate synthetic, checksum-valid test IBANs for a country (119 countries, real bank codes). Without an API key: up to 10 a day per user. Name a bank to get IBANs of that bank: free samples without a key, any number with a paid key. Test data only, never for payments.
| Name | Type | Req | Description |
|---|---|---|---|
| bank | string | – | Optional bank name, BIC or bank code, e.g. "Deutsche Bank" |
| country | string | yes | Country name or ISO code, e.g. "Germany", "DE", "UK" |
| quantity | integer | – | – |
No output schema declared.
No examples provided.
iban_format IBAN format of a country ~57
A country's IBAN length, structure (bank code, branch, account and check digit positions), SEPA membership, currency, national check digit, regex and one example test IBAN.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | Country name or ISO code |
No output schema declared.
No examples provided.
validate_ibans Validate IBANs ~86
Check IBANs: country format, length, MOD-97 check digits and, where the country has one, the national check digit of the account number. Up to 10 IBANs per call without an API key. A valid IBAN is well-formed; it does not prove the account exists.
| Name | Type | Req | Description |
|---|---|---|---|
| ibans | array | yes | IBANs, spaces allowed |
No output schema declared.
No examples provided.
How do I install the io.github.offx366/ibangen-mcp server?
io.github.offx366/ibangen-mcp is a hosted endpoint at https://ibangen.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · ibangen.com
claude mcp add --transport http offx366-ibangen-mcp 'https://ibangen.com/api/mcp'
What is the io.github.offx366/ibangen-mcp server?
io.github.offx366/ibangen-mcp is listed in the public MCP registry as io.github.offx366/ibangen-mcp. Validate IBANs, generate test IBANs with real bank codes, look up BICs and bank codes (IBANgen). This page covers its hosted endpoint (https://ibangen.com/api/mcp).
Is the io.github.offx366/ibangen-mcp server safe to use?
io.github.offx366/ibangen-mcp scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.offx366/ibangen-mcp server expose?
io.github.offx366/ibangen-mcp exposes 5 tools: validate_ibans, generate_test_ibans, bank_test_ibans, iban_format, calculate_iban. Their descriptions and schemas cost roughly 481 tokens of context every time the server is loaded.
Does the io.github.offx366/ibangen-mcp server require authentication?
No. We connected to io.github.offx366/ibangen-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.offx366/ibangen-mcp server still maintained?
io.github.offx366/ibangen-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.