com.normapi/mcp · v1.0.1 · finance-and-payments
NormAPI is healthy: it completed an MCP handshake in 2706 ms and exposes 3 tools.
Validate and generate German e-invoices (XRechnung, ZUGFeRD) against the official KoSIT rules.
Endpoint: https://normapi.com/mcp (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 3 |
| Latency | 2706 ms |
| Last checked (UTC) | 2026-10-14T20:50:48.411Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-14T20:50:48.411Z | Healthy | 2706 |
validate_invoice | Check an XRechnung (UBL or CII XML) or a ZUGFeRD/Factur-X PDF against the official KoSIT rules. Returns the verdict, the rule set version, and every finding; each business-rule finding comes with a plain-language meaning, cause and fix. Send the XML as text in `xml`, or the PDF base64-encoded in `pd |
generate_invoice | Produce an XRechnung (`ubl` or `cii` XML) or a ZUGFeRD hybrid PDF (`zugferd`) from invoice data. Totals are computed server-side in decimal arithmetic, and the document is validated against the official rules before it is returned. Data the rules do not permit is refused with the broken rules and ho |
explain_rule | Explain one EN 16931 / XRechnung / Peppol business rule by its code (e.g. BR-DE-15, BR-CO-10, PEPPOL-EN16931-R010): what it requires, why invoices typically break it, and how to fix it, with a link to the full page. Case does not matter. Schema findings (cvc-*) have no explanation. |