# io.github.koraykoylu/ibanchecker-mcp (remote · mcp.ibanchecker.cash)

IBAN validation, extraction, format specs and BIC/SWIFT lookup tools for AI assistants.

- Trust score: 68/100 (medium)
- Change this week: +17
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.ibanchecker.cash`: 68/100 (this document), [markdown](https://verifymcp.io/servers/koraykoylu-ibanchecker-mcp/mcp.md), [page](https://verifymcp.io/servers/koraykoylu-ibanchecker-mcp/mcp)
- npm · `@ibanchecker/mcp`: 79/100, [markdown](https://verifymcp.io/servers/koraykoylu-ibanchecker-mcp/ibanchecker-mcp.md), [page](https://verifymcp.io/servers/koraykoylu-ibanchecker-mcp/ibanchecker-mcp)

## Channel facts

- Endpoint: `https://mcp.ibanchecker.cash/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.2`

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

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1030 tokens (~206/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http koraykoylu-ibanchecker-mcp https://mcp.ibanchecker.cash/mcp
```

### Codex

```toml
[mcp_servers.koraykoylu-ibanchecker-mcp]
url = "https://mcp.ibanchecker.cash/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "koraykoylu-ibanchecker-mcp": {
      "type": "remote",
      "url": "https://mcp.ibanchecker.cash/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add koraykoylu-ibanchecker-mcp --url https://mcp.ibanchecker.cash/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  koraykoylu-ibanchecker-mcp:
    url: "https://mcp.ibanchecker.cash/mcp"
```

### Other

```json
{
  "mcpServers": {
    "koraykoylu-ibanchecker-mcp": {
      "type": "http",
      "url": "https://mcp.ibanchecker.cash/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-08-02 (score 68, +11)

- [functional improvement] Schema quality: unverified → excellent

### 2026-08-01 (score 57, +1)

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

### 2026-07-31 (score 56, +3)

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

### 2026-07-30 (score 53, +1)

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

### 2026-07-29 (score 52, +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.

### 2026-07-27 (score 51, +1)

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

### 2026-07-26 (score 50)

First indexed and scored.

## MCP tools (5)

### `validate_iban` (~278 tokens)

Validate IBAN

Validate a single International Bank Account Number (IBAN) against the official ISO 13616 structure for its country.

What it checks: the country code, total length for that country, the national BBAN structure, and the MOD-97 check digits. When the bank/branch code maps to a known institution, the response also includes the bank name, BIC/SWIFT code, and country.

Returns JSON with fields such as `valid` (boolean), `countryCode`, `checkDigitsValid`, the `formatted` IBAN, and an optional `bank` object. On a malformed input the call still succeeds with `valid: false` and a `reason` (e.g. INVALID_FORMAT, INVALID_CHECKSUM); it does not throw for invalid IBANs.

Use this when you have one account number to verify. For many IBANs prefer `validate_bulk_ibans`; to pull IBANs out of prose use `extract_ibans_from_text` first. No account data is stored; validation runs in memory and is discarded.

Input parameters:

- `iban` (string, required): A single IBAN to validate. Case-insensitive; spaces are tolerated and ignored (e.g. 'DE89 3704 0044 0532 0130 00' or 'GB29NWBK60161331926819').

### `validate_bulk_ibans` (~193 tokens)

Validate Multiple IBANs

Validate a batch of up to 100 IBANs in one call, applying the same ISO 13616 checks as `validate_iban` (country, length, BBAN structure, MOD-97).

Returns a JSON array of per-IBAN results in the same order as the input, each with `valid`, `countryCode`, an optional `reason` for failures, and bank details when the code is recognized, plus a summary count of valid vs. invalid entries.

Use this instead of calling `validate_iban` in a loop when checking a list (e.g. a payment file or a column of supplier accounts). Split inputs larger than 100 into multiple calls. Account numbers are validated in memory and never stored.

Input parameters:

- `ibans` (array, required): Array of 1 to 100 IBAN strings to validate. Case-insensitive; spaces are tolerated. Order is preserved in the response.

### `extract_ibans_from_text` (~198 tokens)

Extract IBANs From Text

Scan a free-form block of text and pull out every candidate IBAN, then validate each one.

Useful for unstructured sources such as emails, invoices, PDFs pasted as text, or chat messages where IBANs appear inline and may be split by spaces or surrounded by other words. Returns a JSON array of the IBANs found, each with its validation result (`valid`, `countryCode`, bank details when known); text containing no IBAN returns an empty list rather than an error.

Use this as the first step when the account number is buried in prose; pass the extracted IBANs to `validate_bulk_ibans` only if you need to re-check them separately. Input text is processed in memory and not stored.

Input parameters:

- `text` (string, required): Arbitrary text to scan for IBANs, e.g. the body of an email or invoice. IBANs may be split across spaces or embedded in sentences.

### `get_iban_format` (~175 tokens)

Get Country IBAN Format

Return the IBAN format specification for a country, covering 90 supported IBAN-using countries.

Returns JSON describing the country's total IBAN length, the BBAN layout (bank code, branch code, and account number positions and lengths), an example IBAN, and the SEPA-membership flag. Use this to understand or display how a country's IBAN is structured, to build input masks, or to explain a validation failure, not to validate a specific number (use `validate_iban` for that). An unsupported or unknown country code returns an error result describing the problem.

Input parameters:

- `country_code` (string, required): Two-letter ISO 3166-1 alpha-2 country code, case-insensitive (e.g. 'DE' for Germany, 'GB' for the United Kingdom, 'FR' for France).

### `lookup_bic` (~186 tokens)

Look Up Bank by BIC/SWIFT

Look up a financial institution by its BIC (Business Identifier Code, also called SWIFT code) and return the matching bank's details.

Accepts an 8-character (head office) or 11-character (branch) BIC. Returns JSON with the bank name, city, ISO country code, SEPA membership, and (when available) the official website and Wikidata entity. Use this to resolve a BIC to a human-readable bank, to confirm a SWIFT code is real, or to enrich a validated IBAN with institution details. An unknown or malformed BIC returns an error result rather than a guess; codes are never fabricated.

Input parameters:

- `bic` (string, required): An 8- or 11-character ISO 9362 BIC/SWIFT code, case-insensitive (e.g. 'DEUTDEFF' or 'DEUTDEFF500').

## Diagnostics

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

## Score history

- 2026-08-03: 68
- 2026-08-02: 68
- 2026-08-01: 57
- 2026-07-31: 56
- 2026-07-30: 53
- 2026-07-29: 52
- 2026-07-28: 51
- 2026-07-27: 51
- 2026-07-26: 50

## Links

- Remote endpoint: https://mcp.ibanchecker.cash/mcp
- Repository: https://github.com/koraykoylu/ibanchecker-mcp
- Website: https://ibanchecker.cash/integrations
- Changelog RSS feed: https://verifymcp.io/servers/koraykoylu-ibanchecker-mcp/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/koraykoylu-ibanchecker-mcp/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/koraykoylu-ibanchecker-mcp/mcp