IBAN-Test MCP Server
Connect AI clients, internal agents and automations to IBAN-Test through the Model Context Protocol (MCP). Validate IBANs, generate IBANs, check BICs and query API usage - without building bank data logic into your AI system.
Why MCP?
AI agents can understand text, extract data from emails and prepare workflows. For valid payment data, they need a reliable tool. The IBAN-Test MCP server makes these checks available as structured tool calls.
AI extracts IBANs from invoices and validates them before passing data to accounting or ERP.
Agents check bank details for suppliers, customers or users during data capture.
Support assistants can validate submitted bank details without implementing sensitive validation logic.
MCP makes IBAN-Test available as a standardized tool for AI clients and automation platforms.
Integration
The MCP access uses Bearer tokens in the header and returns structured responses for controlled tool calls. You can find the token in your dashboard after login.
Endpoint
https://www.iban-test.eu/mcp
Header
Authorization: Bearer YOUR_API_TOKEN
ibantest_iban_validateValidates an IBAN and returns validation details.
ibantest_iban_generateGenerates an IBAN from country code, bank code and account number.
ibantest_bank_account_validateChecks German bank code and account number against bank data logic.
ibantest_bic_validateValidates BIC format and bank data information.
ibantest_api_usageShows current API usage for the authenticated user.
Start with free checks, create your API token in the dashboard and connect your MCP-capable client to IBAN-Test.
Frequently asked questions
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_TOKEN
You 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.
Bank data validation
For these countries, we check IBANs against available bank directories and return bank details such as institution, city and BIC when available.
IBAN syntax check
Check IBANs for a valid structure, correct length and checksum. This helps you catch typos and transposed digits before a payment fails. Additional bank validation against real bank directories is available for the countries listed above.
API and automation
Validate IBANs in payment forms, SaaS products, SEPA workflows and AI agents. Use the REST API for automation or connect AI clients through MCP.
MCP Server for AI Agents - Connect AI clients to IBAN validation tools - https://www.iban-test.eu/mcp - MCP Documentation