Eleata e-Invoice Validator

io.github.hernaninversoPublished by GitHub account hernaninversov0.1.1Updated Oct 24, 2026

Validate EU e-invoices (Peppol, XRechnung, Factur-X, UBL, CII) and explain error codes.

VerifiedSTDIODesktop onlyDeveloper ToolsBusiness & Commerce

Overview

AI-generated overview

Validates EU electronic invoices (Peppol, XRechnung, Factur-X, UBL, CII) and explains validation error codes from an AI assistant.

What you can do
The server exposes three tools. validate_einvoice checks one invoice against official Schematron rules for Peppol BIS 3.0, EN 16931 UBL/CII, XRechnung 3.0.x, Factur-X/ZUGFeRD, UBL and CII, returning valid or invalid plus each rule id, an explanation and a suggested fix. list_formats lists the formats currently supported and planned. explain_error_code explains a single code such as 00400 or BR-DE-21 in plain English with the fix, using a bundled offline reference.
When to use it
Useful when an assistant is asked whether an invoice file is valid before submission, or when a rejection from a platform such as SdI, Chorus Pro or KSeF needs to be understood and corrected. It suits developers and finance or e-invoicing staff working with EU invoice formats.
Requirements
Runs locally over stdio, typically started with npx, so Node.js is needed. A free API key is required in the environment variable EINVOICE_API_KEY for validate_einvoice; the other two tools work without it. Network access is needed for validation, which calls the hosted eleata API.
Before you install
validate_einvoice sends the invoice content to the hosted eleata API, so invoice data leaves the machine; the other two tools are local. The API key is supplied as EINVOICE_API_KEY and should be kept out of shared configuration. The free tier is limited to 200 validations per month.

Installation

In SourceWeft

  1. Open Eleata e-Invoice Validator in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

eleata e-invoice MCP server

Validate EU electronic invoices and explain validation error codes directly from your AI coding agent (Claude, Cursor, Copilot, …). It wraps the hosted eleata validation API plus a bundled offline error-code reference.

Never ship a broken invoice. When you ask your agent "is this FatturaPA / XRechnung / Peppol file valid?", it runs the official Schematron rules and gets back the rule id and the fix — before a rejection (an SdI scarto, a Chorus Pro refusal, a KSeF error) ever happens.

Tools

ToolWhat it doesAPI key
validate_einvoiceValidate one invoice (Peppol BIS 3.0, EN 16931 UBL/CII, XRechnung 3.0.x, Factur-X/ZUGFeRD, UBL, CII). Returns valid/invalid + each rule id, explanation and fix.required
list_formatsList the formats eleata validates today + roadmap.none
explain_error_codeExplain one error code (e.g. 00400, BR-DE-21) in plain English, with the fix. Works offline.none

Setup

  1. Get a free API key (200 validations/month, no card) at https://eleata.io/signup/.
  2. Add the server to your agent's MCP config.

Claude Desktop / Claude Code (claude_desktop_config.json or .mcp.json)

json
{  "mcpServers": {    "eleata-einvoice": {      "command": "npx",      "args": ["-y", "eleata-einvoice-mcp"],      "env": { "EINVOICE_API_KEY": "your_free_key_here" }    }  }}

Cursor (~/.cursor/mcp.json)

Same block as above.

Example prompts

  • "Validate this XRechnung file and tell me what to fix" (paste the XML)
  • "What does FatturaPA error 00400 mean and how do I fix it?"
  • "Which e-invoice formats can you validate today?"

Privacy

validate_einvoice sends the invoice you pass to the hosted eleata API for validation. list_formats and explain_error_code are local/offline (the error-code reference is bundled). See https://eleata.io/privacy/.

Links

MIT licensed. Schematron engines: Mustang / phive. Schematron rules from CEN, OpenPeppol, KoSIT.

Source: README.md at commit 58e280b

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

40% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.