Skip to main content
Glama
pipeworx-io

mcp-openiban

by pipeworx-io

mcp-openiban

OpenIBAN MCP — validate an IBAN's checksum + bank code and resolve the

Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.

Tools

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.

Related MCP server: veridigit

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "openiban": {
      "url": "https://gateway.pipeworx.io/openiban/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/openiban/mcp returns the tools in the table above plus the shared Pipeworx meta-toolsask_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 1476+ data sources. The only difference is which pack's tools are listed directly; ask_pipeworx reaches all of them from either one.

Using with ask_pipeworx

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.

More

License

MIT

Related MCP Connectors

Related MCP Servers

  • A
    license
    A
    quality
    A
    maintenance
    IBAN validation, BIC/SWIFT lookup, SEPA compliance, issuer classification and risk indicators for AI agents. 39K+ bank entries from GLEIF. Supports 75+ countries.
    11
    127 npm
    3
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    Verified validation of structured identifiers — IBAN, payment cards, ISBN-13 and VIN — for AI agents. Runs the real checksum algorithms (mod-97, Luhn, mod-10, ISO 3779) instead of letting the model guess, and returns structured results with clear errors.
    4
    25 npm
    Apache 2.0
  • A
    license
    A
    quality
    B
    maintenance
    IBAN validation, extraction, format specs, and BIC/SWIFT lookup tools for AI assistants, backed by ibanchecker.cash. Covers 90 countries; no IBAN data is stored.
    5
    23 npm
    MIT
  • F
    license
    Not graded
    quality
    B
    maintenance
    Validates International Bank Account Numbers (IBANs) through a Cloudflare-hosted MCP server, enabling agents to check IBAN validity via natural language.
    -