VAT Validator MCP

REMOTE · VAT-VALIDATOR-MCP-PRODUCTION.UP.RAILWAY.APP · 2 COMPONENTS · SCANNED AUG 3

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

Available components

remote · vat-validator-mcp-production.up.railway.app 61 npm · vat-validator-mcp 39

+4 this week 61 61 Trust /100

Trust breakdown (6 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 →

Endpoint Security57

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 2 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability64

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 Management27

Stability observed for 8 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

Capabilities20

Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · vat-validator-mcp-production.up.railway.app

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http ojaskord-vat-validator-mcp 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/"

// 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.

3 Aug 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.
1 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
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
29 Jul 26 +1

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

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
27 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
26 Jul 26 57

First indexed and scored.

Show 7 earlier entries Hide earlier entries

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 3 Aug 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

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

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.

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.

Input Output Examples

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.

Input Output Examples

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.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	57
27 Jul	57
28 Jul	58
29 Jul	59
30 Jul	59
31 Jul	59
1 Aug	60
2 Aug	60
3 Aug	61