The IBAN-Test MCP server connects AI clients and agents with validated tools for IBAN validation, IBAN generation, BIC validation and bank account validation.
This FAQ explains what MCP does at IBAN-Test, which credentials are needed and when API quota is used. For classic integrations without an AI client, use the IBAN-Test API.
No. IBAN-Test does not provide a separate AI. It provides validated tools for AI clients and agents. The AI client calls these tools through MCP in a structured way.
IBAN, BIC and bank account results come from the IBAN-Test API, not from an AI guess. This matters when payment data is processed in emails, forms, workflows or back-office processes.
Yes. When an AI client validates an IBAN, checks a BIC, validates a bank account or generates an IBAN through MCP, this uses one API request.
Checking your current usage with ibantest_api_usage does not use an API request. It only shows how much quota has already been used.
Use the same API token that you use for the REST API. Send the token as a Bearer token to the MCP endpoint.
https://www.iban-test.eu/mcp
Authorization: Bearer YOUR_API_TOKENYou can find your API token in the dashboard after login.
The IBAN-Test MCP server provides structured tools for AI clients and agents:
ibantest_iban_validate - validate an IBANibantest_iban_generate - generate an IBANibantest_bank_account_validate - validate bank code and account numberibantest_bic_validate - validate a BICibantest_api_usage - show API usageThis lets an AI workflow validate payment data without implementing bank data logic itself.