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 Business Data (VAT, EORI, company, sanctions, KYB)

REMOTE · API.WSYSTEM.DEV

EU VAT (VIES) and EORI validation, company registry, sanctions screening, KYB. Free tier, x402.

Available components

60 Trust /100

Last scanned (18 hours ago)

Scores higher than 45% of remote servers

Reachable. Last reached 17 Oct 2026.

Category Security

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 Usability66
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 837 tokens (~119/item across 7 items; 7 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (29% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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

Unverified: 1 category

A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

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.

  • 17 Oct 26 60

    First indexed and scored.

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 17 Oct 2026 · Probed https://api.wsystem.dev/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.wsystem.dev CN=WE1,O=Google Trust Services,C=US 17 Oct 2026 15 Jan 2027 ECDSA 256 ECDSA-SHA256 1c9ad0738ac6f3b40e044872de594765
SANs: api.wsystem.dev
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.wsystem.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
wsystem.dev. 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://api.wsystem.dev/mcp/ Verified 200
http (plaintext) http://api.wsystem.dev/mcp/ HTTPS enforced 301 https://api.wsystem.dev/mcp/
MCP tools · 7 exposed · ~749 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
kyb_check ~106

One-call KYB check of a supplier/customer: EU VAT validation (VIES) + official business register + EU/UN/OFAC/UK sanctions screening, returning a pass / review / fail verdict with reasons. company: a VAT ID ('FR40303265045'), a company name, or a registry id; country: optional ISO code (e.g. 'NO').

NameTypeReqDescription
companystringyes–
countrystring––
requester–––

No output schema declared.

No examples provided.

lookup_company ~136

Look up a company in official European business registers by name or registry number. country: FR (SIREN), NO (org.nr), FI (Y-tunnus), CZ (ICO), PL (KRS number), EE, or any other ISO code / 'LEI' (GLEIF). Returns legal name, ID, status/active, address, VAT ID, activity code and official source link. Use to confirm a company exists and is active, find its registry number, or map a name to a VAT ID.

NameTypeReqDescription
countrystring––
limitinteger––
querystringyes–

No output schema declared.

No examples provided.

screen_sanctions ~96

Screen a person or company name against official EU, UN, OFAC SDN and UK sanctions lists. Fuzzy matching with transliteration; returns candidate matches with 0-100 scores, list, programme, DOB. A potential match needs human review; this is a screening aid, not legal advice.

NameTypeReqDescription
birth_year–––
country–––
namestringyes–
thresholdnumber––

No output schema declared.

No examples provided.

verify_batch ~66

Validate up to 100 EU VAT numbers in one call via VIES (supplier/customer list cleanup, onboarding, invoice runs). Same per-item result as verify_vat; items with member_state_unavailable should be retried later.

NameTypeReqDescription
requester–––
vatsarrayyes–
NameTypeReqDescription
resultarrayyes–

No examples provided.

verify_eori ~113

Validate an EU EORI (customs Economic Operators Registration and Identification) number, e.g. 'SE5560360793', 'DE1234567890123', against the official European Commission EOS service. Use for import/export, customs declarations and freight-forwarder onboarding. Returns valid/invalid and trader name/address only when the trader consented to publication. UK (GB) EORIs are not in EOS (HMRC checks those); XI EORIs are.

NameTypeReqDescription
eoristringyes–

No output schema declared.

No examples provided.

verify_eori_batch ~45

Validate up to 100 EU EORI numbers in one call via the official EC EOS service (customs / import-export KYB).

NameTypeReqDescription
eorisarrayyes–
NameTypeReqDescription
resultarrayyes–

No examples provided.

verify_vat ~187

Validate an EU VAT number against the official European Commission VIES service (27 EU states + XI Northern Ireland). Use when asked whether a VAT ID is valid/active, before zero-rated reverse-charge B2B invoices, or to get a company's registered name/address from its VAT number. Input: VAT with country prefix, e.g. 'IE6388047V', 'DE811193231' (spaces/dots ok). Returns status: valid | invalid | invalid_format | member_state_unavailable (VIES/member state down - retry later, valid=null) | error, plus name, address (if the member state discloses them; DE/ES often don't) and consultation_number (audit proof) when requester is set. For GB VAT numbers use HMRC instead; for >1 number use verify_batch.

NameTypeReqDescription
requester–––
vatstringyes–

No output schema declared.

No examples provided.

Install

How do I install the EU Business Data (VAT, EORI, company, sanctions, KYB) MCP server?

EU Business Data (VAT, EORI, company, sanctions, KYB) is a hosted endpoint at https://api.wsystem.dev/mcp/, 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 · api.wsystem.dev

# add to Claude Code
claude mcp add --transport http zifengw-eu-business-data-mcp 'https://api.wsystem.dev/mcp/'
Common questions

What is the EU Business Data (VAT, EORI, company, sanctions, KYB) MCP server?

EU Business Data (VAT, EORI, company, sanctions, KYB) is an MCP server listed in the public MCP registry as io.github.zifengw/eu-business-data-mcp. EU VAT (VIES) and EORI validation, company registry, sanctions screening, KYB. Free tier, x402. This page covers its hosted endpoint (https://api.wsystem.dev/mcp/).

Is the EU Business Data (VAT, EORI, company, sanctions, KYB) MCP server safe to use?

EU Business Data (VAT, EORI, company, sanctions, KYB) scores 60 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 EU Business Data (VAT, EORI, company, sanctions, KYB) MCP server expose?

EU Business Data (VAT, EORI, company, sanctions, KYB) exposes 7 tools: verify_vat, verify_batch, lookup_company, screen_sanctions, kyb_check, and 2 more. Their descriptions and schemas cost roughly 749 tokens of context every time the server is loaded.

Does the EU Business Data (VAT, EORI, company, sanctions, KYB) MCP server require authentication?

No. We connected to EU Business Data (VAT, EORI, company, sanctions, KYB) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the EU Business Data (VAT, EORI, company, sanctions, KYB) MCP server still maintained?

EU Business Data (VAT, EORI, company, sanctions, KYB) is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.