# E-invoice validator & repair check (XRechnung, Peppol BIS 3, EN 16931) (remote · einvoice-validator-k2qw.onrender.com)

Validate XRechnung, Peppol BIS 3 and EN 16931 invoices with KoSIT; explain rules; check auto-repair

- Trust score: 23/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `einvoice-validator-k2qw.onrender.com`: 23/100 (this document), [markdown](https://verifymcp.io/servers/nyo-agentti-einvoice-validator/einvoice-validator-k2qw.md), [page](https://verifymcp.io/servers/nyo-agentti-einvoice-validator/einvoice-validator-k2qw)

## Channel facts

- Endpoint: `https://einvoice-validator-k2qw.onrender.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint returned HTTP 404.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

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

## Install

### How do I install the E-invoice validator & repair check (XRechnung, Peppol BIS… MCP server?

E-invoice validator & repair check (XRechnung, Peppol BIS… is a hosted endpoint at https://einvoice-validator-k2qw.onrender.com/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 nyo-agentti-einvoice-validator 'https://einvoice-validator-k2qw.onrender.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "nyo-agentti-einvoice-validator": {
      "url": "https://einvoice-validator-k2qw.onrender.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "nyo-agentti-einvoice-validator": {
      "type": "http",
      "url": "https://einvoice-validator-k2qw.onrender.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.nyo-agentti-einvoice-validator]
url = "https://einvoice-validator-k2qw.onrender.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nyo-agentti-einvoice-validator": {
      "type": "remote",
      "url": "https://einvoice-validator-k2qw.onrender.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add nyo-agentti-einvoice-validator --url 'https://einvoice-validator-k2qw.onrender.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  nyo-agentti-einvoice-validator:
    url: "https://einvoice-validator-k2qw.onrender.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "nyo-agentti-einvoice-validator": {
      "Transport": "http",
      "Url": "https://einvoice-validator-k2qw.onrender.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add nyo-agentti-einvoice-validator -t streamable-http -u 'https://einvoice-validator-k2qw.onrender.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "nyo-agentti-einvoice-validator": {
      "type": "http",
      "url": "https://einvoice-validator-k2qw.onrender.com/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-10-28 (score 23, −50)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.10 → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

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

### 2026-10-25 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-24 (score 72)

First indexed and scored.

## MCP tools (2)

### `validate_einvoice` (~121 tokens)

Validate an e-invoice

Validate an XRechnung / Peppol BIS 3 / EN 16931 e-invoice (UBL 2.1 Invoice/CreditNote or CII CrossIndustryInvoice XML) with the official KoSIT validator. Returns accepted/rejected, the matched scenario and every error and warning with rule id, message, location and a link to a plain-language explanation. For rejected files it also reports which errors an automatic repair removes (measured on this file).

Input parameters:

- `xml` (string, required): The complete invoice XML as text (max 5 MB).

### `explain_rule` (~78 tokens)

Explain an e-invoice business rule

Explain an EN 16931 / XRechnung / Peppol business rule by id (e.g. BR-CO-10, BR-DE-15, PEPPOL-EN16931-R001): what it means and how to fix it.

Input parameters:

- `rule` (string, required): Rule id, e.g. BR-CO-10

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/nyo-agentti-einvoice-validator/einvoice-validator-k2qw#diagnostics

## Score history

- 2026-11-05: 23
- 2026-11-04: 23
- 2026-11-03: 23
- 2026-11-02: 23
- 2026-11-01: 23
- 2026-10-31: 23
- 2026-10-30: 23
- 2026-10-29: 23
- 2026-10-28: 23
- 2026-10-27: 73
- 2026-10-26: 73
- 2026-10-25: 72
- 2026-10-24: 72

## Common questions

### What is the E-invoice validator & repair check (XRechnung, Peppol BIS… MCP server?

E-invoice validator & repair check (XRechnung, Peppol BIS… is an MCP server listed in the public MCP registry as io.github.nyo-agentti/einvoice-validator. Validate XRechnung, Peppol BIS 3 and EN 16931 invoices with KoSIT; explain rules; check auto-repair. This page covers its hosted endpoint (https://einvoice-validator-k2qw.onrender.com/mcp).

### Is the E-invoice validator & repair check (XRechnung, Peppol BIS… MCP server safe to use?

E-invoice validator & repair check (XRechnung, Peppol BIS… scores 23 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 E-invoice validator & repair check (XRechnung, Peppol BIS… MCP server expose?

E-invoice validator & repair check (XRechnung, Peppol BIS… exposes 2 tools: validate_einvoice, explain_rule. Their descriptions and schemas cost roughly 199 tokens of context every time the server is loaded.

### Does the E-invoice validator & repair check (XRechnung, Peppol BIS… MCP server require authentication?

Its publisher declares no required credentials for E-invoice validator & repair check (XRechnung, Peppol BIS…. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the E-invoice validator & repair check (XRechnung, Peppol BIS… MCP server still maintained?

E-invoice validator & repair check (XRechnung, Peppol BIS… 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://einvoice-validator-k2qw.onrender.com/mcp
- Website: https://nyo-agentti.github.io/
- Changelog RSS feed: https://verifymcp.io/servers/nyo-agentti-einvoice-validator/einvoice-validator-k2qw.xml
- Changelog JSON feed: https://verifymcp.io/servers/nyo-agentti-einvoice-validator/einvoice-validator-k2qw.json
- HTML version of this page: https://verifymcp.io/servers/nyo-agentti-einvoice-validator/einvoice-validator-k2qw