Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

VAT.SUPPORT

REMOTE · VAT.SUPPORT

EU & UK statutory VAT compliance, VIES validation, ViDA e-invoicing & Art. 196 reverse-charge.

Available components

61 Trust /100

Last scanned (2 hours ago)

Scores higher than 43% of remote servers

Reachable. Last reached 5 Nov 2026.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security66
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1032 tokens (~147/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 89% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "reverse_charge_certificate" implies "charge" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 4 Nov 26 61

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://vat.support/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=vat.support CN=YE2,O=Let's Encrypt,C=US 16 Sept 2026 15 Dec 2026 ECDSA 256 ECDSA-SHA384 6adb1860939bf686361f8b8e8336a2eb3f5
SANs: vat.support
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of vat.support. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
support. present 59704 8 Verified
vat.support. present 55184 8 Verified
vat.support. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy frame-ancestors 'self' https://vat.support https://*.vat.support
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://vat.support/api/mcp Verified 200
http (plaintext) http://vat.support/api/mcp HTTPS enforced 308 https://vat.support/api/mcp
MCP tools · 7 exposed · ~952 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
intrastat_threshold_check ~191

Evaluate statutory Intrastat reporting obligations for cross-border physical goods movement (dispatches and arrivals) across all 27 EU Member States and Northern Ireland.

NameTypeReqDescription
annual_arrivals_eurnumber–Total annual value of goods received from other EU Member States in EUR
annual_dispatches_eurnumber–Total annual value of goods shipped to other EU Member States in EUR
arrivals_unsureboolean–Set to true if arrival volume is unknown
business_countrystringyesTwo-letter ISO country code of establishment (e.g. DE, FR, PL, IT, ES)
business_subdivisionstring–Optional regional overlay (pass 'NI' for Northern Ireland)
dispatches_unsureboolean–Set to true if dispatch volume is unknown
languagestring–Response language: en, ru, es, zh-CN

No output schema declared.

No examples provided.

reverse_charge_certificate ~165

Generate an EU Art. 196 reverse-charge eligibility verdict for a B2B service invoice between two EU Member States. Validates the customer's VAT ID via VIES and returns a printable certificate. Returns INELIGIBLE for same-country, non-EU, or invalid VAT cases.

NameTypeReqDescription
customer_countrystringyesCustomer ISO-3166-1 alpha-2 (e.g. 'IT')
customer_vat_idstring–Customer VAT identifier including country prefix (e.g. 'IT12345678901')
service_typestring–Type of service: professional_services | digital_services | transport | telecom | event_admission
supplier_countrystringyesSupplier ISO-3166-1 alpha-2 (e.g. 'DE')

No output schema declared.

No examples provided.

vat_compliance_full ~185

Run the full 10-question VAT compliance gap analysis. Returns compliance score (0–100), risk band, itemised findings with Article citations, and source verification per finding.

NameTypeReqDescription
answersobjectyesQ1..Q10 answers. Q1=ISO country, Q2=array of supply types, Q3=B2B|B2C|MIXED, Q4=array of countries, Q5A=annual cross-border B2C revenue in EUR (numeric; legacy strings under_10k/over_10k/unsure still…
languagestring–en, ru, es, zh-CN

No output schema declared.

No examples provided.

vat_number_check ~66

Validate a single EU/UK VAT identifier against VIES (EU) or HMRC (UK). Returns name + address when available.

NameTypeReqDescription
vat_idstringyesFull VAT identifier including country prefix (e.g. 'DE123456789' or 'GB123456789')

No output schema declared.

No examples provided.

vat_rate_lookup ~63

Look up the applicable VAT rate for a country (and optional rate type), sourced from the EU TEDB (Taxes in Europe Database).

NameTypeReqDescription
countrystringyesISO-2 country code
rate_typestring–Defaults to 'standard' if omitted

No output schema declared.

No examples provided.

vat_registration_check ~103

Determine whether a business needs to register for VAT in a given country, given customer type and annual revenue.

NameTypeReqDescription
annual_revenue_eurnumber––
countrystringyes–
customer_typestring––
sale_countriesarray–Other countries where the business sells
supply_typesarray–Supply mix — `goods`, `digital_services`, `professional_services`, etc. Defaults to `[goods]` when omitted.

No output schema declared.

No examples provided.

vida_mandate_check ~179

Determine EU VAT in the Digital Age (ViDA) and statutory B2B e-invoicing mandates, implementation phases (P1–P5), platform economy deemed-supplier rules, and digital reporting deadlines.

NameTypeReqDescription
business_typestring–Primary business model
cross_border_b2bboolean–Whether the business engages in cross-border B2B sales within the EU (triggers mandatory e-invoicing & real-time digital reporting)
is_platformboolean–Whether the business operates an online digital platform or intermediation service
languagestring–Response language: en, ru, es, zh-CN
passenger_transportboolean–Whether the platform facilitates road or passenger transport
short_term_accommodationboolean–Whether the platform facilitates short-term property/room rentals

No output schema declared.

No examples provided.

Install

How do I install the VAT.SUPPORT MCP server?

VAT.SUPPORT is a hosted endpoint at https://vat.support/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · vat.support

# add to Claude Code
claude mcp add --transport http vmalyshev1-vat-support 'https://vat.support/api/mcp'
Common questions

What is the VAT.SUPPORT MCP server?

VAT.SUPPORT is an MCP server listed in the public MCP registry as io.github.vmalyshev1/vat-support. EU & UK statutory VAT compliance, VIES validation, ViDA e-invoicing & Art. 196 reverse-charge. This page covers its hosted endpoint (https://vat.support/api/mcp).

Is the VAT.SUPPORT MCP server safe to use?

VAT.SUPPORT scores 61 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the VAT.SUPPORT MCP server expose?

VAT.SUPPORT exposes 7 tools: vida_mandate_check, intrastat_threshold_check, reverse_charge_certificate, vat_number_check, vat_rate_lookup, and 2 more. Their descriptions and schemas cost roughly 952 tokens of context every time the server is loaded.

Does the VAT.SUPPORT MCP server require authentication?

No. We connected to VAT.SUPPORT without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the VAT.SUPPORT MCP server still maintained?

VAT.SUPPORT is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.