Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.einvoicewiz/einvoicewiz

REMOTE · EINVOICEWIZ.COM · SCANNED SEP 20

Generate & validate EN 16931 e-invoices (Factur-X, ZUGFeRD, XRechnung); verification certificates

Available components

+3 this week 75 Trust /100
Trust breakdown (7 categories)

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 Security66
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 710 tokens (~101/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
  • Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 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
Install

How do I install the com.einvoicewiz/einvoicewiz MCP server?

com.einvoicewiz/einvoicewiz is a hosted endpoint at https://einvoicewiz.com/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 · einvoicewiz.com

# add to Claude Code
claude mcp add --transport http com-einvoicewiz-einvoicewiz 'https://einvoicewiz.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-einvoicewiz-einvoicewiz": {
      "url": "https://einvoicewiz.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-einvoicewiz-einvoicewiz": {
      "type": "http",
      "url": "https://einvoicewiz.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-einvoicewiz-einvoicewiz]
url = "https://einvoicewiz.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-einvoicewiz-einvoicewiz": {
      "type": "remote",
      "url": "https://einvoicewiz.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-einvoicewiz-einvoicewiz --url 'https://einvoicewiz.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-einvoicewiz-einvoicewiz:
    url: "https://einvoicewiz.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-einvoicewiz-einvoicewiz": {
      "Transport": "http",
      "Url": "https://einvoicewiz.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-einvoicewiz-einvoicewiz -t streamable-http -u 'https://einvoicewiz.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-einvoicewiz-einvoicewiz": {
      "type": "http",
      "url": "https://einvoicewiz.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 20 Sept 2026 · Probed https://einvoicewiz.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=einvoicewiz.com CN=YE2,O=Let's Encrypt,C=US 8 Sept 2026 7 Dec 2026 ECDSA 256 ECDSA-SHA384 67a8bcf040762479f5101faf1dad0d55fea
SANs: einvoicewiz.com, www.einvoicewiz.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
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

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of einvoicewiz.com. Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
einvoicewiz.com. present 49249 13 Verified
einvoicewiz.com. Verified address RRset verified with the apex keys
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
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://einvoicewiz.com/mcp Verified 200
http (plaintext) http://einvoicewiz.com/mcp HTTPS enforced 301 https://einvoicewiz.com/mcp
MCP tools · 7 exposed · ~555 tokens

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 →

Tool Tokens
check_credits ~27

Credits remaining and calls used for an API key.

NameTypeReqDescription
api_keystring

No output schema declared.

No examples provided.

create_facturx_pdf ~120

Your existing PDF invoice + invoice JSON → Factur-X / ZUGFeRD PDF/A-3 with embedded XML (1 credit). pdf_base64: the original PDF, base64-encoded (max 15 MB). Returns {pdf_base64, cert_id, verify_url, credits_left}. The output is validated (EN 16931 + PDF/A-3) before delivery; failures are not charged.

NameTypeReqDescription
api_keystring
invoiceobjectyes
pdf_base64stringyes

No output schema declared.

No examples provided.

generate_einvoice_xml ~175

Invoice JSON → validated EN 16931 CII XML (1 credit; failures free). profile: "en16931" (Factur-X/ZUGFeRD data, B2B) or "xrechnung" (German public sector; needs invoice.buyer_reference = Leitweg-ID and seller contact_email/contact_phone). Invoice schema: see https://einvoicewiz.com/openapi.json (required: invoice_number, issue_date, currency, seller{name,country}, buyer{name,country}, lines[{name,qty,unit_price,vat_rate}]). Returns {xml, validation, verify:{id,url}, credits_left}. On 422 the body lists the violated rules.

NameTypeReqDescription
api_keystring
invoiceobjectyes
profilestring

No output schema declared.

No examples provided.

lookup_certificate ~42

Look up a verification certificate (EIW-…) — free, no key. Confirms which file hashes passed validation and when.

NameTypeReqDescription
cert_idstringyes

No output schema declared.

No examples provided.

signup ~39

Create an einvoicewiz API key with 20 free credits (no card). The key is shown once — store it.

NameTypeReqDescription
emailstringyes

No output schema declared.

No examples provided.

validate_einvoice ~97

Validate a Factur-X / ZUGFeRD / XRechnung file (PDF or XML, base64) against EN 16931 + KOSIT + PDF/A (1 credit). Returns the rule-level report {result:{status, errors[], warnings[], profile}, verify, credits_left}. verify is set only when the file passed.

NameTypeReqDescription
api_keystring
file_base64stringyes

No output schema declared.

No examples provided.

which_format_do_i_need ~55

Decision helper (free, no key): which e-invoice format a recipient needs and whether a plain PDF is still acceptable.

NameTypeReqDescription
recipient_countrystringyes
recipient_is_public_authorityboolean

No output schema declared.

No examples provided.

Common questions

What is the com.einvoicewiz/einvoicewiz MCP server?

com.einvoicewiz/einvoicewiz is an MCP server listed in the public MCP registry as com.einvoicewiz/einvoicewiz. Generate & validate EN 16931 e-invoices (Factur-X, ZUGFeRD, XRechnung); verification certificates. This page covers its hosted endpoint (https://einvoicewiz.com/mcp).

Is the com.einvoicewiz/einvoicewiz MCP server safe to use?

com.einvoicewiz/einvoicewiz scores 75 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 com.einvoicewiz/einvoicewiz MCP server expose?

com.einvoicewiz/einvoicewiz exposes 7 tools: signup, check_credits, generate_einvoice_xml, create_facturx_pdf, validate_einvoice, and 2 more. Their descriptions and schemas cost roughly 555 tokens of context every time the server is loaded.

Does the com.einvoicewiz/einvoicewiz MCP server require authentication?

No. We connected to com.einvoicewiz/einvoicewiz without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.einvoicewiz/einvoicewiz MCP server still maintained?

com.einvoicewiz/einvoicewiz is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.