Jithox E-Invoice Readiness
com.jithox/einvoice-readiness · v1.2.1
Read-only EU e-invoice checks: VAT format, VIES, Peppol lookup. Returns evidence, no filing.
MCPremoteno credentialsFinanceLaw & government
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 5 tools, protocol 2025-06-18 · checked 2026-10-17
Test & rating
B 88/100
What it does: 5 tools · 5 read, 0 write · Finance, Law & government, Developer tools
Test call get_einvoice_readiness: needs a key: rpc error: unauthorized: this tool needs a credential and none was sent. Nothing ran and nothing was charged. A person creates a server key on http (971 ms)
How the rating is made
- Answers without login: +30
- Speed of first answer: +10
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +10
- Read/write annotations: +5
- Safe test call: +8
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://mcp.jithox.com/mcpTools
5 tools listed at last check
validate_invoiceStructurally validate a draft EU invoice and report machine-readable issues (schema problems, VAT-id format, date sanity, BIS 3.0 completeness, computed totals). Full report, never fails fast. Not legal approval. Validation and readiness only; never sends a Peppol invoice and gives no legal, fiscalvalidate_vat_numberDeterministic structure/checksum validation of an EU VAT number (incl. the Belgian modulo-97 checksum) with the normalized identifier and a stable issue code. Format plausibility only — not a live VIES result. Validation and readiness only; never sends a Peppol invoice and gives no legal, fiscal orverify_vat_viesCheck a VAT number's ACTIVE status against the official EU VIES source. Returns valid / invalid / invalid_input / unavailable with provenance (source, checkedAt). When VIES is unavailable it says so truthfully and makes no validity claim. Validation and readiness only; never sends a Peppol invoice alookup_peppol_participantCheck whether a receiver is registered on the Peppol network and accepts BIS Billing 3.0 invoices, via the official SML/SMP discovery route when enabled (otherwise an honest mock that says so). Only status registered/not_registered is definitive; unavailable/not_configured are truthful and never a hget_einvoice_readinessReadiness snapshot for YOUR canary workspace: one plain state, what is ready, what is missing, and the next safe step. Diagnostics, not a compliance certificate. Validation and readiness only; never sends a Peppol invoice and gives no legal, fiscal or compliance guarantee.
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/com.jithox/einvoice-readiness)