mcp-registry/com.einvoicechecker/einvoice · v1.0.0
Also listed as github/vpukhalskyi/einvoicechecker-mcp
As of 2026-10-22 17:29 UTC, the Einvoicechecker Einvoice MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 8 minutes.
Validate, parse and render EU e-invoices: XRechnung, ZUGFeRD, Factur-X, Peppol BIS 3.0, KSeF.
Claude Code
claude mcp add --transport http einvoicechecker-einvoice-mcp-server https://einvoicechecker.com/v1/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"einvoicechecker-einvoice-mcp-server": {
"type": "http",
"url": "https://einvoicechecker.com/v1/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
8 of 8 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
1 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 4 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.einvoicechecker%2Feinvoice/fixes
{
"name": "list_supported_formats",
"description": "Which formats, profiles and rule sets this service supports, and what each tool costs.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
},
"annotations": {
"readOnlyHint": true
},
"title": "Supported e-invoice formats"
}{
"name": "validate_invoice",
"description": "Run the official rule set for the detected format (KoSIT for XRechnung/ZUGFeRD/Factur-X, OpenPeppol for Peppol BIS, FA(3) schema for KSeF, Porezna uprava HR-CIUS schematron for Croatian eRačun, Facturae XSD + calculation/NIF/DIR3 rules for Spain, LHDN SDK rules for MyInvois). Returns valid/invalid with every failed rule: id, severity, message, XPath.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"kosit": {
"type": "boolean",
"description": "Run the full KoSIT schematron (default true). false = schema and core checks only, faster"
},
"content": {
"type": "string",
"description": "Invoice XML (UBL, CII, XRechnung, Peppol BIS, ZUGFeRD/Factur-X XML, KSeF FA(3)) as text"
},
"content_base64": {
"type": "string",
"description": "A ZUGFeRD / Factur-X PDF (or any invoice file) as base64, when the invoice is not plain XML"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
},
"title": "Validate e-invoice"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.einvoicechecker/einvoice"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.einvoicechecker/einvoice"}) over MCP.
fix_invoice ~600 tokensvalidate_invoice ~259 tokensrender_invoice_html ~183 tokensrender_invoice_pdf ~169 tokensparse_invoice ~165 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.einvoicechecker%2Feinvoice?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.einvoicechecker%2Feinvoice?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.einvoicechecker%2Feinvoice.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.einvoicechecker%2Feinvoice.svg :target: https://glimind.com/server/mcp-registry%2Fcom.einvoicechecker%2Feinvoice?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:fed60869dc19c551…, first seen 2026-10-17, included at leaf 2844 of 47,228. Version history · verify what your client received.
Compare: most reliable data servers · most reliable knowledge servers · most reliable other servers · most reliable media servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-22 17:29 UTC, the Einvoicechecker Einvoice MCP server is up with a Glimind reliability score of 94/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 8 minutes.
Einvoicechecker Einvoice MCP server advertises 8 tools, including detect_invoice, fix_invoice, list_supported_formats, my_usage, parse_invoice.
Point your MCP client at this streamable-http endpoint: https://einvoicechecker.com/v1/mcp
Glimind scanned all 8 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.