OpenIBAN MCP — validate an IBAN's checksum + bank code and resolve the
Part of Pipeworx — an MCP gateway connecting AI agents to 1679+ live data sources.
| Tool | Description |
|---|---|
validate_iban |
Validate an IBAN: check its checksum and (where supported) its bank code, and resolve the bank name, BIC, and city. Returns whether the IBAN is structurally valid plus bank details when available. Best coverage for EU/DACH banks (DE, NL, BE, CH, AT, LU); for other countries the checksum is still validated but bank details may be empty. IBANs with spaces are accepted (e.g. "DE89 3704 0044 0532 0130 00"). |
suggest_iban |
Suggest corrected IBANs for a possibly-mistyped IBAN. Returns a list of candidate IBANs with validity and bank name/BIC. Coverage is limited; if no suggestions are available this returns an error field. |
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"openiban": {
"url": "https://gateway.pipeworx.io/openiban/mcp"
}
}
}tools/list at https://gateway.pipeworx.io/openiban/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1679+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
curl -X POST https://gateway.pipeworx.io/v1/tools/validate_iban \
-H 'Content-Type: application/json' \
-d '{"iban":"DE89 3704 0044 0532 0130 00"}'No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/validate_iban. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"openiban": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-openiban"]
}
}
}Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-openibanIt speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Openiban data" })
The gateway picks the right tool and fills the arguments automatically.
MIT