vat.support VAT Compliance
REMOTE · SNAPSHOT.VAT.SUPPORT · SCANNED SEP 20
EU/UK VAT compliance for AI agents: number validation, rate lookups, reverse-charge checks.
Available components
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 Security60
- 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 5 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 634 tokens (~126/item across 5 items; 5 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 Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 79% 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 6 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
How do I install the vat.support VAT Compliance MCP server?
vat.support VAT Compliance is a hosted endpoint at https://snapshot.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 · snapshot.vat.support
claude mcp add --transport http vmalyshev1-vat-support 'https://snapshot.vat.support/api/mcp'
{
"mcpServers": {
"vmalyshev1-vat-support": {
"url": "https://snapshot.vat.support/api/mcp"
}
}
} {
"servers": {
"vmalyshev1-vat-support": {
"type": "http",
"url": "https://snapshot.vat.support/api/mcp"
}
}
} [mcp_servers.vmalyshev1-vat-support] url = "https://snapshot.vat.support/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"vmalyshev1-vat-support": {
"type": "remote",
"url": "https://snapshot.vat.support/api/mcp",
"enabled": true
}
}
} openclaw mcp add vmalyshev1-vat-support --url 'https://snapshot.vat.support/api/mcp' --transport streamable-http
mcp_servers:
vmalyshev1-vat-support:
url: "https://snapshot.vat.support/api/mcp" {
"McpServers": {
"vmalyshev1-vat-support": {
"Transport": "http",
"Url": "https://snapshot.vat.support/api/mcp"
}
}
} assistant mcp add vmalyshev1-vat-support -t streamable-http -u 'https://snapshot.vat.support/api/mcp'
{
"mcpServers": {
"vmalyshev1-vat-support": {
"type": "http",
"url": "https://snapshot.vat.support/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Probed https://snapshot.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=snapshot.vat.support | CN=YE1,O=Let's Encrypt,C=US | 26 Aug 2026 | 24 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 6dd5c76f99018a1257672471bed73105282 |
| SANs: snapshot.vat.support | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 snapshot.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 |
| snapshot.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://snapshot.vat.support/api/mcp | Verified | 200 | |
| http (plaintext) | http://snapshot.vat.support/api/mcp | HTTPS enforced | 308 | https://snapshot.vat.support/api/mcp |
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 →
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.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_country | string | yes | Customer ISO-3166-1 alpha-2 (e.g. 'IT') |
| customer_vat_id | string | – | Customer VAT identifier including country prefix (e.g. 'IT12345678901') |
| service_type | string | – | Type of service: professional_services | digital_services | transport | telecom | event_admission |
| supplier_country | string | yes | Supplier 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.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | yes | Q1..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… |
| language | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| vat_id | string | yes | Full 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).
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO-2 country code |
| rate_type | string | – | 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.
| Name | Type | Req | Description |
|---|---|---|---|
| annual_revenue_eur | number | – | – |
| country | string | yes | – |
| customer_type | string | – | – |
| sale_countries | array | – | Other countries where the business sells |
| supply_types | array | – | Supply mix — `goods`, `digital_services`, `professional_services`, etc. Defaults to `[goods]` when omitted. |
No output schema declared.
No examples provided.
What is the vat.support VAT Compliance MCP server?
vat.support VAT Compliance is an MCP server listed in the public MCP registry as io.github.vmalyshev1/vat-support. EU/UK VAT compliance for AI agents: number validation, rate lookups, reverse-charge checks. This page covers its hosted endpoint (https://snapshot.vat.support/api/mcp).
Is the vat.support VAT Compliance MCP server safe to use?
vat.support VAT Compliance scores 69 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 VAT Compliance MCP server expose?
vat.support VAT Compliance exposes 5 tools: reverse_charge_certificate, vat_number_check, vat_rate_lookup, vat_registration_check, vat_compliance_full. Their descriptions and schemas cost roughly 582 tokens of context every time the server is loaded.
Does the vat.support VAT Compliance MCP server require authentication?
No. We connected to vat.support VAT Compliance without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the vat.support VAT Compliance MCP server still maintained?
vat.support VAT Compliance is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.