Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Eleata e-Invoice Validator

NPM · ELEATA-EINVOICE-MCP · SCANNED SEP 20

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

Available components

0 this week 83 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 392 tokens (~130/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Eleata e-Invoice Validator MCP server?

Eleata e-Invoice Validator runs locally as an npm package, launched with npx -y eleata-einvoice-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · eleata-einvoice-mcp

# add to Claude Code
claude mcp add hernaninverso-eleata-einvoice-mcp -- npx -y eleata-einvoice-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "hernaninverso-eleata-einvoice-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "eleata-einvoice-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "hernaninverso-eleata-einvoice-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "eleata-einvoice-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add hernaninverso-eleata-einvoice-mcp -- npx -y eleata-einvoice-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "hernaninverso-eleata-einvoice-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "eleata-einvoice-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add hernaninverso-eleata-einvoice-mcp --command npx --arg -y --arg eleata-einvoice-mcp
# ~/.hermes/config.yaml
mcp_servers:
  hernaninverso-eleata-einvoice-mcp:
    command: "npx"
    args: ["-y", "eleata-einvoice-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "hernaninverso-eleata-einvoice-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "eleata-einvoice-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add hernaninverso-eleata-einvoice-mcp -t stdio -c npx -a -y eleata-einvoice-mcp
// mcp.json
{
  "mcpServers": {
    "hernaninverso-eleata-einvoice-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "eleata-einvoice-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 19 Sept 26 +1

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

  • 17 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 16 Sept 26 +1
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

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

  • 12 Sept 26 +1

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

  • 10 Sept 26 +1

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

  • 9 Sept 26 −4
    • Stability: pass → 0.77 functional
  • 8 Sept 26 +1
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/eleata-einvoice-mcp@0.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 95 packages
Packages resolved 95
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~392 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
explain_error_code ~105

Explain a single e-invoice validation error code (e.g. a FatturaPA SdI control like 00400, or an XRechnung rule like BR-DE-21) in plain English, with the suggested fix and an example. Works offline; no API key required.

NameTypeReqDescription
rule_idstringyesThe rule id / error code, e.g. '00400', 'BR-DE-21', 'PEPPOL-EN16931-R053'.

No output schema declared.

No examples provided.

list_formats ~45

List the EU e-invoice formats eleata can validate today, plus what is on the roadmap (e.g. FatturaPA, KSeF). No API key required.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

validate_einvoice ~242

Validate an EU electronic invoice against the official Schematron rules (Peppol BIS 3.0, EN 16931 UBL/CII, XRechnung 3.0.x, Factur-X/ZUGFeRD, UBL, CII). Returns whether it is valid and, for each violation, the rule id, a plain-English explanation and a suggested fix. Use this before a developer ships or transmits an invoice so a rejection (an SdI scarto, a Chorus Pro refusal, a KSeF error) is caught early. Requires EINVOICE_API_KEY (a free key from https://eleata.io/signup/).

NameTypeReqDescription
contentstringyesThe invoice to validate. For XML formats, the raw XML text. For a Factur-X / ZUGFeRD PDF, the base64-encoded PDF bytes (set is_pdf=true).
formatstringFormat hint. Default: auto (the server sniffs XML vs PDF and the profile).
is_pdfbooleanSet true if `content` is a base64-encoded PDF (Factur-X/ZUGFeRD). Default false.

No output schema declared.

No examples provided.

Common questions

What is the Eleata e-Invoice Validator MCP server?

Eleata e-Invoice Validator is an MCP server listed in the public MCP registry as io.github.hernaninverso/eleata-einvoice-mcp. Validate EU e-invoices (Peppol, XRechnung, Factur-X, UBL, CII) and explain error codes. This page covers its npm package (eleata-einvoice-mcp).

Is the Eleata e-Invoice Validator MCP server safe to use?

Eleata e-Invoice Validator scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 Eleata e-Invoice Validator MCP server expose?

Eleata e-Invoice Validator exposes 3 tools: validate_einvoice, list_formats, explain_error_code. Their descriptions and schemas cost roughly 392 tokens of context every time the server is loaded.

Is the Eleata e-Invoice Validator MCP server still maintained?

Eleata e-Invoice Validator is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Eleata e-Invoice Validator MCP server under?

Eleata e-Invoice Validator declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.