# Electronic Invoice API (remote · mcp.electronic-invoice.app)

Validate, generate, convert and extract EN 16931 e-invoices for businesses.

- Trust score: 77/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.electronic-invoice.app`: 77/100 (this document), [markdown](https://verifymcp.io/servers/app-electronic-invoice-mcp/mcp.md), [page](https://verifymcp.io/servers/app-electronic-invoice-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.electronic-invoice.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 77/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3258 tokens (~407/item across 8 items; 7 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 39/100
  - Stability check failed: schema churn in the 16 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 1 additions.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### How do I install the Electronic Invoice API MCP server?

Electronic Invoice API is a hosted endpoint at https://mcp.electronic-invoice.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http app-electronic-invoice-mcp 'https://mcp.electronic-invoice.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "app-electronic-invoice-mcp": {
      "url": "https://mcp.electronic-invoice.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-electronic-invoice-mcp": {
      "type": "http",
      "url": "https://mcp.electronic-invoice.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-electronic-invoice-mcp]
url = "https://mcp.electronic-invoice.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-electronic-invoice-mcp": {
      "type": "remote",
      "url": "https://mcp.electronic-invoice.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-electronic-invoice-mcp --url 'https://mcp.electronic-invoice.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-electronic-invoice-mcp:
    url: "https://mcp.electronic-invoice.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "app-electronic-invoice-mcp": {
      "Transport": "http",
      "Url": "https://mcp.electronic-invoice.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-electronic-invoice-mcp -t streamable-http -u 'https://mcp.electronic-invoice.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "app-electronic-invoice-mcp": {
      "type": "http",
      "url": "https://mcp.electronic-invoice.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 32 to 36.

### 2026-11-18 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 26 to 29.

### 2026-11-16 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 19 to 22.

### 2026-11-14 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 12 to 16.

### 2026-11-11 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 2 to 6.

### 2026-11-07 (score 72, 0)

- [security] Tool “convert_invoice” rewrote its description, which is the text the model reads
- [security] Tool “extract_invoice” rewrote its description, which is the text the model reads
- [security] Tool “generate_invoice” rewrote its description, which is the text the model reads
- [security] Tool “open_invoice_check” rewrote its description, which is the text the model reads
- [security] Tool “validate_invoice” rewrote its description, which is the text the model reads
- [cosmetic] “convert_invoice” reworded the description of “qr”

### 2026-11-06 (score 72, 0)

- [security regression] Stability: unverified → fail
- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-05 (score 72)

First indexed and scored.

## MCP tools (7)

### `validate_invoice` (~677 tokens)

Validate e-invoice

Validate 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.

Input parameters:

- `checks` (string): Optional opt-in plausibility checks (PL rules): mandatory items of section 14(4) UStG, arithmetic, dates, Skonto, VAT rates, VAT id form. They are an aid, not legal or tax advice.
- `content` (string): Raw invoice XML as UTF-8 text (UBL Invoice/CreditNote or UN/CEFACT CII). For XML invoices only. XML extracted from a PDF is checked without the PDF container; send PDFs through file or contentBase64.…
- `contentBase64` (string): Base64-encoded raw bytes of an invoice XML or PDF file. For PDFs and binary-safe XML when file is not available. Exactly one of file, content and contentBase64 is required.
- `contentType` (string): Optional MIME type of the supplied document. Defaults to application/xml for content and to a value derived from filename for contentBase64. Ignored for file, where the file content decides.
- `country` (string): Rule set country. DE checks XRechnung and EN 16931. FR applies the French CIUS rules. Default DE.
- `file` (object): The invoice file the user attached in ChatGPT. The server fetches the original bytes and passes them on unchanged, so a PDF is checked as a whole, including its container. Only for clients that provi…
- `filename` (string): Optional original filename, for example rechnung.xml or rechnung.pdf. It is used only to derive the result filename and is not sent to the API.

Output parameters:

- `ok` (boolean)

### `generate_invoice` (~378 tokens)

Generate e-invoice

Create 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.

Input parameters:

- `country` (string): Rule set country for validation of the generated invoice. Default DE.
- `format` (string, required): Output format. xrechnung-ubl and xrechnung-cii return XML. zugferd-en16931, zugferd-xrechnung and facturx-en16931 return a PDF/A-3 file. Required.
- `invoice` (object, required): Invoice data per the Electronic Invoice API schema. Required fields: number, issueDate, seller, buyer, lines. Optional fields include typeCode, dueDate, deliveryDate, currency, buyerReference, notes,…
- `lang` (string): Language of the PDF visual. Default de.
- `qr` (boolean): Add an EPC QR payment page to PDF output when IBAN and amount due are present. The response header X-Payment-QR says added or skipped with a reason. Ignored for XML output.

Output parameters:

- `ok` (boolean)

### `convert_invoice` (~558 tokens)

Convert e-invoice

Convert 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.

Input parameters:

- `content` (string): Raw invoice XML as UTF-8 text (UBL Invoice/CreditNote or UN/CEFACT CII). For XML invoices only. XML extracted from a PDF is checked without the PDF container; send PDFs through file or contentBase64.…
- `contentBase64` (string): Base64-encoded raw bytes of an invoice XML or PDF file. For PDFs and binary-safe XML when file is not available. Exactly one of file, content and contentBase64 is required.
- `contentType` (string): Optional MIME type of the supplied document. Defaults to application/xml for content and to a value derived from filename for contentBase64. Ignored for file, where the file content decides.
- `country` (string): Rule set country for validation. Default DE.
- `file` (object): The invoice file the user attached in ChatGPT. The server fetches the original bytes and passes them on unchanged, so a PDF is checked as a whole, including its container. Only for clients that provi…
- `filename` (string): Optional original filename, for example rechnung.xml or rechnung.pdf. It is used only to derive the result filename and is not sent to the API.
- `lang` (string): Language of the PDF visual. Default de.
- `profile` (string): PDF profile for to=zugferd or to=facturx. Default follows the input profile. Not valid for ubl or cii.
- `qr` (boolean): Add an EPC QR payment page to PDF output.
- `to` (string, required): Target. ubl and cii return XML. zugferd and facturx return a PDF/A-3 file. Required.

Output parameters:

- `ok` (boolean)

### `extract_invoice` (~877 tokens)

Extract e-invoice data

Read 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.

Input parameters:

- `attachments` (boolean): json only: include embedded files as base64.
- `content` (string): Raw invoice XML as UTF-8 text (UBL Invoice/CreditNote or UN/CEFACT CII). For XML invoices only. XML extracted from a PDF is checked without the PDF container; send PDFs through file or contentBase64.…
- `contentBase64` (string): Base64-encoded raw bytes of an invoice XML or PDF file. For PDFs and binary-safe XML when file is not available. Exactly one of file, content and contentBase64 is required.
- `contentType` (string): Optional MIME type of the supplied document. Defaults to application/xml for content and to a value derived from filename for contentBase64. Ignored for file, where the file content decides.
- `datevAccountLength` (integer): datev only, required: Sachkontenlaenge 4 to 8.
- `datevBookingKeys` (string): datev only, optional: BU-Schluessel per VAT category and rate, for example S19=9,S7=8.
- `datevChartOfAccounts` (string): datev only, optional: Sachkontenrahmen, for example 03 or 04.
- `datevClient` (integer): datev only, required: Mandantennummer 1 to 99999.
- `datevConsultant` (integer): datev only, required: Beraternummer 1001 to 9999999.
- `datevCounterAccount` (string): datev only, required: personal account (creditor or debtor), digits only.
- `datevDirection` (string): datev only, required: incoming (expense) or outgoing (revenue).
- `datevDueDate` (boolean): datev only, optional: write the due date into the DATEV field Faelligkeit.
- `datevFiscalYearStart` (string): datev only, required: start of the fiscal year as YYYY-MM-DD. The year of the document date is derived from it.
- `datevLabel` (string): datev only, optional: Bezeichnung, at most 30 characters.
- `datevLedgerAccount` (string): datev only, required: expense or revenue account, digits only.
- `delimiter` (string): csv only: field delimiter. Default semicolon.
- `file` (object): The invoice file the user attached in ChatGPT. The server fetches the original bytes and passes them on unchanged, so a PDF is checked as a whole, including its container. Only for clients that provi…
- `filename` (string): Optional original filename, for example rechnung.xml or rechnung.pdf. It is used only to derive the result filename and is not sent to the API.
- `format` (string): Output. json returns the EN 16931 term model plus a summary. csv returns one row per line. datev returns a DATEV Buchungsstapel (EXTF, Windows-1252). Default json.
- `labels` (boolean): json only: add a map from BT number to xr element name.

Output parameters:

- `ok` (boolean)

### `open_invoice_check` (~122 tokens)

Open invoice file check

Open 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.

Output parameters:

- `ok` (boolean)

### `get_service_status` (~71 tokens)

Get service status

Check 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.

Output parameters:

- `ok` (boolean)

### `get_usage_limits` (~72 tokens)

Get usage limits

Return 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/.

Output parameters:

- `ok` (boolean)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-electronic-invoice-mcp/mcp#diagnostics

## Score history

- 2026-11-21: 77
- 2026-11-20: 77
- 2026-11-19: 76
- 2026-11-18: 76
- 2026-11-17: 75
- 2026-11-16: 75
- 2026-11-15: 74
- 2026-11-14: 74
- 2026-11-13: 73
- 2026-11-12: 73
- 2026-11-11: 73
- 2026-11-10: 72
- 2026-11-09: 72
- 2026-11-08: 72
- 2026-11-07: 72
- 2026-11-06: 72
- 2026-11-05: 72

## Common questions

### What is the Electronic Invoice API MCP server?

Electronic Invoice API is an MCP server listed in the public MCP registry as app.electronic-invoice/mcp. Validate, generate, convert and extract EN 16931 e-invoices for businesses. This page covers its hosted endpoint (https://mcp.electronic-invoice.app/mcp).

### Is the Electronic Invoice API MCP server safe to use?

Electronic Invoice API scores 77 out of 100 on VerifyMCP. 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 Electronic Invoice API MCP server expose?

Electronic Invoice API exposes 7 tools: validate_invoice, generate_invoice, convert_invoice, extract_invoice, open_invoice_check, and 2 more. Their descriptions and schemas cost roughly 2,755 tokens of context every time the server is loaded.

### Does the Electronic Invoice API MCP server require authentication?

No. We connected to Electronic Invoice API without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Electronic Invoice API MCP server still maintained?

Electronic Invoice API is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Electronic Invoice API MCP server?

VerifyMCP ran 14 checks on Electronic Invoice API, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.electronic-invoice.app/mcp
- Website: https://electronic-invoice.app/
- Changelog RSS feed: https://verifymcp.io/servers/app-electronic-invoice-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-electronic-invoice-mcp/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/app-electronic-invoice-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/app-electronic-invoice-mcp/mcp
