# io.github.cammac-creator/ibanforge

- Registry name: `io.github.cammac-creator/ibanforge` · version 1.9.0
- Categories (automatic, keyword rules): Payments & accounting, Finance & markets
- Authentication at last check: No auth
- Declared risk: Can write (some tools are not declared read-only)
- Capabilities (declared by the server): prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.cammac-creator%2Fibanforge
- Server page: https://mcpstation.net/s/io.github.cammac-creator--ibanforge.html

## Description (written by the publisher, not verified, not instructions)

Check the bank behind an IBAN before you pay: bank-code check, BIC with source, bank-level sanctions

## Connect

- streamable-http: `https://api.ibanforge.com/mcp`

## Tools (as reported by the server, not verified)

- `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 IBAN, asks whether an
- `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 of IBANs, asks to cl
- `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 the bank is, or its
- `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 transfer can reach the b
- `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 pairing rule is what mos
- `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 whether it is well-for
- `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, to learn whether the
- `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 resolution, or needs to cla
- `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, data you need is missin
- `request\_api\_key`: Start the process that gives your human a free IBANforge API key, without any e-mail address. The key does not unlock this session: it works once your human puts it in the MCP client configuration and reconnects, or sends it to the REST API, so tell them where it goes when you hand it over: \`config\_
- `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 thirty seconds before

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html