invowerk
REMOTE · API.INVOWERK.DEV · SCANNED OCT 14
E-invoice checker for ZUGFeRD, Factur-X, XRechnung and Peppol BIS. Free web tool, API and MCP.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1809 tokens (~301/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the invowerk MCP server?
invowerk is a hosted endpoint at https://api.invowerk.dev/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.invowerk.dev
claude mcp add --transport http dev-invowerk-xrechnung-e-invoice-validator 'https://api.invowerk.dev/mcp/'
{
"mcpServers": {
"dev-invowerk-xrechnung-e-invoice-validator": {
"url": "https://api.invowerk.dev/mcp/"
}
}
} {
"servers": {
"dev-invowerk-xrechnung-e-invoice-validator": {
"type": "http",
"url": "https://api.invowerk.dev/mcp/"
}
}
} [mcp_servers.dev-invowerk-xrechnung-e-invoice-validator] url = "https://api.invowerk.dev/mcp/"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-invowerk-xrechnung-e-invoice-validator": {
"type": "remote",
"url": "https://api.invowerk.dev/mcp/",
"enabled": true
}
}
} openclaw mcp add dev-invowerk-xrechnung-e-invoice-validator --url 'https://api.invowerk.dev/mcp/' --transport streamable-http
mcp_servers:
dev-invowerk-xrechnung-e-invoice-validator:
url: "https://api.invowerk.dev/mcp/" {
"McpServers": {
"dev-invowerk-xrechnung-e-invoice-validator": {
"Transport": "http",
"Url": "https://api.invowerk.dev/mcp/"
}
}
} assistant mcp add dev-invowerk-xrechnung-e-invoice-validator -t streamable-http -u 'https://api.invowerk.dev/mcp/'
{
"mcpServers": {
"dev-invowerk-xrechnung-e-invoice-validator": {
"type": "http",
"url": "https://api.invowerk.dev/mcp/"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 30. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 20. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 1 Oct 26 72
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 14 Oct 2026 · Probed https://api.invowerk.dev/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.invowerk.dev | CN=YE1,O=Let's Encrypt,C=US | 15 Sept 2026 | 14 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5ec5ed82f42bf7b678fd4186e28f02778fc |
| SANs: api.invowerk.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
| CN=ISRG Root X1,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 4 Jun 2015 | 4 Jun 2035 | RSA 4096 | SHA256-RSA | 8210cfb0d240e3594463e0bb63828b00 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.invowerk.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| invowerk.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; connect-src 'self' https://api.invowerk.dev; worker-src 'self' blob:; font-src 'self' data:; frame-ancestors 'none'; form-action 'self' https://polar.sh https://*.polar.sh https://sandbox.polar.sh; base-uri 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), microphone=(), camera=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.invowerk.dev/mcp/ | Verified | 200 | |
| http (plaintext) | http://api.invowerk.dev/mcp/ | HTTPS enforced | 301 | https://api.invowerk.dev/mcp/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
convert_invoice Convert an e-invoice between UBL and CII ~293
Convert an e-invoice to UBL or CII. The result is checked before it is returned. Input: `invoice_base64` is the base64 of an XML invoice or a ZUGFeRD / Factur-X PDF, at most 4 MB decoded; or pass the file as a download link in `file`. `target_syntax` is "ubl" or "cii". `target_flavor` is optional, "en16931" or "xrechnung"; without it the flavor of the source is kept. Returns `xml`, `syntax`, `flavor` and `self_validation` (`valid`, `finding_count`). invowerk checks the converted XML before answering and never returns an invalid document. Input that cannot be read or converted fails with an error message. Credits: 3 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| file | object | – | The file as a download link, instead of `invoice_base64`. In ChatGPT, pass the user's uploaded file here. Other clients can set `download_url` to a public https URL. |
| invoice_base64 | – | – | The invoice file, base64-encoded. At most 4 MB decoded. |
| target_flavor | – | – | Optional: "en16931" or "xrechnung". Without it the flavor of the source is kept. |
| target_syntax | string | yes | Syntax to convert to: "ubl" or "cii". |
Structured output declared, but exposes no named fields.
No examples provided.
explain_errors Explain error codes ~245
Explain rule codes in plain language. Works without an API key. Covers the codes of `validate_invoice` findings and hints: EN 16931, XRechnung, ZUGFeRD and invowerk's own hint codes (IW-*). Input: `codes` is a list of one or more codes, e.g. ["BR-CO-18", "BR-DE-21"]. Duplicates are removed. `lang` is "de" (default) or "en". Returns `lang` and `explanations`. Each explanation has `title`, `meaning`, `causes`, `fixes`, `severity`, `standard`, `bt_refs`, `xpath_hints` and `explain_url` (the German page for the code). If any code is unknown, the call fails and names the unknown codes. Credits: free. This tool is not metered.
| Name | Type | Req | Description |
|---|---|---|---|
| codes | array | yes | One or more rule codes from validate_invoice, e.g. ["BR-CO-18", "BR-DE-21"]. |
| lang | string | – | Language of the explanations: "de" (default) or "en". |
Structured output declared, but exposes no named fields.
No examples provided.
generate_invoice Create an e-invoice from JSON ~297
Create a valid EN 16931 e-invoice (UBL or CII XML) from JSON. Input: `invoice` is a JSON object keyed on EN 16931 Business Terms, the same schema as `POST /v1/generate`, at most 4 MB. Main fields: `syntax` ("ubl" default, or "cii"), `flavor` ("en16931" default, or "xrechnung", which requires `buyer_reference`, the Leitweg-ID BT-10), `invoice_number`, `issue_date` (YYYY-MM-DD), `currency`, `seller`, `buyer`, `lines`, `tax_breakdown`, `totals`. invowerk writes your amounts as given. It does not compute or correct them. Returns `xml`, `syntax`, `flavor` and `self_validation`. invowerk checks the XML before answering and never returns an invalid document. Invalid input, or XML that fails the check, returns an error, as does a busy (`engine_busy`) or overrunning (`engine_timeout`) generate. Credits: 5 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice | object | yes | The invoice as a JSON object keyed on EN 16931 Business Terms, the schema of POST /v1/generate and of parse_invoice's `model`: syntax, flavor, invoice_number, issue_date, currency, seller, buyer, lin… |
Structured output declared, but exposes no named fields.
No examples provided.
parse_invoice Read an e-invoice into JSON ~283
Read an existing e-invoice into JSON keyed on EN 16931 Business Terms. The JSON is the input format of `generate_invoice`, so you can edit it and create the invoice again. Input: `invoice_base64` is the base64 of an XML invoice (UBL or CII) or a ZUGFeRD / Factur-X PDF, at most 4 MB decoded; or pass the file as a download link in `file`. A PDF may have at most 500 pages and 16 attachments. Returns `model` (the invoice as JSON), `detection` (`syntax`, `flavor`, `customization_id`) and `source` ("xml" or "pdf-embedded"). A file that cannot be read fails with an error that starts with an error code, e.g. a PDF without embedded XML, a UBL credit note, malformed XML, or a busy (`engine_busy`) or overrunning (`engine_timeout`) read. Credits: 2 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| file | object | – | The file as a download link, instead of `invoice_base64`. In ChatGPT, pass the user's uploaded file here. Other clients can set `download_url` to a public https URL. |
| invoice_base64 | – | – | The invoice file, base64-encoded. At most 4 MB decoded. |
Structured output declared, but exposes no named fields.
No examples provided.
render_invoice Render an e-invoice as HTML ~292
Render an XML e-invoice (UBL or CII, e.g. XRechnung) as a readable HTML page. invowerk uses the KoSIT XRechnung visualization. Use it to show a person what an e-invoice contains. Input: `invoice_base64` is the base64 of the XML, at most 4 MB decoded, or pass the file as a download link in `file`. PDFs are not accepted. `lang` sets the label language, "de" (default) or "en". Returns `html` (a complete HTML document), `lang`, `flavor` (e.g. "xrechnung") and `syntax` (e.g. "ubl_invoice"). A file that is not an XML invoice, malformed XML or XML with a DOCTYPE fails with an error message, and so does a busy (`engine_busy`) or overrunning (`engine_timeout`) render. Credits: 1 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| file | object | – | The file as a download link, instead of `invoice_base64`. In ChatGPT, pass the user's uploaded file here. Other clients can set `download_url` to a public https URL. |
| invoice_base64 | – | – | The invoice file, base64-encoded. At most 4 MB decoded. |
| lang | string | – | Language of the labels: "de" (default) or "en". |
Structured output declared, but exposes no named fields.
No examples provided.
validate_invoice Check an e-invoice ~399
Check an e-invoice against EN 16931 and German rules. Input: `invoice_base64` is the base64 of an XML invoice (UBL or CII) or a ZUGFeRD / Factur-X PDF, at most 4 MB decoded; or pass the file as a download link in `file`. `explain=true` adds an explanation to findings whose rule has one, in `lang` ("de" or "en"). `valid` is the result. For XRechnung the KoSIT validator decides. If it is unreachable, invowerk's own check with the same rules decides, `verdict_source` is "local" and `official_degraded` is true. `disagreement` is true when both ran and differ. `findings` lists each problem with `rule_id`, `severity` and `message`; pass the codes to `explain_errors` (free). `pdfa_verdict` is the PDF/A check of a PDF. `hints` never change `valid`. Unreadable input returns a finding, not an error. It fails with an error when the check is busy (`engine_busy`), ran longer than 20 s (`engine_timeout`) or the XML has more than 100,000 elements (`document_too_complex`). Credits: 1 per call.
| Name | Type | Req | Description |
|---|---|---|---|
| explain | boolean | – | true adds an explanation to each finding whose rule has one. |
| file | object | – | The file as a download link, instead of `invoice_base64`. In ChatGPT, pass the user's uploaded file here. Other clients can set `download_url` to a public https URL. |
| invoice_base64 | – | – | The invoice file, base64-encoded. At most 4 MB decoded. |
| lang | string | – | Language of the explanations: "de" (default) or "en". |
Structured output declared, but exposes no named fields.
No examples provided.
What is the invowerk MCP server?
invowerk is an MCP server listed in the public MCP registry as dev.invowerk/xrechnung-e-invoice-validator. E-invoice checker for ZUGFeRD, Factur-X, XRechnung and Peppol BIS. Free web tool, API and MCP. This page covers its hosted endpoint (https://api.invowerk.dev/mcp/).
Is the invowerk MCP server safe to use?
invowerk scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the invowerk MCP server expose?
invowerk exposes 6 tools: validate_invoice, render_invoice, explain_errors, generate_invoice, parse_invoice, convert_invoice. Their descriptions and schemas cost roughly 1,809 tokens of context every time the server is loaded.
Does the invowerk MCP server require authentication?
No. We connected to invowerk without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the invowerk MCP server still maintained?
invowerk is still listed as active in the MCP registry. We last reached this channel on 14 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.