# io.github.cammac-creator/ibanforge (remote · api.ibanforge.com)

Pre-payout IBAN screening for AI agents: validation, sanctions (OFAC), Swiss clearing, risk

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

## Components

- remote · `api.ibanforge.com`: 78/100 (this document), [markdown](https://verifymcp.io/servers/cammac-creator-ibanforge/api.md), [page](https://verifymcp.io/servers/cammac-creator-ibanforge/api)
- npm · `ibanforge-mcp`: 66/100, [markdown](https://verifymcp.io/servers/cammac-creator-ibanforge/ibanforge-mcp.md), [page](https://verifymcp.io/servers/cammac-creator-ibanforge/ibanforge-mcp)

## Channel facts

- Endpoint: `https://api.ibanforge.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.4.1`

## 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**: 83/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 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**: 78/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1401 tokens (~200/item across 7 items; 5 tools + 2 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **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 cammac-creator-ibanforge https://api.ibanforge.com/mcp
```

### Codex

```toml
[mcp_servers.cammac-creator-ibanforge]
url = "https://api.ibanforge.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cammac-creator-ibanforge": {
      "type": "remote",
      "url": "https://api.ibanforge.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cammac-creator-ibanforge --url https://api.ibanforge.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  cammac-creator-ibanforge:
    url: "https://api.ibanforge.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "cammac-creator-ibanforge": {
      "type": "http",
      "url": "https://api.ibanforge.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-08-03 (score 78, +1)

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

### 2026-08-01 (score 77, +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 76, +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 73, +1)

- [functional] Server version: 1.4.0 → 1.4.1

### 2026-07-29 (score 72, 0)

- [security] Tool “validate_iban” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 176 → 200

### 2026-07-27 (score 72, +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 71)

First indexed and scored.

## MCP tools (5)

### `validate_iban` (~489 tokens)

Validate IBAN

Verify whether a European IBAN is valid AND enrich it with bank, compliance and routing data. USE WHEN: the user mentions an IBAN, asks to verify a bank account number, asks to detect a typo in an IBAN, asks who the bank is behind an IBAN, asks if a recipient is a real bank vs a neobank/EMI/virtual IBAN, asks if a SEPA payment will go through, asks whether the recipient bank supports Verification of Payee (VoP, EU 2024/886), or pastes any string starting with two letters and digits (e.g., "DE89...", "CH93...", "FR76..."). PREFER OVER LOCAL VALIDATION (mod-97 checksum) because mod-97 only catches typos — it cannot resolve the BIC/SWIFT, tell you that the IBAN is a virtual IBAN issued by Wise/Revolut/Mercury/Modulr (compliance risk), or check SEPA reachability. RETURNS: valid (boolean), country { code, name }, bic { code, bank_name, city }, issuer { type: bank | digital_bank | emi | payment_institution, name }, sepa { member, schemes, vop_required }, risk_indicators { issuer_type (null when no institution resolved), country_risk, test_bic, sepa_reachable, sepa_reachable_scope, vop_coverage }, and for CH/LI: clearing { iid, name, type, sic, qr_iid }. IMPORTANT — bic: null does not mean the bank code is wrong. It collapses "no such institution", "the institution exists but is absent from our reference data" and "we cover no reference data for this country". Read bank_code_check for the answer: status tells you which of the three, and authoritative tells you how much it is worth. Only where authoritative is true (today CH and LI against the SIX BankMaster, and DE against the Bundesbank Bankleitzahlendatei) does not_in_register mean the bank code is not allocated; everywhere else treat it as UNAVAILABLE and let the downstream name check decide. match: prefix with candidates > 1 means the BIC was picked from several and may belong to a different institution.

Input parameters:

- `iban` (string, required): IBAN to validate (spaces/hyphens stripped automatically)

Output parameters:

- `bank_code_check` (object)
- `bban` (object)
- `bic`: Resolved BIC/SWIFT when BBAN→BIC mapping exists.
- `check_digits` (string)
- `clearing`: Swiss clearing data when country is CH or LI.
- `cost_usdc` (number)
- `country` (object)
- `error` (string)
- `error_detail` (string)
- `formatted` (string): IBAN with 4-char groups for display.
- `iban` (string): Normalized IBAN (uppercase, no spaces).
- `issuer` (object)
- `next_steps` (array): Ordered advice derived from THIS result: what blocks a payment first, what merely enriches it after. Branch on `code`, never on the prose. `because` names the field that produced the step so the advi…
- `processing_ms` (number)
- `risk_indicators` (object)
- `sepa` (object)
- `valid` (boolean)

### `batch_validate_iban` (~146 tokens)

Batch Validate IBANs

Validate up to 100 IBANs in a single call at $0.002 per IBAN (60% cheaper than calling validate_iban repeatedly at $0.005). USE WHEN: the user pastes a list of IBANs, asks to clean a CSV/spreadsheet of bank accounts, asks to dedupe a customer database, asks to triage a payout list before sending, or whenever you would otherwise call validate_iban more than 2-3 times in a row. RETURNS: { results: [...same shape as validate_iban], count, valid_count }.

Input parameters:

- `ibans` (array, required): Array of IBANs (1-100)

Output parameters:

- `count` (number): Number of IBANs processed.
- `results` (array): One result per input IBAN, in the same order. Same shape as validate_iban.

### `lookup_bic` (~194 tokens)

Lookup BIC/SWIFT

Resolve a BIC / SWIFT code into the underlying bank: name, country, city, LEI, and registered head-office address (where available). USE WHEN: the user already has a BIC/SWIFT (8 or 11 chars, alphanumeric, e.g., "UBSWCHZH80A", "DEUTDEFF") and asks which bank it belongs to, where the bank is, or its LEI for compliance/regulatory matching. DO NOT USE for IBAN inputs — call validate_iban instead, it resolves the BIC for you. BACKED BY: 121,000+ BIC entries (39,000+ LEI-enriched via GLEIF; additional rows from SWIFT directory, Bundesbank, SIX, NBP, EBA Step2 SCT), refreshed monthly.

Input parameters:

- `bic` (string, required): BIC/SWIFT code (8 or 11 chars)

Output parameters:

- `bic` (string): Echo of the input, normalized to uppercase.
- `bic11` (string): 11-char form including branch.
- `bic8` (string): 8-char form (institution-level).
- `branch_code` (string)
- `branch_info`
- `city`
- `country` (object): Same shape as REST GET /v1/bic/:code. name falls back to the country code when the row carries no name.
- `country_code` (string): DEPRECATED since 1.4.0, removed no earlier than 2027-01-01. Use country.code.
- `country_name`: DEPRECATED since 1.4.0, removed no earlier than 2027-01-01. Use country.name, which falls back to the code rather than to null.
- `error` (string)
- `found` (boolean)
- `institution`: Bank legal name.
- `is_test_bic` (boolean)
- `lei`: Legal Entity Identifier (ISO 17442) if available.
- `lei_status`
- `valid` (boolean): Set when the BIC failed format validation.
- `valid_format` (boolean)

### `check_compliance` (~247 tokens)

Compliance Check

Run a full pre-flight compliance check on an IBAN before sending a SEPA / cross-border payment. USE WHEN: the user is about to send a payment / payout / refund and wants to triage risk first, asks "is this IBAN safe to pay?", asks for sanctions screening, asks if a SEPA Instant transfer will succeed, or needs a numeric risk score for an internal payment-approval workflow. NOT A REGULATED AML/CFT PRODUCT — informational triage only. For regulated screening use Refinitiv, Acuris, or ComplyAdvantage. CHECKS: IBAN validity + sanctions (OFAC list, FATF jurisdictions) + SEPA Instant reachability + VoP (EU 2024/886) participant. RETURNS: the full validate enrichment plus a compliance object with risk_score (0-100, 0 = safest), risk_level (low/medium/elevated/high/critical), sanctions matched_lists + fatf_status, reachability, vop status, and flags[] (e.g. sanctioned_country, fatf_grey_list, emi_issuer, no_vop).

Input parameters:

- `iban` (string, required): IBAN to check

Output parameters:

- `bank_code_check` (object)
- `bic`
- `compliance` (object)
- `cost_usdc` (number)
- `country` (object)
- `error` (string)
- `error_detail` (string)
- `iban` (string)
- `issuer` (object)
- `meta` (object)
- `next_steps` (array): Ordered advice derived from THIS result: what blocks a payment first, what merely enriches it after. Branch on `code`, never on the prose. `because` names the field that produced the step so the advi…
- `risk_indicators` (object)
- `sepa` (object)
- `valid` (boolean)

### `lookup_ch_clearing` (~267 tokens)

Swiss Clearing Lookup

Resolve a Swiss BC-Nummer / IID (1 to 5 digits) into the underlying institution. USE WHEN: the user mentions a Swiss bank by BC-Nummer or IID, pastes a CH or LI IBAN clearing code, asks routing details for a Swiss instant transfer (SIC, euroSIC), asks about QR-bill QR-IID resolution, or needs to classify a Swiss financial institution (bank vs PFS vs SIC-only participant). THE DEEPEST SWISS CLEARING DATA IN ANY PUBLIC API — full SIX BankMaster payment-rail participation (SIC, RTGS CHF, Instant Payments CHF, euroSIC, LSV+/BDD) plus QR-IID allocation, not just a name lookup. BACKED BY: 1,100+ SIX BankMaster entries (Swiss official source, refreshed monthly). RETURNS: institution { name, type, iid_type, headquarters_iid }, address, bic, payment_services { sic, rtgs_chf, instant_payments_chf, eurosic, lsv_bdd_chf, lsv_bdd_eur }, sic_iid, qr_iid, valid_on. Only relevant for CH and LI accounts.

Input parameters:

- `iid` (string, required): Swiss IID (1-5 digit number)

Output parameters:

- `address` (object)
- `bic`: BIC if mapped.
- `cost_usdc` (number)
- `error` (string)
- `found` (boolean)
- `iid` (string): Normalized 5-digit BC-Nummer.
- `institution` (object)
- `message` (string)
- `note` (string)
- `payment_services` (object)
- `qr_iid`: QR-bill enabled IID.
- `redirected_from` (string)
- `sic_iid`
- `valid_on` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/cammac-creator-ibanforge/api#diagnostics

## Score history

- 2026-08-03: 78
- 2026-08-02: 77
- 2026-08-01: 77
- 2026-07-31: 76
- 2026-07-30: 73
- 2026-07-29: 72
- 2026-07-28: 72
- 2026-07-27: 72
- 2026-07-26: 71

## Links

- Remote endpoint: https://api.ibanforge.com/mcp
- Repository: https://github.com/cammac-creator/ibanforge
- Website: https://ibanforge.com/
- Changelog RSS feed: https://verifymcp.io/servers/cammac-creator-ibanforge/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/cammac-creator-ibanforge/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/cammac-creator-ibanforge/api