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.

EU VAT rates

NPM · @DUTY27/EU-VAT-MCP

Standard VAT rate in any EU member state on any date since 2016. Offline, no API key.

Available components

+3 this week 87 Trust /100

Last scanned (16 hours ago)

Scores higher than 91% of npm servers

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to duty27/eu-vat). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 31 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 550 tokens (~137/item across 4 items; 4 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 Management77
  • Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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 +1

    No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 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.

  • 1 Nov 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.

  • 30 Oct 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.

  • 28 Oct 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.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
    • Security disclosure: unverified → fail ▼ functional
  • 23 Oct 26 +1
    • Security disclosure: fail → unverified ▼ functional
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 6 Nov 2026 · Analysed npm/@duty27/eu-vat-mcp@0.1.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo duty27/eu-vat
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/duty27/eu-vat/.github/workflows/mcp-publish.yml@refs/tags/mcp-v0.1.1
Rekor log index 3093465011
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:1adfac434680faedd44b1ae14585a2b9c194d5585123277844502d289cb92294168b5d53a6d4ce26b0d4cecf850f7fdf40788e74d40de7e6769921cb1

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~550 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
get_rate_history ~132

List every standard VAT rate one EU member state has had since 2016-01-01, with the first day each one applied. Use this for "how has the VAT rate in Ireland changed?". Standard VAT rates only (not reduced rates), from 2016-01-01. Data checked against the published rates on 2026-10-04; a change made after that date appears in a newer release.

NameTypeReqDescription
countrystringyesEU member state code such as "DE" or "FR" (case does not matter). Greece is "EL"; "GR" is accepted too.
NameTypeReqDescription
attributionstringyes–
countrystringyes–
dataAsOfstringyes–
windowsarrayyes–

No examples provided.

get_standard_rate ~195

Look up the standard VAT rate in force in one EU member state on a given day (any day since 2016-01-01). Use this for "what was the VAT rate in Germany on 1 July 2020?" or "what is the VAT rate in Finland today?". The day a rate changes is the first day of the new rate. Standard VAT rates only (not reduced rates), from 2016-01-01. Data checked against the published rates on 2026-10-04; a change made after that date appears in a newer release.

NameTypeReqDescription
countrystringyesEU member state code such as "DE" or "FR" (case does not matter). Greece is "EL"; "GR" is accepted too.
datestring–Day as YYYY-MM-DD, for example "2020-07-01". Optional: today (UTC) when omitted.
NameTypeReqDescription
attributionstringyes–
countrystringyes–
dataAsOfstringyes–
datestringyes–
ratenumberyes–

No examples provided.

list_countries ~62

List the 27 EU member states with the codes the other tools expect. Greece is "EL", the code the European Union uses ("GR" is also accepted). Use this to find a code. The United Kingdom and other non-EU countries are not covered.

Input schema present but exposes no named parameters.

NameTypeReqDescription
attributionstringyes–
countriesarrayyes–
dataAsOfstringyes–

No examples provided.

list_rate_changes ~161

List the changes of the standard VAT rate across the EU, newest first, optionally for one country and/or since a date. Use this for "which EU countries changed their VAT rate this year?". Each change gives the old rate, the new rate, and the first day of the new rate. Standard VAT rates only (not reduced rates), from 2016-01-01. Data checked against the published rates on 2026-10-04; a change made after that date appears in a newer release.

NameTypeReqDescription
countrystring–Only this member state (for example "RO"). Omit for all 27.
sincestring–Only changes on or after this day, YYYY-MM-DD. Omit for all of them.
NameTypeReqDescription
attributionstringyes–
changesarrayyes–
dataAsOfstringyes–

No examples provided.

Install

How do I install the EU VAT rates MCP server?

EU VAT rates runs locally as an npm package, launched with npx -y @duty27/eu-vat-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @duty27/eu-vat-mcp

# add to Claude Code
claude mcp add duty27-eu-vat -- npx -y @duty27/eu-vat-mcp
Common questions

What is the EU VAT rates MCP server?

EU VAT rates is an MCP server listed in the public MCP registry as io.github.duty27/eu-vat. Standard VAT rate in any EU member state on any date since 2016. Offline, no API key. This page covers its npm package (@duty27/eu-vat-mcp).

Is the EU VAT rates MCP server safe to use?

EU VAT rates scores 87 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 6 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 EU VAT rates MCP server expose?

EU VAT rates exposes 4 tools: get_standard_rate, get_rate_history, list_rate_changes, list_countries. Their descriptions and schemas cost roughly 550 tokens of context every time the server is loaded.

Is the EU VAT rates MCP server still maintained?

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

What licence is the EU VAT rates MCP server under?

EU VAT rates declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the EU VAT rates MCP server?

VerifyMCP ran 16 checks on EU VAT rates, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.