IBAN Validator checks an IBAN's mod-97 checksum, its length and format for the country, and national check digits where the country defines them. It returns whether the IBAN is valid, the country and the reasons it fails. Paid plans add the bank code, branch code and account number, the correct check digits and the SEPA flag.
Let an agent call IBAN Validator to confirm an input is real and safe before it writes a record, sends a message, or completes a task — grounding the decision in a verifiable check.
Wire ibanvalidator into an agent pipeline so risky inputs are flagged and traced, not passed through on the model's hunch.
Each verdict the agent relies on carries IBAN Validator as its source, so a reviewer can see exactly what was checked.
Point your agent framework at the VerveContext endpoint. Every enabled source — this one included — becomes a tool the model can call. No per-source plumbing.
{
"mcpServers": {
"vervecontext": {
"url": "https://api.vervecontext.com/v1/mcp",
"headers": { "x-api-key": "vc_live_••••" }
}
}
}Each call returns structured fields your agent can read.
ibanisValidformattedcountryCodecountryNamecheckDigitsexpectedLengthlengthHow to ground an agent in it over MCP.
Same data, same VerveContext account, same credit balance — one key works on all of them.
