Skip to main content
Glama

Related Servers

Alternatives to ibangen-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      47 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      IBAN validation across 89 countries, BIC/SWIFT and Swiss clearing lookup, batch validation, payment-reference, postal-address and Swiss QR-bill checks for AI agents. Connect via MCP or the REST API. Includes free quotas, paid credits and a Pro subscription. SEPA and country-risk indicators support payment-data checks; they do not confirm account ownership or replace beneficiary AML/KYC screening.
      13
      515 npm
      3
      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.
      -
    • 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
      24 npm
      Apache 2.0
    • F
      license
      A
      quality
      C
      maintenance
      European business compliance suite for AI agents — 28 tools covering tax ID validation (PT, ES, FR, DE, IT, UK, NL), IBAN verification, EU VAT rates, invoice requirements, e-invoicing rules, payment terms, labor calendar helpers, VAT breakdown calculations and invoice schema validation for 18+ European countries.
      28
      -

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation4/5

    Each tool has a distinct primary purpose: registry lookup by BIC/identifier, IBAN validation, and synthetic test data generation. The only minor overlap is that validate_ibans also returns bank/BIC data on paid plans, which slightly blurs the line with lookup_bank, but the core intents are clearly separable.

    Naming Consistency5/5

    All three tools follow a clean verb_noun snake_case pattern: lookup_bank, validate_ibans, generate_test_ibans. The convention is uniform and self-explanatory with no mixed styles.

    Tool Count4/5

    Three tools is on the lean side but reasonable for a focused IBAN/bank-intelligence utility. Each tool earns its place (validate, lookup, generate), though the surface is thin enough that it borders on minimal.

    Completeness4/5

    Core workflows—validating IBANs, resolving bank records, and generating test data—are covered, giving a coherent lifecycle for the domain. Minor gaps exist, such as IBAN parsing/component extraction or standalone BIC validation, but agents can work around these.