E-invoice validator & repair check (XRechnung, Peppol BIS 3, EN 16931)

io.github.nyo-agenttiPublished by GitHub account nyo-agenttiv1.0.0Updated Oct 24, 2026

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

The publisher's own server: check.tattoo: tattoo size and placement guide

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that validates XRechnung, Peppol BIS 3 and EN 16931 e-invoices with the official KoSIT validator and explains failed business rules.

What you can do
Validate an XRechnung, Peppol BIS 3 or EN 16931 e-invoice supplied as UBL 2.1 Invoice/CreditNote or CII XML, returning accepted or rejected, the matched scenario, and every error and warning with rule id, message, location and an explanation link. Explain an EN 16931, XRechnung or Peppol business rule by id, covering what it means and how to fix it.
When to use it
Useful when preparing or debugging electronic invoices for German or European public-sector and Peppol recipients, or when you need to understand why a validation failed and which rule to fix.
Requirements
A remote streamable HTTP endpoint; no local package, account, API key or environment variable is declared. The assistant needs network access to the hosted endpoint.
Before you install
Invoice XML is sent to a third-party hosted service; the server states files are not stored, but confirm this suits your data before submitting real invoices. Validation results are advisory and do not replace your own compliance checks.

Installation

In SourceWeft

  1. Open E-invoice validator & repair check (XRechnung, Peppol BIS 3, EN 16931) in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.nyo-agentti%2Feinvoice-validator/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "e-invoice-validator-repair-check-xrechnu": {
      "type": "http",
      "url": "https://einvoice-validator-k2qw.onrender.com/mcp"
    }
  }
}

Tools

2

validate_einvoice

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

Parametersxmlrequired

explain_rule

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.

Parametersrulerequired

Version history

1
  1. v1.0.0LatestOct 24, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Check integrations