io.github.offx366/ibangen-mcp
PYPI · IBANGEN-MCP
Validate IBANs, generate synthetic test IBANs and look up banks (SWIFT/BIC) via IBANgen.
Available components
Last scanned (11 hours ago)
Scores higher than 62% of PyPI servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 28 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 19 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 252 tokens (~84/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (67% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +35
- Injection markers: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.57 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 12 Oct 26 −27
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 4 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 3 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Sept 26 51
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 18 Oct 2026 · Analysed pypi/ibangen-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
generate_test_ibans ~104
Generate synthetic, checksum-valid test IBANs for QA and development. `country` is a country name such as "Germany" or "UK". `seed` makes the output repeatable. `bank` targets one bank (paid plans). Requires IBANGEN_API_KEY. Output is test data only and must never be used for payments.
| Name | Type | Req | Description |
|---|---|---|---|
| bank | – | – | – |
| country | string | yes | – |
| quantity | integer | – | – |
| seed | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
lookup_bank ~51
Resolve a BIC or domestic bank identifier to registry records with sources. Requires IBANGEN_API_KEY on a plan that includes bank intelligence.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier_type | string | – | – |
| value | string | yes | – |
No output schema declared.
No examples provided.
validate_ibans ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ibans | array | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
How do I install the io.github.offx366/ibangen-mcp server?
io.github.offx366/ibangen-mcp runs locally as a PyPI package, launched with uvx ibangen-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · ibangen-mcp
claude mcp add offx366-ibangen-mcp -- uvx ibangen-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 synthetic test IBANs and look up banks (SWIFT/BIC) via IBANgen. This page covers its PyPI package (ibangen-mcp).
Is the io.github.offx366/ibangen-mcp server safe to use?
io.github.offx366/ibangen-mcp scores 60 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 October 2026. 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 3 tools: validate_ibans, generate_test_ibans, lookup_bank. Their descriptions and schemas cost roughly 252 tokens of context every time the server is loaded.
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 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.offx366/ibangen-mcp server under?
io.github.offx366/ibangen-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.