Skip to main content
Glama
qinisolabs

veridigit

by qinisolabs

Related Servers

Alternatives to veridigit

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      The deterministic fact-verification layer for AI agents. Validates the structured facts an agent emits — IBANs, payment cards, VAT and national tax IDs, crypto and bank addresses, domains, emails, phone numbers, securities and academic identifiers, plus dates, currencies and holidays — against checksums and curated authoritative data, not guesses.
      56
      1
      Apache 2.0
    • A
      license
      A
      quality
      A
      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
      77 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to validate IBANs, generate synthetic checksum-valid test IBANs, and look up bank registry records by BIC or domestic identifier, with optional paid capabilities for bank, BIC, and SEPA Instant/VoP reachability.
      3
      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
      226 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to run deterministic API validation and UI DOM checks, verifying HTTP status codes, JSON schema fields, and page elements with programmatic proof instead of LLM guesswork.
      MIT

    TDQS

    A4.6/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool validates a completely different type of identifier (card, IBAN, ISBN, VIN) with no overlap in purpose. An agent can clearly distinguish which tool to use based on the entity type.

    Naming Consistency5/5

    All tools follow a consistent 'validate_<entity>' pattern using snake_case, making the naming predictable and uniform.

    Tool Count5/5

    Four tools is an appropriate number for a validation-focused server covering common but distinct identifier types. Each tool serves a clear and necessary purpose without being excessive.

    Completeness4/5

    The set covers major identifier validations (payment, banking, book, vehicle). Minor gap: no validation for other common identifiers like email or phone, but the scope is coherent and well-defined.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues