Invoiceer e-invoicing tools MCP server
io.invoiceer/einvoicinginvoiceer.iostreamable-httpv1.1.0Scanned
Create and validate XRechnung, ZUGFeRD and Peppol e-invoices (KoSIT); Peppol lookup, rule help.
6 tools: 3 change things and 3 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 1
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Invoiceer e-invoicing tools MCP server can do
The Invoiceer e-invoicing tools MCP server is published by invoiceer.io, a domain the MCP Registry verified. It has 6 tools. It can create or change data (3 tools: check_leitweg_id, create_einvoice and explain_rule), but cannot delete data. 3 tools only read.
1 tool reads private data (read_invoice_pdf); 1 tool brings in text other people can write (peppol_lookup); 1 tool can send data out of your system (create_einvoice). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
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.
6 tools
Changes things 3Claude Code: ask
check_leitweg_idCheck a German Leitweg-ID (buyer reference BT-10 for invoices to German public authorities) against the official format and check digit (spec v2.0.2), and whether the authority is …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 Check a German Leitweg-ID (buyer reference BT-10 for invoices to German public authorities) against the official format and check digit (spec v2.0.2), and whether the authority is registered on Peppol (peppol_registered). Returns validity, the parts and the expected check digits.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
create_einvoiceCreate a valid e-invoice from structured data: XRechnung 3.0 (UBL or CII), ZUGFeRD / Factur-X PDF (EN 16931) or Peppol BIS Billing 3.0.Can send data out1 finding
Why it is in this group
- The name "create_einvoice" says "create": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a destination (input.seller.phone): what the tool writes goes there.
Findings
- Warn
The server marks "create_einvoice" 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_einvoice" says "create": a word for a change.
Description, as the server wrote it Create a valid e-invoice from structured data: XRechnung 3.0 (UBL or CII), ZUGFeRD / Factur-X PDF (EN 16931) or Peppol BIS Billing 3.0. The file is checked with the official KoSIT validator before it is returned; if it fails, you get the rule errors instead of a file. XML comes back as text in `xml`, the ZUGFeRD PDF as base64 in `pdf_base64`. XRechnung needs a seller contact (contact, phone, email), a buyer email or Peppol ID (electronic address), a buyer_reference (Leitweg-ID for German authorities) and payment details (iban). Peppol needs peppol_id for seller and buyer.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
explain_ruleExplain an e-invoice business rule code (EN 16931 BR-*, BR-CO-*, XRechnung BR-DE-*, Peppol PEPPOL-EN16931-*): official text (with an English translation for German-only rules), pla…1 finding
Why it is in this group
- The name "explain_rule" says "explain": a word for reading.
- The input takes a statement or command to run (input.code), which can change anything it can reach.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "explain_rule" 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 "explain_rule" says "explain": a word for reading.
Description, as the server wrote it Explain an e-invoice business rule code (EN 16931 BR-*, BR-CO-*, XRechnung BR-DE-*, Peppol PEPPOL-EN16931-*): official text (with an English translation for German-only rules), plain-language meaning, severity, the fields (BT/BG) involved and a link to the reference page.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
Only reads 3Show 3 read-only tools
peppol_lookupCheck whether a company can receive e-invoices over Peppol.Reads text others writeNo findings
Why it is in this group
- The name "peppol_lookup" says "lookup": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Check whether a company can receive e-invoices over Peppol. Accepts a Peppol ID (e.g. 0208:0123456749), a VAT number (e.g. BE0123456749, NL...B01) or a Belgian enterprise number. Returns each matching participant ID, whether it is registered, whether it accepts Peppol BIS invoices, and name/country from the Peppol Directory when published.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: true
read_invoice_pdfRead an ordinary (non-e-invoice) PDF invoice and return its data in the input format of create_einvoice: seller and buyer (name, address, VAT ID, country), invoice number, dates, I…Reads private dataNo findings
Why it is in this group
- The name "read_invoice_pdf" says "read": a word for reading.
What it can reach
- private-dataThe input names a file (input.file_base64), and the tool reads: it reads files.
Description, as the server wrote it Read an ordinary (non-e-invoice) PDF invoice and return its data in the input format of create_einvoice: seller and buyer (name, address, VAT ID, country), invoice number, dates, IBAN/BIC, Leitweg-ID and the invoice lines (only if quantity x price and the line sum match the PDF's net total; otherwise one line with the net total). Regex-based, no guessing: fields we can't read reliably are missing and listed in `missing`. Check and complete them, then call create_einvoice to get XRechnung, ZUGFeRD or Peppol. Scanned PDFs (no text layer) are not supported. Pass the PDF base64-encoded in `file_base64`. Max 5 MB.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
validate_einvoiceValidate an e-invoice (XRechnung UBL/CII, ZUGFeRD / Factur-X PDF, Peppol BIS Billing 3.0, EN 16931) with the official KoSIT validator.No findings
Why it is in this group
- The name "validate_einvoice" says "validate": a word for reading.
Description, as the server wrote it Validate an e-invoice (XRechnung UBL/CII, ZUGFeRD / Factur-X PDF, Peppol BIS Billing 3.0, EN 16931) with the official KoSIT validator. Returns valid/invalid, the detected format, every error and warning with its rule code, and the exact corrected value for common calculation errors. Pass the XML as text in `xml`, or a PDF/XML file base64-encoded in `file_base64`. Max 5 MB.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
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.
1 path in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__einvoicing__create_einvoice"
]
}
}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:13 UTC, unchanged since Nov 6, 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
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- 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 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://invoiceer.io/mcp: tools/list returned 6 tools to an anonymous client, including check_leitweg_id (write), create_einvoice (write), explain_rule (write)
Posture changes
- Nov 6, 2026
- HTTP status of an anonymous initialize: 521 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 3
- Protocol version: none to 2025-06-18
- Oct 29, 2026
- HTTP status of an anonymous initialize: 200 to 521
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 3 to 0
- Protocol version: 2025-06-18 to none
Findings
Matches of fixed checks, with the text they matched.
- Warncreate_einvoice
The server marks "create_einvoice" 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_einvoice" says "create": a word for a change.
- Warnexplain_rule
The server marks "explain_rule" 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 "explain_rule" says "explain": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:create_einvoiceChanges thingsinputSchema
PostureRemote posture changed. HTTP status of an anonymous initialize: 521 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 3 (and 1 more).View diff
- HTTP status of an anonymous initialize: 521 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 3
- Protocol version: none to 2025-06-18
Tools1 added, 3 changed.+1 added~3 changedView diff
- Added:read_invoice_pdfOnly reads
- Changed:check_leitweg_idChanges thingsdescription
- Changed:create_einvoiceChanges thingsinputSchema
- Changed:validate_einvoiceOnly readsinputSchema
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 521; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 3 -> 0 (and 1 more).View diff
- HTTP status of an anonymous initialize: 200 to 521
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 3 to 0
- Protocol version: 2025-06-18 to none
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http einvoicing https://invoiceer.io/mcpclaude mcp add --transport http einvoicing https://invoiceer.io/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__einvoicing__validate_einvoice",
"mcp__einvoicing__peppol_lookup",
"mcp__einvoicing__read_invoice_pdf"
],
"ask": [
"mcp__einvoicing__check_leitweg_id",
"mcp__einvoicing__create_einvoice",
"mcp__einvoicing__explain_rule"
],
"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 einvoicing. Review it before you use it.
Capability tags behind 3 rules
- mcp__einvoicing__peppol_lookup untrusted-input
- mcp__einvoicing__create_einvoice outbound
- mcp__einvoicing__read_invoice_pdf private-data
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/io.invoiceer/einvoicing/verify?hash=1fbf89aaa316da1e3e74123c39e66b4c73420a781d6111e40ae26bab3d1ae1c5" | jq -e '.changed == false'Pinned hash 1fbf89aaa316, from Nov 18, 2026, 12:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.invoiceer/einvoicing/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.invoiceer/einvoicing)Source: MCP Registry. Synced Oct 21, 2026, 19:23 UTC.
Invoiceer e-invoicing tools MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Invoiceer e-invoicing tools MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 3 of which can change, send or delete something, and 2 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 Invoiceer e-invoicing tools MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Invoiceer e-invoicing tools 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 Invoiceer e-invoicing tools MCP server have?
- 6 tools: 3 write, 3 read. check_leitweg_id, create_einvoice, explain_rule, validate_einvoice, peppol_lookup and read_invoice_pdf.
Does the Invoiceer e-invoicing tools MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Invoiceer e-invoicing tools MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_einvoice.
Has the Invoiceer e-invoicing tools MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.