German e-invoicing: generate XRechnung 3.0, pre-check and extract (incl. ZUGFeRD PDF). Paid.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://invoice-api.dropcoin.workers.dev/mcp3 tools · 581msgenerate_xrechnungGenerate a German XRechnung 3.0 e-invoice (UBL 2.1, EN 16931) from plain JSON. Totals, VAT and rounding are computed server-side per the official rules. Mandatory: invoiceNumber, issueDate, buyerReference (Leitweg-ID), seller (+sellerContact with name/phone/email), buyer, paymentIban, lines (name,…Generate a German XRechnung 3.0 e-invoice (UBL 2.1, EN 16931) from plain JSON. Totals, VAT and rounding are computed server-side per the official rules. Mandatory: invoiceNumber, issueDate, buyerReference (Leitweg-ID), seller (+sellerContact with name/phone/email), buyer, paymentIban, lines (name,…
| Parameter | Type | Description |
|---|---|---|
| invoiceNumber* | string | — |
| issueDate* | string | YYYY-MM-DD |
| dueDate | string | — |
| paymentTermsNote | string | — |
| buyerReference* | string | Leitweg-ID / buyer reference (mandatory) |
| seller* | object | — |
| sellerContact* | object | — |
| buyer* | object | — |
| paymentIban* | string | — |
| lines* | array | — |
validate_invoicePre-check an e-invoice (XRechnung UBL or CII XML) against the priority EN 16931 / XRechnung rules incl. cent-exact totals recalculation. Findings carry official rule IDs. A pre-check, not the official KoSIT validation. 10 credits, requires an API key.Pre-check an e-invoice (XRechnung UBL or CII XML) against the priority EN 16931 / XRechnung rules incl. cent-exact totals recalculation. Findings carry official rule IDs. A pre-check, not the official KoSIT validation. 10 credits, requires an API key.
| Parameter | Type | Description |
|---|---|---|
| xml* | string | Invoice XML, max 2 MB |
extract_invoiceExtract structured JSON (parties, lines, totals, payment data) from an e-invoice: XRechnung UBL/CII XML or a ZUGFeRD/Factur-X PDF (embedded XML is pulled from the PDF). Send exactly one of xml / pdfBase64. 5 credits, requires an API key.Extract structured JSON (parties, lines, totals, payment data) from an e-invoice: XRechnung UBL/CII XML or a ZUGFeRD/Factur-X PDF (embedded XML is pulled from the PDF). Send exactly one of xml / pdfBase64. 5 credits, requires an API key.
| Parameter | Type | Description |
|---|---|---|
| xml | string | — |
| pdfBase64 | string | Base64-encoded PDF, max ~2 MB |
3 of 3 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
German e-invoicing: generate XRechnung 3.0, pre-check and extract (incl. ZUGFeRD PDF). Paid.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.