InkVoice — XRechnung & E-Invoicing MCP server
net.inkvoice/inkvoiceinkvoice.netstreamable-httpv1.1.0Scanned
XRechnung and ZUGFeRD e-invoicing (EN 16931): create, validate, check Leitweg-IDs, German VAT.
5 tools: 4 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 3 findings
Tools listed without sign-in. Remote posture
Anlyon alternative
4 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the InkVoice — XRechnung & E-Invoicing MCP server can do
The InkVoice — XRechnung & E-Invoicing MCP server is published by inkvoice.net, a domain the MCP Registry verified. It has 5 tools. It can create or change data (4 tools: create_zugferd, calculate_vat, create_xrechnung and check_leitweg_id), but cannot delete data. 1 tool only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 3 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 18, 2026, version 1.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Changes things 4Claude Code: ask
calculate_vatConverts between net, tax and gross for a given VAT rate, in either direction.1 finding
Why it is in this group
- The description's first verb is "convert": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "calculate_vat" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "convert": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- title: Calculate German VAT
- openWorldHint: false
- readOnlyHint: true
check_leitweg_idChecks a German Leitweg-ID — the routing identifier that goes in BT-10 of an XRechnung to a public authority.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check a Leitweg-ID
- openWorldHint: false
- readOnlyHint: true
create_xrechnungBuilds a German XRechnung 3.x electronic invoice (EN 16931, CII syntax) from invoice details and returns the XML as text.1 finding
Why it is in this group
- The name "create_xrechnung" says "create": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "create_xrechnung" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "create_xrechnung" says "create": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- title: Create an XRechnung
- openWorldHint: false
- readOnlyHint: true
create_zugferdBuilds a ZUGFeRD 2.x / Factur-X hybrid invoice from the same details create_xrechnung takes, and returns it as a PDF file.1 finding
Why it is in this group
- The name "create_zugferd" says "create": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "create_zugferd" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "create_zugferd" says "create": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- title: Create a ZUGFeRD / Factur-X invoice
- openWorldHint: false
- readOnlyHint: true
Only reads 1Show 1 read-only tool
validate_einvoiceReads an existing electronic invoice and reports what is wrong with it.No findings
Why it is in this group
- The name "validate_einvoice" says "validate": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Check an e-invoice
- openWorldHint: false
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:16 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://api.inkvoice.net/.well-known/oauth-protected-resource/mcp
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.inkvoice.net/mcp: tools/list returned 5 tools to an anonymous client, including create_zugferd (write), calculate_vat (write), create_xrechnung (write), check_leitweg_id (write)
Findings
Matches of fixed checks, with the text they matched.
- Warncreate_zugferd
The server marks "create_zugferd" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "create_zugferd" says "create": a word for a change.
- Warncalculate_vat
The server marks "calculate_vat" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The description's first verb is "convert": a word for a change.
- Warncreate_xrechnung
The server marks "create_xrechnung" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"openWorldHint":false}; The name "create_xrechnung" says "create": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http inkvoice https://api.inkvoice.net/mcpclaude mcp add --transport http inkvoice https://api.inkvoice.net/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__inkvoice__validate_einvoice"
],
"ask": [
"mcp__inkvoice__create_zugferd",
"mcp__inkvoice__calculate_vat",
"mcp__inkvoice__create_xrechnung",
"mcp__inkvoice__check_leitweg_id"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as inkvoice. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/net.inkvoice/inkvoice/verify?hash=4402a9f7a2960abbda842ffecc91b082f5850c057c463d17e9d44b9e7aa104be" | jq -e '.changed == false'Pinned hash 4402a9f7a296, from Nov 18, 2026, 20:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/net.inkvoice/inkvoice/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/net.inkvoice/inkvoice)Source: MCP Registry. Synced Oct 21, 2026, 18:53 UTC.
InkVoice — XRechnung & E-Invoicing MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the InkVoice — XRechnung & E-Invoicing MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 4 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the InkVoice — XRechnung & E-Invoicing MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the InkVoice — XRechnung & E-Invoicing MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the InkVoice — XRechnung & E-Invoicing MCP server have?
- 5 tools: 4 write, 1 read. create_zugferd, calculate_vat, create_xrechnung, check_leitweg_id and validate_einvoice.
Does the InkVoice — XRechnung & E-Invoicing MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the InkVoice — XRechnung & E-Invoicing MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the InkVoice — XRechnung & E-Invoicing MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 18, 2026.