ibangen-mcp
Related Servers
Alternatives to ibangen-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceIBAN validation, extraction, format specs, and BIC/SWIFT lookup tools for AI assistants, backed by ibanchecker.cash. Covers 90 countries; no IBAN data is stored.547 npmMIT
- AlicenseAqualityAmaintenanceIBAN 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.13515 npm3MIT
- FlicenseNot gradedqualityBmaintenanceValidates International Bank Account Numbers (IBANs) through a Cloudflare-hosted MCP server, enabling agents to check IBAN validity via natural language.-
- AlicenseAqualityDmaintenanceVerified 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.424 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to audit EU payment runs offline—validating IBANs, SEPA character sets, VAT numbers, and control sums—without uploading any data.147 npmMIT
- FlicenseAqualityCmaintenanceEuropean 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
Scored across 3 tools
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.
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.
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.
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.