All servers · Payments & accounting
NormAPI
com.normapi/mcp · v1.2.0
New (7 days)Tools changed (7 days)
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Can write (some tools are not declared read-only) |
| Capabilities declared | tools |
| Tool definitions | 4 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Description written by the publisher, not verified
Validate, generate and read German e-invoices (XRechnung, ZUGFeRD) against the official KoSIT rules.
Connect
streamable-http · https://normapi.com/mcp
claude mcp add --transport http mcp https://normapi.com/mcp{
"mcpServers": {
"mcp": {
"url": "https://normapi.com/mcp"
}
}
}Tools as reported by the server
validate_invoiceCheck 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 `pdparse_invoiceRead a received e-invoice — XRechnung or any EN 16931 invoice as UBL or CII XML, or a ZUGFeRD/Factur-X PDF — into structured data. `invoice` is in exactly the shape generate_invoice takes (fields the document lacks are left out); `stated` has the totals, the VAT breakdown and each line net as the dogenerate_invoiceProduce an e-invoice as `ubl` or `cii` XML or a ZUGFeRD hybrid PDF (`zugferd`) from invoice data: an XRechnung for a public-sector buyer (profile `xrechnung`, the default), a plain EN 16931 invoice for a business (profile `en16931`). Totals are computed server-side in decimal arithmetic, and the docexplain_ruleExplain 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.
Tool changes
- 2026-10-24: validate_invoice, parse_invoice, generate_invoice, explain_rule
- 2026-10-23: validate_invoice, generate_invoice, explain_rule
- 2026-10-16: validate_invoice, generate_invoice, explain_rule
Website · JSON · Text for agents · Registry updated 2026-10-23