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.558 npmMIT
- AlicenseAqualityBmaintenanceIBAN 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.13491 npm3MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to validate IBANs and bank codes across multiple countries, verify payee names against account holders, and screen names against major global sanctions lists. It connects clients to a hosted banking reference-data service over OAuth-authenticated HTTP.MIT
- FlicenseNot gradedqualityBmaintenanceValidates International Bank Account Numbers (IBANs) through a Cloudflare-hosted MCP server, enabling agents to check IBAN validity via natural language.-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to validate IBAN, BIC, EU VAT, GTIN/EAN/UPC, and ISBN codes offline through format and check-digit checks, and retrieve related metadata.26,592 npmMIT
- 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.444 npmApache 2.0
TDQS
Scored across 6 tools
Most tools target distinct resources, but lookup_us_routing_number and validate_us_routing_numbers overlap heavily—both check US routing numbers against the same registry, differing mainly in singular vs. batch input and naming. lookup_bank and lookup_us_routing_number are also both registry lookups that an agent could plausibly confuse when choosing a tool.
All tools follow a verb_noun pattern (validate_*, lookup_*, generate_*), which is predictable. However, qualifier ordering is inconsistent (generate_test_ibans vs. generate_us_test_accounts) and singular/plural forms vary across the related US routing tools.
Six tools is well-scoped for IBAN validation, test data generation, US routing lookups, and bank intelligence. Each tool has a distinct role and the set is neither thin nor bloated.
The surface covers validation, generation, and lookup for the core IBAN and US routing domains, including test data workflows. Minor gaps exist, such as no dedicated BIC validation or country/list support tool, but agents can work around these via existing endpoints.