← Registry

API Tools

invoiceer.io

An MCP server for validating, creating, and reading e-invoices and checking Peppol and Leitweg-ID eligibility.

1 endpoint6 known toolsFirst detected October 22, 2026Last detected October 22, 2026

ENDPOINT 1

https://invoiceer.io/mcp

No auth detected

MCP server metadata

Name
invoiceer
Version
1.0.0
Capabilities
tools
Server instructions

Invoiceer e-invoicing tools: validate XRechnung / ZUGFeRD / Factur-X / Peppol BIS invoices with the official KoSIT validator, look up Peppol participants, check German Leitweg-IDs and explain EN 16931 / XRechnung / Peppol business rules (e.g. BR-DE-15), and create valid e-invoices from structured data. Files are checked in memory and not stored. Stripe users can create these e-invoices automatically: https://invoiceer.io/stripe

Known tools 6

validate_einvoice

Validate an e-invoice (XRechnung UBL/CII, ZUGFeRD / Factur-X PDF, Peppol BIS Billing 3.

Potential side effects
peppol_lookup

Check whether a company can receive e-invoices over Peppol.

Inferred read-only
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.

Inferred read-only
create_einvoice

Create a valid e-invoice from structured data: XRechnung 3.

Potential side effects
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).

Potential side effects
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.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.invoiceer]
url = "https://invoiceer.io/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "invoiceer": {
      "type": "http",
      "url": "https://invoiceer.io/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: invoiceer
Remote MCP URL: https://invoiceer.io/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "invoiceer": {
      "url": "https://invoiceer.io/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "invoiceer": {
      "type": "http",
      "url": "https://invoiceer.io/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "invoiceer",
  "transport": "streamable-http",
  "url": "https://invoiceer.io/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.