Skip to main content
Glama
Sirenic MCP server

Sirenic MCP server

Official

Validate EU VAT number (VIES)

validate_eu_vat_number
Read-only

Check an EU VAT number against VIES to confirm supplier validity before invoicing, reverse charging, or paying; returns status, registered details when published, and consultation ID.

Instructions

VAT number check against VIES: use when you only need the tax half of verifying a supplier before payment: confirm that a counterparty's intra-community VAT number really exists before invoicing it, applying the reverse charge or paying it. It is a required check under the French e-invoicing mandate of 1 September 2026 and under the Belgian B2B mandate in force since 1 January 2026. Validates any EU intra-community VAT number against the official VIES service (all member states) and returns valid or invalid, the registered name and address when the member state publishes them, and the VIES consultation identifier as proof. Name and address are served only for a holder that its number's format or its country's register (BE, PL, LV, HR, RO, SE, CZ, DK, FI, FR) proves a legal person; any other holder (natural person, undecided form, missing from its register, or in a state where no register qualifies it: AT, CY, DE, EE, EL, HU, IE, IT, LT, LU, MT, NL, SI, SK, XI) gets neither, the omission counted in ecartes by reason. A register that cannot qualify the holder (down, quota reached, or its local copy not yet built: cause collecte_en_cours) leaves both out as a doubt, says its register and cause in qualification_en_echec, and nothing is cached. A VIES outage (member state down or saturated) returns error 503 amont_indisponible, not charged: retry later; never a false invalid. The response is Ed25519-signed and carries provenance[]: the VIES entry with the date the number was really consulted, never a fabricated one. Paid via x402 ($0.003 in USDC or EURC). When you report a result, cite its citation verbatim.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "vat_number": "<vat_number>"
    },
    "name": "validate_eu_vat_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
vat_numberYesFull VAT number with its 2-letter country prefix and no spaces, e.g. FR27552032534

Output Schema

NameRequiredDescriptionDefault
hintNoHow to settle the quote, present when payment_required is true.
quoteNoThe signable x402 payment requirements when payment_required is true: {x402Version, accepts[]} where each entry carries scheme, network, amount, asset and payTo (USDC and EURC options at the same numeric amount). Sign one entry and call again with `x_payment`.
resultatNoThe endpoint's JSON response when payment_required is false. Paid responses carry `source`, `disclaimer` and an Ed25519 signature, and every paid JSON response carries a `provenance` array (all tools since 2026-09-06): one entry per block served, with the official register, licence, version, `empreinte_sha256` (full snapshots), `as_of` date and `precision_as_of` (what that date means), plus the common per-block envelope: `etat` in a closed list (servi, absence_mesuree, absence_non_conclusive, partiel, perime, indisponible, sans_objet), `motif` when unavailable, `age_jours` (only for publication or ingestion dates), `couverture` (complete / partielle / non_mesurable with its measure) and `confiance` in bands (faible / moyenne / forte, only where a measure grounds it, never averaged across blocks). Read the states before the numbers: an absence_non_conclusive, indisponible or partiel block is never « nothing to report »; only absence_mesuree asserts an absence. Register codes: GET /v1/provenance/registres ; states, closed lists and reading rules: GET /v1/lecture (both free). The PDF tools carry no JSON envelope (the PDF report prints it).
free_tierNoFree API key offer for this tool, present with a quote.
payment_requiredYesTrue when this response is an x402 payment quote instead of data: settle one of the quote's `accepts` options and call the tool again with `x_payment`.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the read-only and open-world annotations, it discloses many important behaviors: conditional name/address returns by country and holder type, fallback behavior with ecartes and qualification_en_echec, a 503 amont_indisponible error for VIES outages, no caching on qualification failure, Ed25519-signed responses, provenance, x402 payment cost, and citation requirements. These details materially help an agent understand what will happen and how to report results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the purpose and usage context, but it is a long, dense paragraph. The detailed country lists, legal mandate dates, and failure taxonomy are useful but not all necessary for deciding to invoke the tool, so it is somewhat overlong despite being informative.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the external VIES dependency, one required parameter, and the presence of an output schema, the description is complete enough for correct invocation. It covers return conditions, error handling, payment, provenance, and reporting requirements, so an agent has the context needed to call and interpret the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and the single vat_number parameter is fully documented in the schema with its required country prefix, pattern, and example. The description adds little parameter-level detail beyond saying it validates any EU intra-community VAT number, so the baseline of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: validating an EU intra-community VAT number against VIES. It also distinguishes the scope from broader supplier verification by saying to use it 'when you only need the tax half of verifying a supplier before payment.'

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear usage context: confirming a counterparty's VAT number before invoicing, applying reverse charge, or paying, and notes legal mandates that make this check required. It implies an alternative by scoping this to 'only need the tax half,' but it does not explicitly name sibling tools or state when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools