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
validate_ibanValidates one IBAN, including SEPA bank participation.
validate_iban_batchValidates multiple IBANs; each IBAN counts as one API request.
generate_test_ibanGenerates an IBAN from country, bank code and account number.
ibantest_bank_account_validateChecks a German bank code and account number.
ibantest_bic_validateValidates a BIC.
get_usage_infoShows API usage without consuming a validation request.
IBAN validation also returns the bank’s participation in SEPA Direct Debit schemes, checked against the EPC participant registers.
sddCore – SEPA Direct Debit Core; sddB2b – SEPA Direct Debit B2B.
Both schemes are checked independently. confirmed means there is an unambiguous, current register match. unknown means participation could not be confirmed; it does not mean the bank does not support the scheme.
This checks bank participation. It does not confirm account existence or direct debit eligibility, a mandate, or the success of a collection.
Start with free checks, create your API token in the dashboard and connect your MCP-capable client to IBAN-Test.
Frequently asked questions
Find more answers in our MCP FAQ about setup, authentication and API usage.
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 get_usage_info 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:
validate_iban – Validates one IBAN, including SEPA bank participation.validate_iban_batch – Validates multiple IBANs; each IBAN counts as one API request.generate_test_iban – Generates an IBAN from country, bank code and account number.ibantest_bank_account_validate – Checks a German bank code and account number.ibantest_bic_validate – Validates a BIC.get_usage_info – Shows API usage without consuming a validation request.This lets an AI workflow validate payment data without implementing bank data logic itself.
IBAN validation also returns the bank’s participation in SEPA Direct Debit schemes, checked against the EPC participant registers.
sddCore – SEPA Direct Debit Core; sddB2b – SEPA Direct Debit B2B.
Both schemes are checked independently. confirmed means there is an unambiguous, current register match. unknown means participation could not be confirmed; it does not mean the bank does not support the scheme.
This checks bank participation. It does not confirm account existence or direct debit eligibility, a mandate, or the success of a collection.
Bank data validation
IBAN-Test goes beyond checksum-only validation. For these countries, we check the bank identifier against available bank directories and return bank details such as institution, city and BIC when available. See how IBAN validation works.
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 structure and check digits, then use available bank-directory data in payment forms, SaaS products, SEPA workflows and AI agents. Automate through REST or MCP.
MCP Server for AI Agents – Connect AI clients to IBAN validation tools – https://www.iban-test.eu/mcp – API documentation