# IBANforge Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## IBANforge

Validate IBANs and check the bank behind them before you pay, with sanctions screening.

- Record: https://musedirectory.ai/connector/ibanforge
- Category: Finance & Bills
- Developer: cammac-creator (https://ibanforge.com?src=mcp-registry)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 953ms, checked 2026-09-28T08:31:24Z
- Endpoint: https://api.ibanforge.com/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-09-25T00:31:07Z)
- Source: Found in the official MCP Registry (io.github.cammac-creator/ibanforge) https://registry.modelcontextprotocol.io/v0/servers?search=io.github.cammac-creator%2Fibanforge

Validates IBANs across 89 countries and enriches them with bank details, BIC codes, and compliance data. Checks whether recipient banks are reachable on SEPA rails and screens against OFAC, EU and UN sanctions lists. Supports Swiss QR-bills and structured payment references.

Example request: "Check if this IBAN is valid and whether the bank is under sanctions before I send a payment."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use IBANforge to help me. It is a free service with an MCP server at https://api.ibanforge.com/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- validate_iban: Verify whether an IBAN from any of the 89 IBAN countries is valid AND enrich it with bank, compliance and routing data. USE WHEN: the user mentions an IBAN, asks to validate an IBAN and identify the issuing bank, asks to detect a typo in an IBAN, asks who the bank is behind an IB
- batch_validate_iban: Validate up to 100 IBANs in a single call. Paid per call in USDC via x402, it costs $0.002 per IBAN instead of $0.005 per validate_iban call; on an API key or a credit pack each IBAN uses one request or credit, the same as one validate_iban call. USE WHEN: the user pastes a list 
- lookup_bic: 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 
- check_compliance: Run a pre-flight compliance triage 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 whether the payee's bank or its country is under sanctions, asks if a SEPA Instant tran
- validate_payment_reference: Validate a structured payment reference and, when an IBAN is supplied, decide whether the two may legally travel together. USE WHEN: assembling a payment instruction from an invoice, a QR-bill or a remittance advice; whenever a Swiss IBAN and a reference appear together (the pair
- check_swiss_qr_bill: Check a Swiss QR-bill payload, the text a QR-bill's code carries (starts with SPC), rule by rule, each finding citing the SIX document it comes from. USE WHEN: an agent, an ERP or an accounting tool holds a scanned or generated QR-bill and must know before paying or issuing it wh
- check_postal_address: Check a structured ISO 20022 postal address against a payment rail's published address rules, rule by rule, each verdict citing the document it comes from. USE WHEN: assembling a payment instruction (pain.001, a Fedwire message, a T2 transfer) with a creditor or debtor address, t
- lookup_ch_clearing: 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 resolut
- send_feedback: Report a problem or a need directly to the IBANforge operators: incorrect validation result, stale or missing BIC/bank data, latency, or anything blocking you from using or PAYING for the service (missing network, unclear pricing, quota shape). USE WHEN: a result looks wrong, dat
- request_api_key: Start the process that gives this session its own free IBANforge API key, without any e-mail address and without leaving your conversation. USE WHEN: you used up the free allowance, a call answers 402, or you are about to run more than a handful of validations. WHAT YOU MUST DO W
- poll_api_key: Collect the API key once a human has approved the request opened by request_api_key. USE WHEN: you have called request_api_key and shown the code to your human. HOW TO CALL IT: leave `device_code` empty to reuse the last request from this session. The server usually waits up to t

Screening checks:
- MCP handshake: pass (Answered in 516ms)
- Domain against threat feeds (Cloudflare security DNS): pass (api.ibanforge.com, ibanforge.com not flagged)
- Published packages against the OSV malicious-package database: pass (No malicious-package advisories)
- Hidden instructions or invisible characters in tool text: warn (validate_iban: Unusually long tool description; request_api_key: Tool text tells the model to take extra steps)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (Domain registered 176 days ago)
- AI review of purpose and tool behavior: pass (No concerns)