MCP server for AI agents: validate e-invoices

With the eRechio MCP server, an AI agent or assistant can have an XRechnung (UBL or CII) or the XML of a ZUGFeRD/Factur-X invoice validated and gets the same answer as from the REST API: schema check, KoSIT rule check, every message with an explanation.

Address: https://api.erechio.de/mcp · Model Context Protocol, transport “Streamable HTTP” · since API version 1.4.0 (22 Nov 2026). Sign in with your existing API key. Get a test key now: free, 50 documents per month.

Good to know: the JSON field names and the detailed explanations (erklaerung) in the results are in German; the API reference translates every field.

Setup

You need an API key (pk_…), for example the test key. Send it as header Authorization: Bearer pk_… (alternatively X-API-Key). There is no OAuth.

Claude Code

claude mcp add --transport http erechio https://api.erechio.de/mcp --header "Authorization: Bearer pk_YOUR_KEY"

Other clients (for example Cursor, VS Code)

Clients with remote MCP over HTTP usually read a JSON configuration. Field names differ slightly between clients; check your client's documentation.

{
  "mcpServers": {
    "erechio": {
      "type": "http",
      "url": "https://api.erechio.de/mcp",
      "headers": {
        "Authorization": "Bearer pk_YOUR_KEY"
      }
    }
  }
}

Test with curl

The tool list can be fetched without a key:

curl -s https://api.erechio.de/mcp -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Technical details

Tools

ToolArgumentsResult
validate_invoicexml (required): the invoice as XML text – XRechnung UBL/CII or the XML of a ZUGFeRD/Factur-X invoice, at most 2 MB.
idempotency_key (optional): like the Idempotency-Key header, see idempotency; same rules.
structuredContent is exactly the response of POST /v1/validate with the same fields (vollstaendig_validiert, regelpruefung_bestanden, schemapruefung, meldungen with erklaerung, kontingent, regelstand and so on; field list: response). Plus a short German summary as text.
explain_rulecode (required): a rule code as reported by a validator, e.g. BR-DE-15; also from other validators such as the KoSIT validator.German explanation: titel, was (what the rule requires), beheben (how to fix), pfad_ubl, pfad_cii and mehr (link to the error page). The most frequent rules are covered; for other codes the result is gefunden: false, not an error. No key needed, not counted.
get_statusnoneThe response of GET /v1/status. No key needed, not counted.

With validate_invoice, rely on vollstaendig_validiert, not on the text summary. A successful call only means the validation ran, not that the invoice is free of errors.

Limits and quota

The same quota and limits as the REST API apply: each successful validation counts one document against your key's monthly quota (test key: 50 documents per month), at most 60 validations per minute, at most 2 MB per invoice. Calls via REST and MCP share the same quota.

Errors

API errors (401, 413, 422, 429 …) arrive as a tool result with isError=true and the same error code and text as in the API (status codes). A missing or invalid key on validate_invoice is a 401.

Privacy

The invoice is validated in memory only and then discarded, not stored, as with the REST API. Per validation we log only time, key identifier, syntax, result, number of errors and duration, without IP address (details: API privacy). Note that your AI client or its provider also sees the invoice; that is outside eRechio.

What does not exist

Technical notes on the data format, not tax or legal advice. eRechio is not an offering of KoSIT. Back to the API reference.