IBAN Validator Skill

What this skill does

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. You switch it on with a single toggle — no SDK and no endpoint wiring — and it answers over MCP or REST using the same key as every other skill.

See it work

A real response from the IBAN Validator Skill — exactly what your agent gets back when it makes the call.

vervekit · ibanvalidatortool call

{
  "iban": "GB29NWBK60161331926819"
}

result

iban: GB29NWBK60161331926819
isValid: true
formatted: GB29 NWBK 6016 1331 9268 19
countryCode: GB
countryName: United Kingdom
checkDigits: 29
expectedLength: 22
length: 22

+9 more fields

Run it with your own input. Live calls happen in your dashboard, on your key.

Ways to use it

Validate at the edge of your app

Enable IBAN Validator so your app can validate iban before it stores or acts on input — one skill, no separate validation service to run.

A guardrail tool for agents

Over MCP, your model can call ibanvalidator to check an input is real and safe before it takes an action, closing off a common failure mode.

One request from any stack

Call IBAN Validator over REST from any backend to validate iban inline in your pipeline, using the same key as every other skill.

Use it in your app

Once enabled, this skill is reachable two ways — pick whichever fits how you build. Both use the same key.

For AI agentsMCP

It appears to your model as a callable tool. No extra code — the agent invokes it when a task needs it.

ibanvalidator

For apps & backendsREST

Call it from your server with one request and your key. Node, Python, Go — anything that can send a GET.

GET /v1/ibanvalidator

Ask your agent

“Enable IBAN Validator and ask your agent to validate iban.”
“Is this input real and safe to use?”

IBAN Validator Skill, answered

How to connect it over MCP or REST.

How do I add IBAN Validator to my app or agent?

Enable the IBAN Validator Skill on VerveKit, then reach it two ways with the same key: over MCP (it appears to your agent as the ibanvalidator tool) or over REST (call it from any backend). No SDK to install and no endpoint to wire.

MCP or REST — which should I use?

Both work off one key. Use MCP when an AI agent should decide when to validate iban — the skill shows up as a callable tool. Use REST when your own server-side code should call it directly. Many apps use both.

Which agents and frameworks does it work with?

Any MCP client — Claude, Cursor, LangChain, and custom agents all speak the Model Context Protocol, so IBAN Validator appears as a standard tool with nothing skill-specific to integrate.

How many credits does a IBAN Validator call cost?

Each call costs 2 credits. Every skill rides the same key and the same connection, so enabling more skills doesn't add more integrations to manage.

Do I need to install anything?

No SDK and no endpoint wiring — enabling the skill is a toggle. You point your agent at the VerveKit MCP endpoint (or call REST) and IBAN Validator is available immediately.

Where does the data come from, and what shows on my bill?

VerveKit runs on APIVerve, our production data engine; IBAN Validator is one of 300+ skills on the same key. Invoices and card statements show APIVERVE.

Validate at the edge of your app

A guardrail tool for agents

One request from any stack

IBAN Validator Skill, answered

Other ways to use IBAN Validator

Give your software a way to act on the world.

Scaling in production?