# EU e-invoicing and business checks (EN 16931, Peppol, VAT, sanctions) (remote · api.wsystem.dev)

EN 16931/XRechnung e-invoice validate+create, Peppol routing, EU VAT/EORI, sanctions, KYB. Free tier

- Trust score: 65/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.wsystem.dev`: 65/100 (this document), [markdown](https://verifymcp.io/servers/wsystemdev-eu-business-data-mcp/api.md), [page](https://verifymcp.io/servers/wsystemdev-eu-business-data-mcp/api)

## Channel facts

- Endpoint: `https://api.wsystem.dev/mcp/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.4`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 14 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2210 tokens (~157/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (14% of tools); any adoption earns full credit.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_einvoice_sandbox" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the EU e-invoicing and business checks (EN 16931, Peppol, VAT… MCP server?

EU e-invoicing and business checks (EN 16931, Peppol, VAT… 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.

### Claude

```bash
claude mcp add --transport http wsystemdev-eu-business-data-mcp 'https://api.wsystem.dev/mcp/'
```

### Cursor

```json
{
  "mcpServers": {
    "wsystemdev-eu-business-data-mcp": {
      "url": "https://api.wsystem.dev/mcp/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "wsystemdev-eu-business-data-mcp": {
      "type": "http",
      "url": "https://api.wsystem.dev/mcp/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.wsystemdev-eu-business-data-mcp]
url = "https://api.wsystem.dev/mcp/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wsystemdev-eu-business-data-mcp": {
      "type": "remote",
      "url": "https://api.wsystem.dev/mcp/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add wsystemdev-eu-business-data-mcp --url 'https://api.wsystem.dev/mcp/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  wsystemdev-eu-business-data-mcp:
    url: "https://api.wsystem.dev/mcp/"
```

### Netclaw

```json
{
  "McpServers": {
    "wsystemdev-eu-business-data-mcp": {
      "Transport": "http",
      "Url": "https://api.wsystem.dev/mcp/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add wsystemdev-eu-business-data-mcp -t streamable-http -u 'https://api.wsystem.dev/mcp/'
```

### Other

```json
{
  "mcpServers": {
    "wsystemdev-eu-business-data-mcp": {
      "type": "http",
      "url": "https://api.wsystem.dev/mcp/"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 65, +1)

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

### 2026-11-03 (score 64, +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.

### 2026-10-31 (score 63, +1)

- [security] Tool “validate_einvoice” rewrote its description, which is the text the model reads

### 2026-10-29 (score 62, +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.

### 2026-10-28 (score 61, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 1954 → 2210
- [functional] New tool “parse_einvoice”

### 2026-10-27 (score 61, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-26 (score 60)

First indexed and scored.

## MCP tools (14)

### `verify_vat` (~220 tokens)

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.
UK (GB) VAT checks are coming soon: until HMRC live access is granted, GB numbers return
status member_state_unavailable, valid=null, error HMRC_LIVE_ACCESS_PENDING (not charged). For >1 number use verify_batch.

Input parameters:

- `requester`
- `vat` (string, required)

### `verify_batch` (~87 tokens)

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
(GB items stay member_state_unavailable until HMRC live access is granted; they are not charged).

Input parameters:

- `requester`
- `vats` (array, required)

Output parameters:

- `result` (array)

### `lookup_company` (~136 tokens)

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.

Input parameters:

- `country` (string)
- `limit` (integer)
- `query` (string, required)

### `screen_sanctions` (~96 tokens)

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.

Input parameters:

- `birth_year`
- `country`
- `name` (string, required)
- `threshold` (number)

### `kyb_check` (~106 tokens)

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').

Input parameters:

- `company` (string, required)
- `country` (string)
- `requester`

### `verify_eori` (~113 tokens)

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.

Input parameters:

- `eori` (string, required)

### `verify_eori_batch` (~45 tokens)

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

Input parameters:

- `eoris` (array, required)

Output parameters:

- `result` (array)

### `validate_einvoice` (~200 tokens)

Validate an EU e-invoice XML (UBL 2.1 Invoice/CreditNote or UN/CEFACT CII, e.g. XRechnung, Factur-X/ZUGFeRD XML) against the
official CEN EN 16931 rules and, for XRechnung, the KoSIT XRechnung 3.0 rules. Returns valid, and every error with its rule ID
(e.g. BR-CO-10), a plain-English message, XPath and a fix hint. rules: auto | en16931 | xrechnung. Slovak sellers also get eFaktúra field
checks (FR SR transposition v1.13, warnings with ruleset SK-FS); Norwegian sellers get NO-LAW field checks. Peppol-specific rules are not checked yet.
For PDFs use the REST endpoint POST /einvoice/validate.

Input parameters:

- `rules` (string)
- `xml` (string, required)

### `parse_einvoice` (~153 tokens)

Read an incoming EU e-invoice into one JSON shape: seller, buyer, dates, references, totals, VAT breakdown, payment/IBAN, lines and
attachments. Accepts UBL 2.1 Invoice/CreditNote or UN/CEFACT CII XML (XRechnung, Peppol BIS 3, Factur-X XML) in xml, or a ZUGFeRD/Factur-X
PDF as base64 in pdf_base64. Use when asked to read, extract or book a received e-invoice. Values are returned as written in the invoice;
this does NOT validate it (use validate_einvoice for that).

Input parameters:

- `pdf_base64`
- `xml`

### `create_einvoice` (~180 tokens)

Create a validated EU e-invoice (UBL 2.1) from simple JSON. invoice = {format: en16931|xrechnung|peppol-bis3, invoice_number,
issue_date (YYYY-MM-DD), due_date?, tax_point_date?, delivery_date?, currency (EUR), buyer_reference?, seller: {name, vat_id, street, city,
postal_code, country, email, phone, contact_name, company_id?, company_id_scheme?, legal_form?}, buyer: {...}, lines: [{description, quantity, unit_price, unit?, vat_category (S|Z|E|AE|K|G|O), vat_rate}],
payment: {iban, bic?, terms?}}. Totals and VAT breakdown are computed; returns {valid, xml, totals, errors}.

Input parameters:

- `invoice` (object, required)

### `einvoice_route` (~119 tokens)

'Can I e-invoice this company?' id = EU VAT number (e.g. 'BE0403170701') or Peppol id ('0208:0403170701').
Returns VIES VAT status, Peppol registration (Peppol Directory, then SML/SMP; BIS 3 invoice support), the country's B2B e-invoice mandate
(dates, format, source) and the recommended format for create_einvoice. France's PPF directory is not included yet.

Input parameters:

- `id` (string, required)

### `send_einvoice_sandbox` (~171 tokens)

SANDBOX ONLY - never reaches a real buyer. Runs the full send flow on an invoice (same JSON as create_einvoice): VIES check
of the buyer VAT, sanctions screen of the buyer name, EN 16931 create + validate, route lookup (Peppol/mandate), transport
hand-off and an Ed25519-signed evidence receipt (JWS). transport: "mock" (simulated, default), "recommand" or "e-invoice-be"
(the UBL is really submitted to that Peppol access point's sandbox, addressed to W System's own sandbox company; the
partner document id is returned). Use it to build and test an integration before live sending exists.

Input parameters:

- `invoice` (object, required)
- `transport` (string)

### `due_diligence_report` (~117 tokens)

Counterparty due-diligence report in one call: VIES VAT, official business register, EU/UN/OFAC/UK sanctions,
EC EORI, GLEIF LEI and Peppol e-invoice route, with deterministic risk flags, 0-100 risk score, pass/review/fail
verdict, sources and UTC timestamp. company: VAT ID (best), registry number or name; country: ISO code for names.

Input parameters:

- `company` (string, required)
- `country` (string)

### `check_fr_pa_registry` (~200 tokens)

Is this e-invoicing platform on France's official list of Plateformes Agréées (PA)? name = platform or company name
(e.g. 'Pennylane'), website = its site (e.g. 'https://www.acubeapi.com/'); give at least one. Checks the DGFiP lists on
impots.gouv.fr: registered PAs (with registration date) and operators awaiting interoperability tests. Returns
on_official_list, status (approved | awaiting_interop_tests | possible_match | not_found), scored matches, list date and the
official source. Use for supplier due diligence before the French reform (receive from 1 Sep 2026, SMEs issue from
1 Sep 2027). A 'solution compatible' is not a PA itself. Unofficial copy; the official lists prevail.

Input parameters:

- `limit` (integer)
- `name` (string)
- `website` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/wsystemdev-eu-business-data-mcp/api#diagnostics

## Score history

- 2026-11-05: 65
- 2026-11-04: 64
- 2026-11-03: 64
- 2026-11-02: 63
- 2026-11-01: 63
- 2026-10-31: 63
- 2026-10-30: 62
- 2026-10-29: 62
- 2026-10-28: 61
- 2026-10-27: 61
- 2026-10-26: 60

## Common questions

### What is the EU e-invoicing and business checks (EN 16931, Peppol, VAT… MCP server?

EU e-invoicing and business checks (EN 16931, Peppol, VAT… is an MCP server listed in the public MCP registry as io.github.wsystemdev/eu-business-data-mcp. EN 16931/XRechnung e-invoice validate+create, Peppol routing, EU VAT/EORI, sanctions, KYB. Free tier. This page covers its hosted endpoint (https://api.wsystem.dev/mcp/).

### Is the EU e-invoicing and business checks (EN 16931, Peppol, VAT… MCP server safe to use?

EU e-invoicing and business checks (EN 16931, Peppol, VAT… scores 65 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 e-invoicing and business checks (EN 16931, Peppol, VAT… MCP server expose?

EU e-invoicing and business checks (EN 16931, Peppol, VAT… exposes 14 tools: verify_vat, verify_batch, lookup_company, screen_sanctions, kyb_check, and 9 more. Their descriptions and schemas cost roughly 1,943 tokens of context every time the server is loaded.

### Does the EU e-invoicing and business checks (EN 16931, Peppol, VAT… MCP server require authentication?

No. We connected to EU e-invoicing and business checks (EN 16931, Peppol, VAT… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the EU e-invoicing and business checks (EN 16931, Peppol, VAT… MCP server still maintained?

EU e-invoicing and business checks (EN 16931, Peppol, VAT… is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://api.wsystem.dev/mcp/
- Repository: https://github.com/wsystemdev/eu-business-data-mcp
- Website: https://wsystem.dev/
- Changelog RSS feed: https://verifymcp.io/servers/wsystemdev-eu-business-data-mcp/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/wsystemdev-eu-business-data-mcp/api.json
- HTML version of this page: https://verifymcp.io/servers/wsystemdev-eu-business-data-mcp/api