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 Validator MCP

REMOTE · VAT-VALIDATOR-MCP-PRODUCTION.UP.RAILWAY.APP · 2 COMPONENTS · SCANNED SEP 20

Validate EU, UK, AU VAT numbers for AI agents. EU ViDA e-invoicing compliance.

0 this week 74 Trust /100
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 Security57
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 545 tokens (~272/item across 2 items; 2 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 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
Install

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

# add to Claude Code
claude mcp add --transport http ojaskord-vat-validator-mcp 'https://vat-validator-mcp-production.up.railway.app/'
// .cursor/mcp.json
{
  "mcpServers": {
    "ojaskord-vat-validator-mcp": {
      "url": "https://vat-validator-mcp-production.up.railway.app/"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ojaskord-vat-validator-mcp": {
      "type": "http",
      "url": "https://vat-validator-mcp-production.up.railway.app/"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.ojaskord-vat-validator-mcp]
url = "https://vat-validator-mcp-production.up.railway.app/"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ojaskord-vat-validator-mcp": {
      "type": "remote",
      "url": "https://vat-validator-mcp-production.up.railway.app/",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ojaskord-vat-validator-mcp --url 'https://vat-validator-mcp-production.up.railway.app/' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ojaskord-vat-validator-mcp:
    url: "https://vat-validator-mcp-production.up.railway.app/"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ojaskord-vat-validator-mcp": {
      "Transport": "http",
      "Url": "https://vat-validator-mcp-production.up.railway.app/"
    }
  }
}
# add to Vellum
assistant mcp add ojaskord-vat-validator-mcp -t streamable-http -u 'https://vat-validator-mcp-production.up.railway.app/'
// mcp.json
{
  "mcpServers": {
    "ojaskord-vat-validator-mcp": {
      "type": "http",
      "url": "https://vat-validator-mcp-production.up.railway.app/"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 8 Sept 26 0
    • Server version: 2.0.42 → 2.0.44 functional
  • 26 Aug 26 +2
    • 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 +1
    • Server version: 2.0.40 → 2.0.42 functional
  • 19 Aug 26 0
    • Server version: 2.0.39 → 2.0.40 functional
  • 11 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
  • 31 Jul 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
  • 30 Jul 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
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 20 Sept 2026 · Probed https://vat-validator-mcp-production.up.railway.app

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.up.railway.app CN=YE1,O=Let's Encrypt,C=US 29 Jul 2026 27 Oct 2026 ECDSA 256 ECDSA-SHA384 6da79bb561da3efeb0e751ca21abd3999fe
SANs: *.up.railway.app, up.railway.app
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 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 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://vat-validator-mcp-production.up.railway.app Verified 200
http (plaintext) http://vat-validator-mcp-production.up.railway.app HTTPS enforced 301 https://vat-validator-mcp-production.up.railway.app/
MCP tools · 2 exposed · ~545 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_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.

NameTypeReqDescription
country_codestringISO 2-letter code e.g. DE, FR, GB. Omit for all countries.
NameTypeReqDescription
_disclaimerstring
agent_actionstringyes
checked_atstringyes
countrystring
country_codestring
notestring
ratesobjectPresent only when country_code is omitted -- full rate table for all supported jurisdictions
reducedarrayReduced VAT rates as percentages, if any apply
source_urlstringyes
standardnumberStandard 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.

NameTypeReqDescription
invoice_amountnumberInvoice amount in local currency — used in fraud risk weighting.
invoice_company_namestringCompany name as it appears on the invoice — if provided, cross-checks against registry and flags mismatches.
vat_numberstringyesVAT number with country prefix. EU: DE123456789. AU: ABN12345678901.
NameTypeReqDescription
_disclaimerstring
addressstring|null
agent_actionstringyesMachine-readable verdict
checked_atstringyes
company_namestring|null
fraud_risk_levelstring
fraud_risk_scorenumber
fraud_signalsarray
jurisdictionstringyes
name_matchstring
recommendationstring
source_urlstringyes
summarystring
validbooleanyesWhether the VAT number is currently registered and active per the source registry
vat_numberstringyes

No examples provided.

Common questions

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?

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

Is the VAT Validator MCP server still maintained?

VAT Validator MCP 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.