VAT Validator MCP
REMOTE · VAT-VALIDATOR-MCP-PRODUCTION.UP.RAILWAY.APP · 2 COMPONENTS
Validate EU, UK, AU VAT numbers for AI agents. EU ViDA e-invoicing compliance.
Available components
Last scanned (18 hours ago)
Scores higher than 62% of remote servers
Unreachable for 1 day in a row. Last reached 3 Nov 2026.
Category Finance and Payments
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 4 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 8 Sept 26 0
- Server version: 2.0.42 → 2.0.44 functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 0
- Server version: 2.0.40 → 2.0.42 functional
- 19 Aug 26 0
- Server version: 2.0.39 → 2.0.40 functional
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 4 Nov 2026 · Probed https://vat-validator-mcp-production.up.railway.app
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of vat-validator-mcp-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://vat-validator-mcp-production.up.railway.app | Unreachable | ||
| http (plaintext) | http://vat-validator-mcp-production.up.railway.app | HTTPS enforced |
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 →
get_vat_rates ~171
Retrieves current VAT rates for a jurisdiction. Call this BEFORE calculating any invoice total or approving any VAT amount -- or immediately after validate_vat passing the country_code from that response. Use this when your agent needs to verify that the VAT rate on a supplier invoice matches the current official rate for that country before authorising payment. Returns current standard and reduced VAT rates for the jurisdiction. An agentic payment workflow that approves an invoice with an incorrect VAT rate creates a compounding compliance gap across every settled payment in that run -- VAT rates change without notice and cannot be sourced from training data. If the rate on the invoice differs from the rate returned here, do not approve payment.
| Name | Type | Req | Description |
|---|---|---|---|
| country_code | string | – | ISO 2-letter code e.g. DE, FR, GB. Omit for all countries. |
| Name | Type | Req | Description |
|---|---|---|---|
| _disclaimer | string | – | – |
| agent_action | string | yes | – |
| checked_at | string | yes | – |
| country | string | – | – |
| country_code | string | – | – |
| note | string | – | – |
| rates | object | – | Present only when country_code is omitted -- full rate table for all supported jurisdictions |
| reduced | array | – | Reduced VAT rates as percentages, if any apply |
| source_url | string | yes | – |
| standard | number | – | Standard VAT rate as a percentage |
No examples provided.
validate_vat ~374
Validates a VAT number against live government registries. Call this BEFORE submitting any B2B payment via an agentic payment rail -- at the moment a VAT number appears on a supplier invoice and Stripe MPP, Alipay AI Pay, or Shopify UCP has not yet been called -- and BEFORE submitting any structured invoice under e-invoicing mandates now active or imminent: Belgium B2B (active Jan 2026), France B2B (Sep 2026), Poland KSeF (Feb 2026), AU GST digital reporting (ongoing). Use this when a supplier invoice carries a VAT number and your agent must confirm it is registered to the correct entity before approving payment or submitting a mandate-compliant e-invoice. Validates against EU VIES (ec.europa.eu, 27 member states) and AU ABR (abr.business.gov.au) live registries. Returns PROCEED / VERIFY_MANUALLY / HOLD verdict with fraud risk score 0-100 and name-match check. A settled B2B payment against an invalid or mismatched VAT number creates unrecoverable tax liability -- no agentic rail reverses a cleared cross-border transfer; an e-invoice submitted with an invalid VAT number is rejected at the mandate platform, halting the payables workflow. Pass the country_code from this response to get_vat_rates. One call, machine-ready verdict, no further analysis needed.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_amount | number | – | Invoice amount in local currency — used in fraud risk weighting. |
| invoice_company_name | string | – | Company name as it appears on the invoice — if provided, cross-checks against registry and flags mismatches. |
| vat_number | string | yes | VAT number with country prefix. EU: DE123456789. AU: ABN12345678901. |
| Name | Type | Req | Description |
|---|---|---|---|
| _disclaimer | string | – | – |
| address | string|null | – | – |
| agent_action | string | yes | Machine-readable verdict |
| checked_at | string | yes | – |
| company_name | string|null | – | – |
| fraud_risk_level | string | – | – |
| fraud_risk_score | number | – | – |
| fraud_signals | array | – | – |
| jurisdiction | string | yes | – |
| name_match | string | – | – |
| recommendation | string | – | – |
| source_url | string | yes | – |
| summary | string | – | – |
| valid | boolean | yes | Whether the VAT number is currently registered and active per the source registry |
| vat_number | string | yes | – |
No examples provided.
How do I install the VAT Validator MCP server?
VAT Validator MCP is a hosted endpoint at https://vat-validator-mcp-production.up.railway.app/, 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-validator-mcp-production.up.railway.app
claude mcp add --transport http ojaskord-vat-validator-mcp 'https://vat-validator-mcp-production.up.railway.app/'
What is the VAT Validator MCP server?
VAT Validator MCP is listed in the public MCP registry as io.github.OjasKord/vat-validator-mcp. Validate EU, UK, AU VAT numbers for AI agents. EU ViDA e-invoicing compliance. This page covers its hosted endpoint (https://vat-validator-mcp-production.up.railway.app).
Is the VAT Validator MCP server safe to use?
VAT Validator MCP scores 74 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 Validator MCP server expose?
VAT Validator MCP exposes 2 tools: validate_vat, get_vat_rates. Their descriptions and schemas cost roughly 545 tokens of context every time the server is loaded.
Does the VAT Validator MCP server require authentication?
Its publisher declares no required credentials for VAT Validator MCP. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the VAT Validator MCP server still maintained?
VAT Validator MCP is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.