Skip to main content
Glama
PanStories

VIES VAT Validator MCP

by PanStories
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to VIES VAT Validator MCP

No user-submitted related servers found.

    Related Servers

    • EU VAT Validator (VIES)

      apifymcpfactory-droid
      F
      license
      Not graded
      quality
      D
      maintenance
      Validates EU and Northern Ireland VAT numbers against the official VIES service, returning validity, company name and address, and distinguishing invalid from unavailable. Supports bulk checking up to 100 VAT IDs.
      -

    • Giltiq MCP Server

      giltiq
      A
      license
      A
      quality
      C
      maintenance
      Validates EU VAT IDs using VIES and Germany's BZSt with automatic failover and legally binding qualified confirmations per §18e UStG, ensuring reliability even when VIES is down.
      2
      4 npm
      MIT

    • vies-smoother

      Lucrumist
      A
      license
      Not graded
      quality
      D
      maintenance
      SLA'd EU VAT number validation for AI agents via VIES, with caching and circuit-breaking to handle flaky upstream, returning valid/invalid/unavailable responses.
      MIT

    • goodvat

      goodvat
      A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to answer tax compliance questions (VAT, sales tax, GST) and validate EU VAT numbers in real time via the VIES registry.
      2
      24 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 4 tools

    Disambiguation4/5

    validate_vat and check_vat_format overlap in that validate_vat includes a local format check, so an agent could wonder which to use. However, the descriptions clearly differentiate them (validate_vat adds live VIES verification, check_vat_format is zero-network/local-only), making the intended split reasonably clear.

    Naming Consistency4/5

    All four names follow a snake_case verb_noun pattern (validate_, check_, list_, get_), which is predictable. The only minor deviation is using two near-synonym verbs (validate vs check) for the two closely related validation tools.

    Tool Count4/5

    Four tools is on the lean side but appropriate for a narrow, single-purpose validator. Each tool maps to a distinct function (validation, format check, country list, error codes), though the count is slightly inflated by the overlapping validate/check pair.

    Completeness4/5

    The surface covers the core lifecycle for VAT validation: format checking, live verification, supported-country discovery, and error-code lookup. Minor gaps exist (e.g. no batch/multi-number validation), but agents can work around these.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources