Electronic Invoice API
app.electronic-invoice/mcpVersion 0.2.0Validate, generate, convert and extract EN 16931 e-invoices for businesses.
Status
Responds193 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 13:36 UTC
- Latency
- 193 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://mcp.electronic-invoice.app/mcpResponds193 msNo sign-in
Claude Code
claude mcp add --transport http electronic-invoice https://mcp.electronic-invoice.app/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: electronic-invoice
Remote MCP server URL: https://mcp.electronic-invoice.app/mcpCursor
{
"mcpServers": {
"electronic-invoice": {
"url": "https://mcp.electronic-invoice.app/mcp"
}
}
}VS Code
code --add-mcp '{"name":"electronic-invoice","type":"http","url":"https://mcp.electronic-invoice.app/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
7 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
convert_invoiceConvert an existing e-invoice from UBL to CII, CII to UBL, or XML to a ZUGFeRD/Factur-X PDF. Also accepts a ZUGFeRD/Factur-X PDF and converts its embedded XML. Validates every output and returns it only if valid. Changes format or container only; it does not create invoices from data or extract data. Supported profiles are EN 16931 and XRechnung 3.0; other profiles return 422 unsupported_profile. Other formats are not converted. B2B only. Requires the caller's own Electronic Invoice API key, sent either directly as Authorization: Bearer eia_live_... or through an OAuth 2.1 access token issued by this server. A call that reaches the API and returns 200, 400, 422 or 504 counts against the plan quota. | No | No | Not declared | No |
extract_invoiceRead data from an existing UBL/CII XML or ZUGFeRD/Factur-X PDF. Returns JSON business terms keyed by BT/BG numbers, CSV with one row per line, or a DATEV Buchungsstapel (EXTF). Does not validate the invoice. Suited to accounting import or data analysis. Supports UBL, CII and ZUGFeRD/Factur-X only. DATEV export has hard limits: EUR only, one invoice per file, issue date inside the fiscal year, and no booking of prepayments, rounding or Skonto. DATEV output is written to the documented layout and was not tested against a DATEV installation. B2B only. Requires the caller's own Electronic Invoice API key, sent either directly as Authorization: Bearer eia_live_... or through an OAuth 2.1 access token issued by this server. A call that reaches the API and returns 200, 400, 422 or 504 counts against the plan quota. | No | Yes | Not declared | No |
generate_invoiceCreate a new e-invoice file from structured JSON. Builds XRechnung UBL/CII or a ZUGFeRD/Factur-X PDF, validates the result with the same rule sets, and returns the file only if it is valid. Creates new files only; it does not read or change existing files. Supports invoice, credit note, corrected, partial and final invoices, prepayments, and an optional EPC payment QR page for PDF output. B2B only. Requires the caller's own Electronic Invoice API key, sent either directly as Authorization: Bearer eia_live_... or through an OAuth 2.1 access token issued by this server. A call that reaches the API and returns 200, 400, 422 or 504 counts against the plan quota. | No | No | Not declared | No |
get_service_statusCheck whether the Electronic Invoice API is up and which rule set versions it currently runs. Calls GET /v1/health without an API key. Free, not billable, works without an account. B2B only. It reports service health only, not whether a specific API key or quota is valid. | No | Yes | Not declared | No |
get_usage_limitsReturn the technical limits of the Electronic Invoice API: rate limits, concurrency limits, request body size limits, and which HTTP status codes count against the quota. Works without an API key and does not call the API. B2B only. Information about plans is at https://electronic-invoice.app/en/api/. | No | Yes | Not declared | No |
open_invoice_checkOpen an upload field in the chat where the user chooses an invoice PDF or XML file. The file goes straight from the field to this server's validation without passing through the model, so a PDF is checked as a whole, including its PDF/A-3 container, and the validation runs on the KoSIT validator. For clients that cannot pass a file as a tool argument. Opening the field is free, and a check counts against the user's quota only once they press the button. This tool needs no input and checks nothing by itself. B2B only. | No | Yes | Not declared | No |
validate_invoiceValidate an existing e-invoice file without changing it. Accepts UBL Invoice/CreditNote XML, UN/CEFACT CII XML, FatturaPA or KSeF FA(3) XML, or a ZUGFeRD/Factur-X/XRechnung PDF. Returns verdict, findings and rule set versions. Checks: XRechnung 3.0 (UBL, CII), EN 16931 (UBL, CII), Peppol BIS Billing 3.0 (UBL), Netherlands NLCIUS (SI-UBL 2.0, CII), Romania CIUS-RO, French CIUS rules when country is FR, and ZUGFeRD/Factur-X PDF or CII in all profiles (MINIMUM, BASIC WL, BASIC, EN16931, EXTENDED). Other EN 16931 CIUS are checked against the EN 16931 core rules only, and the result notes that national rules were not checked. Italy FatturaPA and Poland KSeF FA(3) are checked against the official schema only. A PDF is also checked as a PDF/A-3 container, but only if the PDF itself is sent. Checks an existing file; it does not create, convert or change invoices. B2B only. Requires the caller's own Electronic Invoice API key, sent either directly as Authorization: Bearer eia_live_... or through an OAuth 2.1 access token issued by this server. A call that reaches the API and returns 200, 400, 422 or 504 counts against the plan quota. | No | Yes | Not declared | No |
Details
- Registry status
- Active
- Published
- Nov 6, 2026
- Updated
- Nov 6, 2026
- Repository
- Not given
- Categories (suggested)
- Invoicing and accountingSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared