# Invoiceer e-invoicing tools (remote · invoiceer.io)

Create and validate XRechnung, ZUGFeRD and Peppol e-invoices (KoSIT); Peppol lookup, rule help.

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-22

## Components

- remote · `invoiceer.io`: 69/100 (this document), [markdown](https://verifymcp.io/servers/io-invoiceer-einvoicing/invoiceer.md), [page](https://verifymcp.io/servers/io-invoiceer-einvoicing/invoiceer)

## Channel facts

- Endpoint: `https://invoiceer.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.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-10-22.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1095 tokens (~182/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 78/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 35% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Invoiceer e-invoicing tools MCP server?

Invoiceer e-invoicing tools is a hosted endpoint at https://invoiceer.io/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 io-invoiceer-einvoicing 'https://invoiceer.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-invoiceer-einvoicing": {
      "url": "https://invoiceer.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-invoiceer-einvoicing": {
      "type": "http",
      "url": "https://invoiceer.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-invoiceer-einvoicing]
url = "https://invoiceer.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-invoiceer-einvoicing": {
      "type": "remote",
      "url": "https://invoiceer.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-invoiceer-einvoicing --url 'https://invoiceer.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-invoiceer-einvoicing:
    url: "https://invoiceer.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-invoiceer-einvoicing": {
      "Transport": "http",
      "Url": "https://invoiceer.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-invoiceer-einvoicing -t streamable-http -u 'https://invoiceer.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-invoiceer-einvoicing": {
      "type": "http",
      "url": "https://invoiceer.io/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-10-22 (score 69, +1)

- [functional regression] Schema quality: 916 → 1095
- [functional improvement] Stability: unverified → 0.03
- [functional] New tool “read_invoice_pdf”

### 2026-10-21 (score 68)

First indexed and scored.

## MCP tools (6)

### `validate_einvoice` (~161 tokens)

Validate an e-invoice

Validate an e-invoice (XRechnung UBL/CII, ZUGFeRD / Factur-X PDF, Peppol BIS Billing 3.0, EN 16931) with the official KoSIT validator. Returns valid/invalid, the detected format, every error and warning with its rule code, and the exact corrected value for common calculation errors. Pass the XML as text in `xml`, or a PDF/XML file base64-encoded in `file_base64`. Max 5 MB.

Input parameters:

- `file_base64` (string): Alternative: the file (ZUGFeRD/Factur-X PDF or XML), base64-encoded.
- `xml` (string): The invoice XML (UBL or CII) as text.

### `peppol_lookup` (~118 tokens)

Peppol participant lookup

Check whether a company can receive e-invoices over Peppol. Accepts a Peppol ID (e.g. 0208:0123456749), a VAT number (e.g. BE0123456749, NL...B01) or a Belgian enterprise number. Returns each matching participant ID, whether it is registered, whether it accepts Peppol BIS invoices, and name/country from the Peppol Directory when published.

Input parameters:

- `query` (string, required): Peppol ID, VAT number or enterprise number.

### `check_leitweg_id` (~84 tokens)

Check a Leitweg-ID

Check a German Leitweg-ID (buyer reference BT-10 for invoices to German public authorities) against the official format and check digit (spec v2.0.2). Returns validity, the parts and the expected check digits.

Input parameters:

- `lang` (string)
- `leitweg_id` (string, required): e.g. 991-33333TEST-33

### `create_einvoice` (~335 tokens)

Create an e-invoice

Create a valid e-invoice from structured data: XRechnung 3.0 (UBL or CII), ZUGFeRD / Factur-X PDF (EN 16931) or Peppol BIS Billing 3.0. The file is checked with the official KoSIT validator before it is returned; if it fails, you get the rule errors instead of a file. XML comes back as text in `xml`, the ZUGFeRD PDF as base64 in `pdf_base64`. XRechnung needs a seller contact (contact, phone, email), a buyer email or Peppol ID (electronic address), a buyer_reference (Leitweg-ID for German authorities) and payment details (iban). Peppol needs peppol_id for seller and buyer.

Input parameters:

- `bic` (string)
- `buyer` (object, required)
- `buyer_reference` (string)
- `credit_note` (boolean)
- `currency` (string)
- `due_date` (string): YYYY-MM-DD, default issue + 14 days
- `format` (string)
- `iban` (string)
- `issue_date` (string): YYYY-MM-DD, default today
- `lines` (array, required)
- `note` (string)
- `number` (string, required)
- `order_reference` (string)
- `payment_reference` (string)
- `payment_terms` (string)
- `period_end` (string)
- `period_start` (string)
- `preceding_invoice` (string): Original invoice number (credit notes)
- `seller` (object, required)

### `read_invoice_pdf` (~179 tokens)

Read a PDF invoice

Read an ordinary (non-e-invoice) PDF invoice and return its data in the input format of create_einvoice: seller and buyer (name, address, VAT ID, country), invoice number, dates, IBAN/BIC, Leitweg-ID and the invoice lines (only if quantity x price and the line sum match the PDF's net total; otherwise one line with the net total). Regex-based, no guessing: fields we can't read reliably are missing and listed in `missing`. Check and complete them, then call create_einvoice to get XRechnung, ZUGFeRD or Peppol. Scanned PDFs (no text layer) are not supported. Pass the PDF base64-encoded in `file_base64`. Max 5 MB.

Input parameters:

- `file_base64` (string, required): The PDF invoice, base64-encoded.

### `explain_rule` (~105 tokens)

Explain a validation rule

Explain an e-invoice business rule code (EN 16931 BR-*, BR-CO-*, XRechnung BR-DE-*, Peppol PEPPOL-EN16931-*): official text (with an English translation for German-only rules), plain-language meaning, severity, the fields (BT/BG) involved and a link to the reference page.

Input parameters:

- `code` (string, required): Rule code, e.g. BR-DE-15 or BR-CO-10.

## Diagnostics

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

## Score history

- 2026-10-22: 69
- 2026-10-21: 68

## Common questions

### What is the Invoiceer e-invoicing tools MCP server?

Invoiceer e-invoicing tools is an MCP server listed in the public MCP registry as io.invoiceer/einvoicing. Create and validate XRechnung, ZUGFeRD and Peppol e-invoices (KoSIT); Peppol lookup, rule help. This page covers its hosted endpoint (https://invoiceer.io/mcp).

### Is the Invoiceer e-invoicing tools MCP server safe to use?

Invoiceer e-invoicing tools scores 69 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 Invoiceer e-invoicing tools MCP server expose?

Invoiceer e-invoicing tools exposes 6 tools: validate_einvoice, peppol_lookup, check_leitweg_id, create_einvoice, read_invoice_pdf, explain_rule. Their descriptions and schemas cost roughly 982 tokens of context every time the server is loaded.

### Does the Invoiceer e-invoicing tools MCP server require authentication?

No. We connected to Invoiceer e-invoicing tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Invoiceer e-invoicing tools MCP server still maintained?

Invoiceer e-invoicing tools is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://invoiceer.io/mcp
- Website: https://invoiceer.io/api
- Changelog RSS feed: https://verifymcp.io/servers/io-invoiceer-einvoicing/invoiceer.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-invoiceer-einvoicing/invoiceer.json
- HTML version of this page: https://verifymcp.io/servers/io-invoiceer-einvoicing/invoiceer