io.github.cammac-creator/ibanforge

NPM · IBANFORGE-MCP · 2 COMPONENTS · SCANNED AUG 3

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

Available components

remote · api.ibanforge.com 78 npm · ibanforge-mcp 66

+24 this week 66 66 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security86

No malware found by supply-chain analysis.Pass
Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
No install/post-install scripts declared.Pass
Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial

Provenance & Transparency45

Source repository is publicly reachable at the declared URL. View diagnostics → Pass
Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
Clear OSI-approved license (MIT).Pass
Actively maintained (last published 3 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability61

AI-judged instruction clarity (excellent).Pass
Context-footprint check failed: tool/resource definitions use about 1364 tokens (~272/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 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
Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · ibanforge-mcp

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add cammac-creator-ibanforge -- npx -y ibanforge-mcp

# add to Codex CLI

codex mcp add cammac-creator-ibanforge -- npx -y ibanforge-mcp

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cammac-creator-ibanforge": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "ibanforge-mcp"
      ],
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add cammac-creator-ibanforge --command npx --arg -y --arg ibanforge-mcp

# ~/.hermes/config.yaml

mcp_servers:
  cammac-creator-ibanforge:
    command: "npx"
    args: ["-y", "ibanforge-mcp"]

// mcp.json

{
  "mcpServers": {
    "cammac-creator-ibanforge": {
      "command": "npx",
      "args": [
        "-y",
        "ibanforge-mcp"
      ]
    }
  }
}

Changelog

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.

3 Aug 26 +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.
2 Aug 26 +22
- Stability: 0.20 → unverified ▼ security
- Provenance: fail → unverified ▼ security
- Install scripts: pass → unverified ▼ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Maintenance: pass → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- License: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- First check of Schema quality: unverified functional
- Licence: MIT functional
1 Aug 26 −10
- Known CVEs: partial → unverified ▼ security
- Dependency health: partial → unverified ▼ functional
31 Jul 26 +29
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- Package version: 1.3.3 → 1.4.1 functional
27 Jul 26 42

First indexed and scored.

Show 2 earlier entries Hide earlier entries

Diagnostics

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 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 94 packages

94 packages in the resolved dependency tree · 94 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 5 exposed · ~1,364 tokens

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.

Tool Tokens

batch_validate_iban ~188

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, cost_usdc }. COST: 0.002 USDC per IBAN (e.g. 10 IBANs = 0.02, 100 IBANs = 0.20).

Input Output Examples

Name	Type	Req	Description
ibans	array	yes	Array of IBAN strings (1 to 100 entries).

Name	Type	Req	Description
cost_usdc	number	—	Actual USDC charged for this call.
count	number	yes	Number of IBANs processed.
results	array	yes	One entry per input IBAN, in the same order. Same shape as validate_iban output.
valid_count	number	yes	How many were valid.

No examples provided.

check_compliance ~249

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. SCOPE: sanctions screening is at the BANK (BIC8) level only — it does NOT screen the beneficiary/account-holder name. CHECKS: IBAN validity + bank sanctions (OFAC) + FATF grey/black list + SEPA Instant reachability + VoP (EU 2024/886) participant flag. RETURNS: the validate_iban fields PLUS a nested compliance { sanctions, reachability, vop, risk_score (0-100), risk_level, flags[] }. COST: 0.02 USDC.

Input Output Examples

Name	Type	Req	Description
iban	string	yes	IBAN to run the compliance check against.

Name	Type	Req	Description
bic	object	—	—
compliance	object	yes	The compliance bundle. Read the score at compliance.risk_score / compliance.risk_level.
cost_usdc	number	—	—
country	object	—	—
iban	string	yes	—
issuer	object	—	—
meta	object	—	Scope + freshness disclosure. Read this before trusting the result.
risk_indicators	object	—	—
sepa	object	—	—
valid	boolean	yes	—

No examples provided.

lookup_bic ~244

Resolve a BIC / SWIFT code into the underlying bank: name, country, city, LEI, address. 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: 121k+ BIC entries (38k+ LEI-enriched via GLEIF; additional rows from SWIFT directory, Bundesbank, SIX, NBP, EBA Step2 SCT), refreshed monthly. RETURNS: bank_name, country, country_name, city, lei, address (if available). COST: 0.003 USDC.

Input Output Examples

Name	Type	Req	Description
bic	string	yes	BIC / SWIFT code, 8 or 11 alphanumeric characters. Example: "UBSWCHZH80A" (UBS Switzerland) or "DEUTDEFF" (Deutsche Bank Frankfurt).

Name	Type	Req	Description
address	object	—	Registered head-office address object (present when available).
address_available	boolean	—	—
bic	string	yes	Echo of the input, normalized to uppercase.
bic11	string	—	11-char form including branch.
bic8	string	—	8-char form (institution-level).
city	string	—	—
country	object	—	—
found	boolean	yes	—
institution	string	—	Bank legal name.
lei	string	—	Legal Entity Identifier (ISO 17442) if available.
valid_format	boolean	yes	—

No examples provided.

lookup_ch_clearing ~295

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. COST: 0.003 USDC. Only relevant for CH and LI accounts.

Input Output Examples

Name	Type	Req	Description
iid	string	yes	Swiss IID / BC-Nummer (1 to 5 digits, leading zeros stripped). Example: "230" for UBS Switzerland AG.

Name	Type	Req	Description
address	object	—	—
bic	string	—	BIC if mapped.
found	boolean	yes	—
iid	string	yes	5-digit zero-padded BC-Nummer.
institution	object	—	—
payment_services	object	—	—
qr_iid	string	—	QR-IID allocation, null when none.
sic_iid	string	—	—
valid_on	string	—	—

No examples provided.

validate_iban ~388

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, country_risk, test_bic, sepa_reachable, vop_coverage }, and for CH/LI: clearing { iid, name, type, sic, qr_iid }. COST: 0.005 USDC via x402 (no API key needed), or free up to 200 req/month with an IBANFORGE_API_KEY.

Input Output Examples

Name	Type	Req	Description
iban	string	yes	IBAN to validate. Spaces and lowercase are accepted. Example: "CH10 0023 0000 0000 1234 5" or "de89370400440532013000".

Name	Type	Req	Description
bban	object	—	—
bic	object	—	Resolved BIC/SWIFT (when BBAN→BIC mapping exists). null if unresolved.
check_digits	string	—	—
clearing	object	—	Swiss clearing data when country is CH or LI (null otherwise).
country	object	—	—
formatted	string	—	IBAN with 4-char groups for display.
iban	string	yes	Normalized IBAN (uppercase, no spaces).
issuer	object	—	—
risk_indicators	object	—	Country + issuer risk signals. Use these instead of a single composite score.
sepa	object	—	—
valid	boolean	yes	—

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

27 Jul 3 Aug