# InkVoice — XRechnung & E-Invoicing > XRechnung and ZUGFeRD e-invoicing (EN 16931): create, validate, check Leitweg-IDs, German VAT. - name: net.inkvoice/inkvoice - version: 1.1.0 - connection class: R0 (autonomous) - trust: 80/100 flags: no-repository - quality: 86/100 (good) - owner: not claimed - descriptor: https://api.protogrid.dev/v1/servers/net.inkvoice%2Finkvoice - tools: https://api.protogrid.dev/v1/servers/net.inkvoice%2Finkvoice/tools **An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe. ## Connection (mcpServers) ```json { "mcpServers": { "inkvoice": { "type": "http", "url": "https://api.inkvoice.net/mcp", "headers": { "Authorization": "Bearer ${INKVOICE_TOKEN}" } } } } ``` Placeholders to fill: `${INKVOICE_TOKEN}`. ## Trust - hygiene: 80 - liveness: 100 - freshness: 85 - provenance: 55 - drivers: +dns-namespace +website +reachable +uptime-100% ~updated-30d-ago -no-repository - Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. ## Quality 86/100 (good) ### protocol: 88 (weight 25) - pass `protocol.modern`: supports 2026-07-28 (server/discover) - pass `protocol.stateless`: answers without a session - pass `protocol.transport`: streamable HTTP - warn `protocol.list_ttl`: tools/list declares ttlMs 0, so clients re-fetch it on every use ### authorization: n/a (weight 15) - n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth - n/a `auth.secret_in_url`: no templated URL ### tool hygiene: 79 (weight 30) - pass `tools.descriptions`: every tool has a description - warn `tools.description_length`: 4 tools have descriptions over 1,024 characters, which crowds the context - pass `tools.schemas`: every tool has an object input schema - pass `tools.annotations`: 5 of 5 tools declare readOnlyHint or destructiveHint - fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: check_leitweg_id (destructiveHint, idempotentHint); create_zugferd (destructiveHint, idempotentHint); calculate_vat (destructiveHint, idempotentHint); … - pass `tools.token_cost`: about 3,053 tokens to load every tool - pass `tools.api_dump`: tools are not a one-to-one API dump ### stability: 100 (weight 15) - pass `stability.changes`: 2 tool changes in 30 days - pass `stability.rug_pull`: no tool changed its meaning under the same name ### dependencies: n/a (weight 15) - n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package - tools: 5, about 3,053 tokens to load them all - tool set hash: 9ec681f2b11c63f111edc571eabf8232 - tools last changed: 2026-10-14T09:09:14.985Z - badge: [![protogrid quality](https://protogrid.dev/badge/net.inkvoice/inkvoice.svg)](https://protogrid.dev/servers/net.inkvoice/inkvoice) - Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. ### Tool changes - 2026-10-14 `create_xrechnung` changed (description) - before: Builds a German XRechnung 3.x electronic invoice (EN 16931, CII syntax) from invoice details and returns the XML as text. This is the format German public-sector buyers are legally required to receive, and that many private B2B buyers now ask for. The EN 16931 business rules are checked before anything is built, and a rejected call comes back naming the rules that failed and the business term (BT-xx) each concerns. The ones worth getting right up front: tax category S requires a rate above 0 %, categories Z, E and AE require exactly 0 %, E and AE additionally require a stated exemption reason (BT-120), and both parties need an email address because XRechnung makes the electronic address (BT-34, BT-49) mandatory. For a public-sector buyer, put their Leitweg-ID in buyerReference (BT-10) — check_leitweg_id will verify it first. What this does NOT do: - It does not validate against the KoSIT Prüftool. It applies our reading of EN 16931, which is not the same thing as the Schematron suite a receiving portal runs. Use validate_einvoice for a second look, and the official validator before a deadline. - It does not produce ZUGFeRD or Factur-X. There is no PDF and no embedded XML — this is a bare XML file. Use create_zugferd for the hybrid a private-sector B2B buyer usually wants. - It handles ONE tax rate and one tax category for the whole invoice. A document mixing 19 % and 7 % lines is not expressible here. - It does not send the invoice anywhere, and there is no Peppol. Nothing is stored: no account, no invoice record, no retained personal data. - after: Builds a German XRechnung 3.x electronic invoice (EN 16931, CII syntax) from invoice details and returns the XML as text. This is the format German public-sector buyers are legally required to receive, and that many private B2B buyers now ask for. The EN 16931 business rules are checked before anything is built, and a rejected call comes back naming the rules that failed and the business term (BT-xx) each concerns. The ones worth getting right up front: tax category S requires a rate above 0 %, categories Z, E and AE require exactly 0 %, E and AE additionally require a stated exemption reason (BT-120), both parties need an email address because XRechnung makes the electronic address (BT-34, BT-49) mandatory, and an IBAN (BT-84) is required, because XRechnung makes payment instructions (BG-16) mandatory (BR-DE-1). For a public-sector buyer, put their Leitweg-ID in buyerReference (BT-10) — check_leitweg_id will verify it first. What this does NOT do: - It does not validate against the KoSIT Prüftool. It applies our reading of EN 16931, which is not the same thing as the Schematron suite a receiving portal runs. Use validate_einvoice for a second look, and the official validator before a deadline. - It does not produce ZUGFeRD or Factur-X. There is no PDF and no embedded XML — this is a bare XML file. Use create_zugferd for the hybrid a private-sector B2B buyer usually wants. - It handles ONE tax rate and one tax category for the whole invoice. A document mixing 19 % and 7 % lines is not expressible here. - It does not send the invoice anywhere, and there is no Peppol. Nothing is stored: no account, no invoice record, no retained personal data. - 2026-10-14 `create_zugferd` changed (description) - before: Builds a ZUGFeRD 2.x / Factur-X hybrid invoice from the same details create_xrechnung takes, and returns it as a PDF file. A hybrid is one invoice stated twice in one file: a PDF/A-3 document a person reads, carrying the same invoice inside it as EN 16931 XML a machine books. This is the format private-sector German B2B buyers generally want, where XRechnung is what public bodies require. If the recipient is a public authority and gave you a Leitweg-ID, you want create_xrechnung instead. The embedded XML declares plain EN 16931 — the profile ZUGFeRD calls COMFORT — not the XRechnung CIUS, because that CIUS is a statement about public-sector procurement. Validation is identical to create_xrechnung: the same EN 16931 rules are applied before anything is built, and a rejected call names the rules and business terms that failed. What this does NOT do: - The result is a binary PDF returned as an attachment. It is not text and there is nothing useful to read in it — do not try to quote or summarise its contents. Offer it to the user as a file. - It does not validate against veraPDF or the Mustangproject validator. The document is built to be valid PDF/A-3 with the required Factur-X metadata, but that is our reading rather than a validator's verdict. - It handles ONE tax rate and one tax category for the whole invoice, exactly as create_xrechnung does. - It does not send the invoice anywhere, and there is no Peppol. - There is no logo and no custom styling. The PDF uses the default invoice layout. Nothing is stored: no account, no invoice record, no retained personal data. - after: Builds a ZUGFeRD 2.x / Factur-X hybrid invoice from the same details create_xrechnung takes, and returns it as a PDF file. A hybrid is one invoice stated twice in one file: a PDF/A-3 document a person reads, carrying the same invoice inside it as EN 16931 XML a machine books. This is the format private-sector German B2B buyers generally want, where XRechnung is what public bodies require. If the recipient is a public authority and gave you a Leitweg-ID, you want create_xrechnung instead. The embedded XML declares plain EN 16931 — the profile ZUGFeRD calls COMFORT — not the XRechnung CIUS, because that CIUS is a statement about public-sector procurement. Validation is identical to create_xrechnung, except that the IBAN is optional here (EN 16931 makes BG-16 optional): the same EN 16931 rules are applied before anything is built, and a rejected call names the rules and business terms that failed. What this does NOT do: - The result is a binary PDF returned as an attachment. It is not text and there is nothing useful to read in it — do not try to quote or summarise its contents. Offer it to the user as a file. - It does not validate against veraPDF or the Mustangproject validator. The document is built to be valid PDF/A-3 with the required Factur-X metadata, but that is our reading rather than a validator's verdict. - It handles ONE tax rate and one tax category for the whole invoice, exactly as create_xrechnung does. - It does not send the invoice anywhere, and there is no Peppol. - There is no logo and no custom styling. The PDF uses the default invoice layout. Nothing is stored: no account, no invoice record, no retained personal data. Full history: https://api.protogrid.dev/v1/servers/net.inkvoice%2Finkvoice/changes ## Remotes - https://api.inkvoice.net/mcp (streamable-http, auth none, reachable true, uptime30d 1) ## Packages _none_ ## Tools (5) - `calculate_vat`: Converts between net, tax and gross for a given VAT rate, in either direction. Give an amount and say whether it is net or gross, and you get all three figures back rounded to the cent. Germany's rates are 19 % (standard) and 7 % (reduced), but any rate from 0 to 100 is accepted, so this also works for an Austrian or French invoice. Rounding is half-away-from-zero, the convention invoices and tax authorities use, and the three returned figures always reconcile: net plus tax equals gross exactly, with no cent left over from rounding each separately. What this does NOT do: it does not decide which rate applies to a supply, handle more than one rate at a time, or know anything about reverse charge, intra-community supply or the Kleinunternehmer rules. It is arithmetic, not tax advice. - `check_leitweg_id`: Checks a German Leitweg-ID — the routing identifier that goes in BT-10 of an XRechnung to a public authority. An invoice to a German public body with a wrong or missing Leitweg-ID is rejected, so this is worth checking before building a document. It verifies the structure (Grobadressierung of 2 to 12 digits, an optional Feinadressierung of up to 30 alphanumerics, then two check digits) and recomputes the ISO/IEC 7064 MOD 97-10 check digit, the same procedure an IBAN uses. When the check digits are wrong it returns the ones the address parts actually imply, so the value can be corrected rather than merely rejected. It also names the Bundesland the leading two digits point at, or Bund for the federation. One real limit: the check digit is computed over the address parts with the hyphens removed, which is what KoSIT specifies, so it CANNOT detect a hyphen in the wrong place. '04011000-1234512345-06' and '040110001-234512345-06' both pass. That is the specification's behaviour, not a defect here. What this does NOT do: it does not confirm that the ID belongs to a real authority or that they are reachable. It checks the number, not the recipient — there is no directory lookup. - `create_xrechnung`: Builds a German XRechnung 3.x electronic invoice (EN 16931, CII syntax) from invoice details and returns the XML as text. This is the format German public-sector buyers are legally required to receive, and that many private B2B buyers now ask for. The EN 16931 business rules are checked before anything is built, and a rejected call comes back naming the rules that failed and the business term (BT-xx) each concerns. The ones worth getting right up front: tax category S requires a rate above 0 %, categories Z, E and AE require exactly 0 %, E and AE additionally require a stated exemption reason (BT-120), both parties need an email address because XRechnung makes the electronic address (BT-34, BT-49) mandatory, and an IBAN (BT-84) is required, because XRechnung makes payment instructions (BG-16) mandatory (BR-DE-1). For a public-sector buyer, put their Leitweg-ID in buyerReference (BT-10) — check_leitweg_id will verify it first. What this does NOT do: - It does not validate against the KoSIT Prüftool. It applies our reading of EN 16931, which is not the same thing as the Schematron suite a receiving portal runs. Use validate_einvoice for a second look, and the official validator before a deadline. - It does not produce ZUGFeRD or Factur-X. There is no PDF and no embedded XML — this is a bare XML file. Use create_zugferd for the hybrid a private-sector B2B buyer usually wants. - It handles ONE tax rate and one tax category for the whole invoice. A document mixing 19 % and 7 % lines is not expressible here. - It does not send the invoice anywhere, and there is no Peppol. Nothing is stored: no account, no invoice record, no retained personal data. - `create_zugferd`: Builds a ZUGFeRD 2.x / Factur-X hybrid invoice from the same details create_xrechnung takes, and returns it as a PDF file. A hybrid is one invoice stated twice in one file: a PDF/A-3 document a person reads, carrying the same invoice inside it as EN 16931 XML a machine books. This is the format private-sector German B2B buyers generally want, where XRechnung is what public bodies require. If the recipient is a public authority and gave you a Leitweg-ID, you want create_xrechnung instead. The embedded XML declares plain EN 16931 — the profile ZUGFeRD calls COMFORT — not the XRechnung CIUS, because that CIUS is a statement about public-sector procurement. Validation is identical to create_xrechnung, except that the IBAN is optional here (EN 16931 makes BG-16 optional): the same EN 16931 rules are applied before anything is built, and a rejected call names the rules and business terms that failed. What this does NOT do: - The result is a binary PDF returned as an attachment. It is not text and there is nothing useful to read in it — do not try to quote or summarise its contents. Offer it to the user as a file. - It does not validate against veraPDF or the Mustangproject validator. The document is built to be valid PDF/A-3 with the required Factur-X metadata, but that is our reading rather than a validator's verdict. - It handles ONE tax rate and one tax category for the whole invoice, exactly as create_xrechnung does. - It does not send the invoice anywhere, and there is no Peppol. - There is no logo and no custom styling. The PDF uses the default invoice layout. Nothing is stored: no account, no invoice record, no retained personal data. - `validate_einvoice`: Reads an existing electronic invoice and reports what is wrong with it. Accepts XRechnung and ZUGFeRD XML in either EN 16931 syntax — CII (used by XRechnung and ZUGFeRD) and UBL — and reports the syntax and profile it found along with the invoice's key fields, so it also answers "what is this file?". It checks the rules behind most real rejections: BT-10 buyer reference present, and its Leitweg-ID check digit when it looks like one; BT-34 and BT-49 electronic addresses present; tax category S not used at 0 %; BT-120 exemption reason present for categories E and AE; line amounts summing to BT-106; net plus tax equalling the BT-112 gross; BT-115 amount due matching gross less prepaid; and the due date not falling before the issue date. What this does NOT do: - It is NOT the KoSIT Prüftool and is not a substitute for it. It covers the rules that account for most rejections, not the full EN 16931 Schematron suite. A file that passes here can still be rejected by a Rechnungseingangsportal. - It does not check the XSD schema, so a structurally invalid document may parse here. - It reads XML only. A ZUGFeRD PDF must have its embedded XML extracted first — pass the XML, not the PDF. Nothing is stored: the document is parsed in memory and discarded.