Skip to main content

honest-vies-mcp

Local MCP server for the EU VIES VAT number validator (the authoritative EU-wide check used before issuing 0% VAT cross-border invoices) — no authentication, no rate limit, no cloud middle.

Part of the honest-mcp family of small, auditable, local-first MCP servers.

Why

A Polish JDG (or any EU business) issuing a 0% VAT reverse-charge invoice to an EU B2B customer must first verify that customer's VAT number is registered in VIES — and keep evidence of the check. Skipping this and it turns out the customer's VAT is invalid, your tax office will demand domestic VAT from you (23% in Poland), retroactively, plus interest.

This server puts VIES a single tool call away. Ask your AI "verify DE143454214 before I issue this invoice" and you get: valid/invalid, registered name and address, and a consultation number for your records if you provided your own VAT.

Same trust model as the rest of the family: data flows only between your machine and the European Commission.

Features

Two tools:

  • check_vat — validate a single EU VAT number. Optionally pass your own VAT (requester_country + requester_vat) to receive a consultation number as legal proof of the check.
  • list_supported_countries — the 27 EU country codes + XI for Northern Ireland.

Data source

  • Endpoint: ec.europa.eu/taxation_customs/vies/ REST API
  • No API key, no registration
  • Coverage: 27 EU member states + Northern Ireland (XI)
  • Note: Greece uses country code EL, not GR

Requirements

  • Python 3.10+

Setup

git clone https://github.com/bartosz-kuc/honest-vies-mcp.git
cd honest-vies-mcp
python3 -m venv venv
./venv/bin/pip install -r requirements.txt

On Windows, create the venv with python -m venv venv and use venv\Scripts\pip and venv\Scripts\python.exe instead of the venv/bin/... paths shown here and below.

Register with Claude Code:

claude mcp add vies /absolute/path/to/venv/bin/python /absolute/path/to/server.py

Claude Desktop claude_desktop_config.json:

{
  "mcpServers": {
    "vies": {
      "command": "/absolute/path/to/venv/bin/python",
      "args": ["/absolute/path/to/server.py"]
    }
  }
}

Example usage

"Verify German VAT DE143454214 before I invoice them."

check_vat(country_code="DE", vat_number="143454214") → valid/invalid + name/address.

"Verify the same, but also get a consultation number — my VAT is PL7393933151."

check_vat(vat="DE143454214", requester_country="PL", requester_vat="7393933151") → response includes a consultation_number field. Save that number with the invoice.

"What's the EU VAT country code for Greece again?"

list_supported_countries() → confirms Greece is EL, not GR.

Data flow

Your AI client
     ↕  MCP stdio
This server (Python, on your machine)
     ↕  HTTPS
ec.europa.eu (VIES)

No cloud middle. Nothing to log in to. No telemetry.

For Polish JDG owners

The tax law bit: art. 42 ust. 1 pkt 1 ustawy o VAT — before applying the 0% rate on an intra-community supply (WDT), the seller must have a valid VAT-UE number of the buyer. Art. 100 ust. 8 pkt 1 — proof of the check is expected on audit. The consultation_number (VIES's requestIdentifier) is the standard evidence: it's a unique code tying your check to a specific date and pair of VAT numbers. Store it with the invoice.

Non-obvious bits VIES will bite you with:

  • If your OWN VAT (the requester) is not currently active in VIES, no consultation number is returned even when the checked VAT is valid.
  • VIES is an EU-wide switch — validation happens against the national database of the country in the VAT prefix. Occasionally a national database is offline; the server surfaces that clearly instead of pretending it's a valid/invalid result.

Author

Bartosz Kuć — Warsaw-based developer, JDG owner running skanfirmy.pl.

Consulting

Available for consulting on Polish tax and business integrations (KSeF, GUS/NFZ/GIOŚ APIs, mBank data), MCP server design, and AI-assisted tooling for JDGs and small teams. See skanfirmy.pl/uslugi for productized packages (audit 3k PLN, setup 8-15k PLN, retainer 2-4k PLN/mo), or reach out via email.

License

MIT — see LICENSE.

Metadata

Release files for honest-vies-mcp 0.2.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for honest-vies-mcp 0.2.0
File Size Uploaded
honest_vies_mcp-0.2.0.tar.gz 8.7 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for honest-vies-mcp 0.2.0
File Interpreter ABI Platform
honest_vies_mcp-0.2.0-py3-none-any.whl Python 3 none any Details

Total release size: 17.5 kB

Release files / honest_vies_mcp-0.2.0.tar.gz

Download URL honest_vies_mcp-0.2.0.tar.gz
Size 8.7 kB
Tags Source
SHA-256 checksum
How to use checksums
115c0a9c7f1e9645b89afdea2eb1b5d3c0bb16c0780210716e51e91cb070a59d
BLAKE2b-256 checksum
How to use checksums
d884251e7cf8caf3032d7eeac6eda47a8832f7847d281e20b9970cde5a0d6347
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 26, 2026.

Transparency log

Release files / honest_vies_mcp-0.2.0-py3-none-any.whl

Download URL honest_vies_mcp-0.2.0-py3-none-any.whl
Size 8.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
aa47f4462b81df8062bef2fd375664c299928bfa0852d2902baa110a9e0b231d
BLAKE2b-256 checksum
How to use checksums
06e8ee17360e2033545804fec9330461ea4045216db490d688a3b7cc60b94ed6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 26, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.2.0 This release

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page