IBAN Analyzer
REMOTE · IBAN-ANALYZER.COM
Resolve an IBAN to its bank: name, BIC/SWIFT, city and address, and validate IBANs.
Available components
Last scanned (17 hours ago)
Scores higher than 74% of remote servers
Reachable. Last reached 21 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 Security86
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 530 tokens (~106/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 Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
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
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 17 Nov 26 +43
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- 16 Nov 26 34
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 21 Nov 2026 · Probed https://iban-analyzer.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=iban-analyzer.com | CN=WE1,O=Google Trust Services,C=US | 23 Oct 2026 | 21 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | ed2c88d1ee544b950ed55b67805bb5f0 |
| SANs: iban-analyzer.com, *.iban-analyzer.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 secure
Validation of iban-analyzer.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| iban-analyzer.com. | DS published | 2371 | 13 | Verified |
| iban-analyzer.com. | Verified address RRset verified with the apex keys |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | No resource metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://iban-analyzer.com/mcp | Verified | 200 | |
| http (plaintext) | http://iban-analyzer.com/mcp | HTTPS enforced | 301 | https://iban-analyzer.com/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 →
analyze_iban Resolve an IBAN to its bank ~149
Look up which bank an IBAN belongs to. Returns the registered bank name, BIC/SWIFT code and address where it is published, plus whether the IBAN is structurally valid, the country and its SEPA status. Where no bank is returned the result says why: a bank code that was never issued reads differently from one we hold no record for, and neither is ever guessed at. This is the tool to use for a payment instruction. Costs one bank lookup from the caller's monthly allowance, whatever the batch size.
| Name | Type | Req | Description |
|---|---|---|---|
| ibans | array | yes | The IBANs to look up, as written. Spaces and lower case are fine. Up to 50 per call. |
No output schema declared.
No examples provided.
get_allowance Allowance remaining ~46
How much of the caller's monthly allowance is left, which plan it belongs to and when it resets. Check this before a long run of lookups. Free - costs no allowance.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_country_iban_format IBAN format for a country ~59
The IBAN length and SEPA status for one country, and whether its IBANs are approved for international use. Free - costs no allowance.
| Name | Type | Req | Description |
|---|---|---|---|
| country_code | string | yes | Two-letter ISO country code, e.g. DE. |
No output schema declared.
No examples provided.
list_supported_countries Countries covered ~52
Every country this service knows, and for each one whether IBAN validation and bank lookup are available. Use it to find out in advance whether a country can be answered at all. Free - costs no allowance.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
validate_iban Check an IBAN is well formed ~101
Check whether IBANs are structurally valid - length, country, checksum - without looking up the bank behind them. Use this when the question is only 'is this typed correctly'; use analyze_iban when the answer needs to name a bank. Costs one validation from the caller's monthly allowance.
| Name | Type | Req | Description |
|---|---|---|---|
| ibans | array | yes | The IBANs to look up, as written. Spaces and lower case are fine. Up to 50 per call. |
No output schema declared.
No examples provided.
How do I install the IBAN Analyzer MCP server?
IBAN Analyzer is a hosted endpoint at https://iban-analyzer.com/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 · iban-analyzer.com
claude mcp add --transport http vitaliyyun-iban-analyzer 'https://iban-analyzer.com/mcp'
What is the IBAN Analyzer MCP server?
IBAN Analyzer is an MCP server listed in the public MCP registry as io.github.vitaliyyun/iban-analyzer. Resolve an IBAN to its bank: name, BIC/SWIFT, city and address, and validate IBANs. This page covers its hosted endpoint (https://iban-analyzer.com/mcp).
Is the IBAN Analyzer MCP server safe to use?
IBAN Analyzer scores 79 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 IBAN Analyzer MCP server expose?
IBAN Analyzer exposes 5 tools: analyze_iban, validate_iban, get_country_iban_format, list_supported_countries, get_allowance. Their descriptions and schemas cost roughly 407 tokens of context every time the server is loaded.
Does the IBAN Analyzer MCP server require authentication?
Yes. IBAN Analyzer asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the IBAN Analyzer MCP server still maintained?
IBAN Analyzer is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the IBAN Analyzer MCP server?
VerifyMCP ran 13 checks on IBAN Analyzer, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.