Invoiceer e-invoicing tools MCP Server

by invoiceer Your server? Claim it

answering

Invoiceer e-invoicing tools is answering right now. Last checked 3 min ago. It exposes 6 tools.

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

Uptime history 5 days of history · worst day 99%

5 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

363 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 7

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 22 October 2026. No other catalogue keeps this.

23 Oct a tool changed the parameters it asks for3 times that day create_einvoice

22 Oct 2 tools changed the parameters they ask for create_einvoice, validate_einvoice

22 Oct a tool appeared read_invoice_pdf

22 Oct a tool description was rewritten check_leitweg_id

and 2 more, back to 22 October 2026

Invoiceer e-invoicing tools missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add einvoicing --transport http https://invoiceer.io/mcp

Settings → Connectors → Add custom connector, then paste this address

https://invoiceer.io/mcp

~/.codex/config.toml

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

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 6

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

einvoice

create_einvoice

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.

explain

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

invoice

read_invoice_pdf

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.

leitweg

check_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), and whether the authority is registered on Peppol (peppol_registered). Returns validity, the parts and the expected check digits.

peppol

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

validate

validate_einvoice

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.

Endpoints

URL	Transport	State	Latency	Checked
https://invoiceer.io/mcp	streamable-http	answering	154 ms	3 min ago

Alternatives to Invoiceer e-invoicing tools

same job, measured the same way

NormAPI

by normapi

Validate, generate and read German e-invoices (XRechnung, ZUGFeRD) against the official KoSIT rules.

209 installs/wk 4 tools answering

E-Invoice Checker

by einvoicechecker

Validate, parse and render EU e-invoices: XRechnung, ZUGFeRD, Factur-X, Peppol BIS 3.0, KSeF.

8 tools answering

Einvoice

by makririch

XRechnung & ZUGFeRD: create, validate, and convert German e-invoices. EN 16931 compliant.

17 installs/wk local only

E-invoice validator & repair check (XRechnung, Peppol BIS 3, EN 16931)

by nyo-agentti

Validate XRechnung, Peppol BIS 3 and EN 16931 invoices with KoSIT; explain rules; check auto-repair

2 tools answering

Kontor MCP

by dashankanadeeshandesilva

Offline e-invoice tools for AI agents: validate, audit, convert and generate XRechnung/ZUGFeRD.

31 installs/wk local only

Invapi MCP

by invapi-org

Extract, create, convert & validate invoices (UBL, CII, XRechnung, ZUGFeRD, PDF, Excel)

21 installs/wk local only

Xrechnung MCP

by imysfylmz

Validate and parse German e-invoices (XRechnung, ZUGFeRD, Factur-X) offline. No API key.

17 installs/wk local only

Tallystick

by tally-stick

Read, validate and write e-invoices on your own machine. XRechnung, ZUGFeRD, Factur-X, UBL, CII.

108 installs/wk local only

Invoiceer e-invoicing tools — questions

Answers built from our own checks of this server.

What can Invoiceer e-invoicing tools do?

It exposes 6 tools, read directly from the server on our last check. Among them: check_leitweg_id, create_einvoice, explain_rule, peppol_lookup, read_invoice_pdf, validate_einvoice. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Invoiceer e-invoicing tools working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 363 ms. The bar chart above shows every period we have measured.

How do I connect Invoiceer e-invoicing tools?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Invoiceer e-invoicing tools need an API key?

No. Invoiceer e-invoicing tools completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 6 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Invoiceer e-invoicing tools?

It answers our handshake in 363 ms on average, which is faster than 41% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.