Validate EU e-invoices (Peppol, XRechnung, Factur-X, UBL, CII) and explain error codes.
Validate EU e-invoices (Peppol, XRechnung, Factur-X, UBL, CII) and explain error codes. Exposed over MCP by the eleata e mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.
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.
Everything the assistant can do here goes through one of these:
validate_einvoice — Validate one invoice (Peppol BIS 3.0, EN 16931 UBL/CII, XRechnung 3.0.x, Factur-X/ZUGFeRD, UBL, CII). Returns valid/invalid + each rule idlist_formats — List the formats eleata validates today + roadmapexplain_error_code — Explain one error code (e.g. 00400, BR-DE-21) in plain English, with the fix. Works offlineYou will need one environment variable: EINVOICE_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Among the payments and commerce options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Eleata E's toolset — validate_einvoice, list_formats, explain_error_code — is a fair guide to whether it matches your workflow. It is maintained by hernaninverso; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Eleata E's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| validate_einvoice | Validate 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. |
| list_formats | List the formats eleata validates today + roadmap. |
| explain_error_code | Explain one error code (e.g. 00400, BR-DE-21) in plain English, with the fix. Works offline. |
{
"mcpServers": {
"eleata-einvoice": {
"command": "npx",
"args": ["-y", "eleata-einvoice-mcp"],
"env": { "EINVOICE_API_KEY": "your_free_key_here" }
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| EINVOICE_API_KEY | Credential the server authenticates with. | Yes |
Payments infrastructure meets AI — customers, invoices, subscriptions and current API docs from Stripe's server.
Build for Shopify with current APIs — the official Dev MCP server for schema-accurate storefront and admin code.
Give your AI assistant a supervised window into your Interactive Brokers account — balances, positions, live quotes and orders.
Invoices, payments and disputes through PayPal's official server — commerce operations by conversation.
Enables querying and listing Azure resources and costs directly from an MCP client.
Empowers LLMs with Bitcoin Lightning Network payment capabilities via the ZBD API.