Skip to main content
Glama
giltiq

Giltiq MCP Server

by giltiq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to Giltiq MCP Server

No user-submitted related servers found.

    Related Servers

    • EU VAT Validator (VIES)

      apifymcpfactory-droid
      F
      license
      Not graded
      quality
      B
      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.
      -

    • vies-smoother

      Lucrumist
      A
      license
      Not graded
      quality
      C
      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

    • VAT Validator MCP

      OjasKord
      A
      license
      Not graded
      quality
      B
      maintenance
      Validates EU, UK, and AU VAT numbers against live sources and uses AI pattern analysis to detect invoice fraud.
      149 npm
      MIT

    • honest-vies-mcp

      bartosz-kuc
      A
      license
      A
      quality
      B
      maintenance
      Local MCP server for validating EU VAT numbers using the official VIES API. Enables AI to check VAT validity and optionally retrieve consultation numbers for legal proof.
      2
      MIT

    • mcp-vies-eu

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Validates EU VAT numbers using the European Commission's VIES system, enabling VAT number checks through natural language queries via the Pipeworx gateway.
      1 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.8/5.0

    Scored across 2 tools

    Disambiguation4/5

    The two tools have clearly distinct purposes: one validates VAT IDs, the other checks upstream API status. There is minor potential overlap in that both relate to the VAT validation domain, but the actions are unambiguous and not confusable.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern (validate_vat_id, check_api_status). The naming style is uniform snake_case with descriptive verbs, making the pattern predictable and clear.

    Tool Count2/5

    With only 2 tools, the server feels thin for a VAT validation service. A typical complete server would include additional operations like fetching supported country codes, retrieving detailed validation history, or parsing raw responses, making this surface minimal.

    Completeness2/5

    The server provides core validation and a status-check companion, but lacks obvious supporting operations such as listing supported jurisdictions, retrieving cached/failed validations history, or handling bulk validations. The domain is narrow and mostly covered, but agents cannot perform related common tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources