# IBAN Analyzer (remote · iban-analyzer.com)

Resolve an IBAN to its bank: name, BIC/SWIFT, city and address, and validate IBANs.

- Trust score: 79/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `iban-analyzer.com`: 79/100 (this document), [markdown](https://verifymcp.io/servers/vitaliyyun-iban-analyzer/iban-analyzer.md), [page](https://verifymcp.io/servers/vitaliyyun-iban-analyzer/iban-analyzer)

## Channel facts

- Endpoint: `https://iban-analyzer.com/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 86/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 530 tokens (~106/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http vitaliyyun-iban-analyzer 'https://iban-analyzer.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "vitaliyyun-iban-analyzer": {
      "url": "https://iban-analyzer.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "vitaliyyun-iban-analyzer": {
      "type": "http",
      "url": "https://iban-analyzer.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.vitaliyyun-iban-analyzer]
url = "https://iban-analyzer.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vitaliyyun-iban-analyzer": {
      "type": "remote",
      "url": "https://iban-analyzer.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add vitaliyyun-iban-analyzer --url 'https://iban-analyzer.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  vitaliyyun-iban-analyzer:
    url: "https://iban-analyzer.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "vitaliyyun-iban-analyzer": {
      "Transport": "http",
      "Url": "https://iban-analyzer.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add vitaliyyun-iban-analyzer -t streamable-http -u 'https://iban-analyzer.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "vitaliyyun-iban-analyzer": {
      "type": "http",
      "url": "https://iban-analyzer.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 79, +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.

### 2026-11-19 (score 78, +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.

### 2026-11-18 (score 77, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-17 (score 77, +43)

- [security improvement] Transport: unverified → pass
- [security improvement] 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.
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] 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

### 2026-11-16 (score 34)

First indexed and scored.

## MCP tools (5)

### `analyze_iban` (~149 tokens)

Resolve an IBAN to its bank

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.

Input parameters:

- `ibans` (array, required): The IBANs to look up, as written. Spaces and lower case are fine. Up to 50 per call.

### `validate_iban` (~101 tokens)

Check an IBAN is well formed

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.

Input parameters:

- `ibans` (array, required): The IBANs to look up, as written. Spaces and lower case are fine. Up to 50 per call.

### `get_country_iban_format` (~59 tokens)

IBAN format for a country

The IBAN length and SEPA status for one country, and whether its IBANs are approved for international use. Free - costs no allowance.

Input parameters:

- `country_code` (string, required): Two-letter ISO country code, e.g. DE.

### `list_supported_countries` (~52 tokens)

Countries covered

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.

### `get_allowance` (~46 tokens)

Allowance remaining

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/vitaliyyun-iban-analyzer/iban-analyzer#diagnostics

## Score history

- 2026-11-21: 79
- 2026-11-20: 78
- 2026-11-19: 78
- 2026-11-18: 77
- 2026-11-17: 77
- 2026-11-16: 34

## Common questions

### 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.

## Links

- Remote endpoint: https://iban-analyzer.com/mcp
- Authorisation metadata: https://iban-analyzer.com/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/vitaliyyun/iban-analyzer-mcp
- Website: https://iban-analyzer.com/ib-api/api-docs
- Changelog RSS feed: https://verifymcp.io/servers/vitaliyyun-iban-analyzer/iban-analyzer.xml
- Changelog JSON feed: https://verifymcp.io/servers/vitaliyyun-iban-analyzer/iban-analyzer/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/vitaliyyun-iban-analyzer/iban-analyzer.json
- HTML version of this page: https://verifymcp.io/servers/vitaliyyun-iban-analyzer/iban-analyzer
