VIES VAT Validator MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | No | Apify token used as a Bearer token in the Authorization header when connecting to the remote Streamable HTTP endpoint (e.g. https://neeenja--vies-vat-validator-mcp.apify.actor/mcp). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_vatB | 校验 VAT / 税务识别号：先做免费本地格式校验，再按需调用欧盟官方 VIES 接口核验真实性。Validate a VAT number: free local format check, then optional live VIES verification. |
| check_vat_formatA | 纯本地 VAT 号格式校验（零网络、零成本）：判断号码形态是否符合该国规则。Free local format-only check (no network). |
| list_supported_countriesA | 返回支持 VAT 校验的国家列表：代码 + 母语名 + 当地 VAT 叫法（如 USt-IdNr. / Partita IVA / btw-nummer）+ 中英名。List VIES-supported countries with native name and local VAT term. |
| get_error_codesB | 返回完整的中英双语 VAT 校验错误码表。Return the full bilingual error-code table. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| vat_compliance_guide | 跨境电商 VAT 合规校验步骤指引 / Cross-border VAT compliance check guide |
| explain_vat_result | 解读一次 VAT 校验结果 / Explain a VAT validation result |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| error-codes | Bilingual VAT error-code table (JSON) |
| supported-countries | VIES-supported countries (JSON) |
| spec | Service metadata (JSON) |
TDQS
Scored across 4 tools
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.
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.
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.
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.