Eleata e-Invoice Validator

Registre officiel Finance et paiements

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

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

NPM package eleata-einvoice-mcp
Claude Code
claude mcp add eleata-e-invoice-validator -e 'EINVOICE_API_KEY=<your einvoice_api_key>' -- npx -y eleata-einvoice-mcp@0.1.1
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "eleata-e-invoice-validator": {
            "command": "npx",
            "args": [
                "-y",
                "eleata-einvoice-mcp@0.1.1"
            ],
            "env": {
                "EINVOICE_API_KEY": "<your einvoice_api_key>"
            }
        }
    }
}

Variables d'environnement

  • EINVOICE_API_KEY obligatoire secret Free API key for the eleata e-invoice validation backend (https://eleata.io/signup/)

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. eleata e-invoice MCP server
  2. Tools
  3. Setup
  4. Example prompts
  5. Privacy
  6. Links

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)
{
  "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/.

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

Questions fréquentes

Qu'est-ce que Eleata e-Invoice Validator ?

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

Comment installer Eleata e-Invoice Validator ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add eleata-e-invoice-validator -e 'EINVOICE_API_KEY=<your einvoice_api_key>' -- npx -y eleata-einvoice-mcp@0.1.1. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour Eleata e-Invoice Validator ?

Oui. Il attend EINVOICE_API_KEY, à renseigner dans sa configuration.

Eleata e-Invoice Validator est-il open source ?

Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.

Qui maintient Eleata e-Invoice Validator ?

Il est publié par hernaninverso. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.