# Generate Random IBAN (remote · generaterandomiban.com)

Generate valid test IBANs for 91 countries and validate any IBAN. Public, no API key.

- Trust score: 82/100 (high trust)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

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

## Channel facts

- Endpoint: `https://generaterandomiban.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- 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-06.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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 347 tokens (~115/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 75% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Generate Random IBAN MCP server?

Generate Random IBAN is a hosted endpoint at https://generaterandomiban.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 com-generaterandomiban-iban-generator 'https://generaterandomiban.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-generaterandomiban-iban-generator": {
      "url": "https://generaterandomiban.com/mcp"
    }
  }
}
```

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  com-generaterandomiban-iban-generator:
    url: "https://generaterandomiban.com/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-generaterandomiban-iban-generator": {
      "type": "http",
      "url": "https://generaterandomiban.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-06 (score 82, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-02 (score 82, 0)

- [security] Stability: 0.97 → pass

### 2026-11-01 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (3)

### `list_countries` (~27 tokens)

List all countries supported for IBAN generation, with code, name and IBAN length.

### `generate_iban` (~193 tokens)

Generate one or more random, structurally valid (ISO 13616 / MOD-97) test IBANs for a country, with correct national check digits where the country has them. Generated IBANs were not issued by any bank: never use them for payments.

Input parameters:

- `count` (integer)
- `country` (string, required): ISO 3166-1 alpha-2 country code, e.g. DE, FR, IT.
- `realistic` (boolean): Realistic mode (default true): digits only in alphanumeric fields (except real bank codes that contain letters), and a real bank code of a major bank (where curated data exists for the country) with…

### `validate_iban` (~41 tokens)

Validate an IBAN: MOD-97 checksum, expected length and country support.

Input parameters:

- `iban` (string, required): The IBAN to validate (spaces are ignored).

## Diagnostics

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

## Score history

- 2026-11-06: 82
- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 82
- 2026-11-01: 82
- 2026-10-31: 81
- 2026-10-30: 81
- 2026-10-29: 81
- 2026-10-28: 80
- 2026-10-27: 80
- 2026-10-26: 79
- 2026-10-25: 79
- 2026-10-24: 78
- 2026-10-23: 78
- 2026-10-22: 77
- 2026-10-21: 77
- 2026-10-20: 76
- 2026-10-19: 76
- 2026-10-18: 75
- 2026-10-17: 75
- 2026-10-16: 74
- 2026-10-15: 74
- 2026-10-14: 74
- 2026-10-13: 73
- 2026-10-12: 73
- 2026-10-10: 72
- 2026-10-07: 70
- 2026-10-06: 70
- 2026-10-04: 69

## Common questions

### What is the Generate Random IBAN MCP server?

Generate Random IBAN is an MCP server listed in the public MCP registry as com.generaterandomiban/iban-generator. Generate valid test IBANs for 91 countries and validate any IBAN. Public, no API key. This page covers its hosted endpoint (https://generaterandomiban.com/mcp).

### Is the Generate Random IBAN MCP server safe to use?

Generate Random IBAN scores 82 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 Generate Random IBAN MCP server expose?

Generate Random IBAN exposes 3 tools: list_countries, generate_iban, validate_iban. Their descriptions and schemas cost roughly 261 tokens of context every time the server is loaded.

### Does the Generate Random IBAN MCP server require authentication?

No. We connected to Generate Random IBAN without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Generate Random IBAN MCP server still maintained?

Generate Random IBAN is still listed as active in the MCP registry. We last reached this channel on 6 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 Generate Random IBAN MCP server?

VerifyMCP ran 12 checks on Generate Random IBAN, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Generate Random IBAN: Authorization. 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://generaterandomiban.com/mcp
- Website: https://generaterandomiban.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-generaterandomiban-iban-generator/generaterandomiban.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-generaterandomiban-iban-generator/generaterandomiban/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-generaterandomiban-iban-generator/generaterandomiban.json
- HTML version of this page: https://verifymcp.io/servers/com-generaterandomiban-iban-generator/generaterandomiban