E-invoice validator & repair check (XRechnung, Peppol BIS 3, EN 16931)
Validate XRechnung, Peppol BIS 3 and EN 16931 invoices with KoSIT; explain rules; check auto-repair
Should I use this
Quality & Safety
Findings (1)
- LOWTool 'explain_rule' description lacks action verbin explain_rule
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"einvoice-validator": {
"url": "https://einvoice-validator-k2qw.onrender.com/mcp"
}
}
}Remote endpoints
https://einvoice-validator-k2qw.onrender.com/mcpstreamable-httpWhat it can do
Tool inventory
Tools (2)
🟢validate_einvoice(xml)
Validate an XRechnung / Peppol BIS 3 / EN 16931 e-invoice (UBL 2.1 Invoice/CreditNote or CII CrossIndustryInvoice XML) with the official KoSIT validator. Returns accepted/rejected, the matched scenario and every error and warning with rule id, message, location and a link to a plain-language explanation. For rejected files it also reports which errors an automatic repair removes (measured on this file).
Input Schema
{
"type": "object",
"properties": {
"xml": {
"type": "string",
"description": "The complete invoice XML as text (max 5 MB)."
}
},
"required": [
"xml"
]
}🟢explain_rule(rule)
Explain an EN 16931 / XRechnung / Peppol business rule by id (e.g. BR-CO-10, BR-DE-15, PEPPOL-EN16931-R001): what it means and how to fix it.
Input Schema
{
"type": "object",
"properties": {
"rule": {
"type": "string",
"description": "Rule id, e.g. BR-CO-10"
}
},
"required": [
"rule"
]
}Community
Evidence