Jithox E-Invoice Readiness
REMOTE · MCP.JITHOX.COM
Read-only EU e-invoice checks: VAT format, VIES, Peppol lookup. Returns evidence, no filing.
Available components
Last scanned (5 hours ago)
Scores higher than 42% of remote servers
Unreachable for 4 days in a row. Last reached 1 Nov 2026.
Category Finance and Payments
Degraded
One or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 5 Nov 26 −17
The score moved with no change recorded against any check. We would rather say so than guess.
- 4 Nov 26 −18
The score moved with no change recorded against any check. We would rather say so than guess.
- 2 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 30 Sept 26 0
- Server version: 1.2.0 → 1.2.1 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
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 5 Nov 2026 · Probed https://mcp.jithox.com/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.jithox.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| jithox.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.jithox.com/mcp | Unreachable | ||
| http (plaintext) | http://mcp.jithox.com/mcp | HTTPS enforced |
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 →
get_einvoice_readiness Assess e-invoice readiness ~89
Readiness 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.
| Name | Type | Req | Description |
|---|---|---|---|
| verifyWithProvider | boolean | – | Also confirm the bound legal entity with the provider (one provider call). |
| Name | Type | Req | Description |
|---|---|---|---|
| billing | object | yes | – |
| capability | – | yes | – |
| data | object | yes | – |
| decision | string | yes | – |
| decisionCategory | string | yes | – |
| generatedAt | string | yes | – |
| limitations | array | yes | – |
| product | – | yes | – |
| provenance | object | yes | – |
| receipt | – | yes | – |
| receiptEnvelope | object | – | – |
| retryable | boolean | yes | – |
| schemaVersion | – | yes | – |
No examples provided.
lookup_peppol_participant Look up a Peppol participant ~215
Check 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 hidden "no". Provide vatId or endpointId (at least one) plus the receiver country. Lookup only — never a send action, and no send tool exists here. Validation and readiness only; never sends a Peppol invoice and gives no legal, fiscal or compliance guarantee.
| Name | Type | Req | Description |
|---|---|---|---|
| countryCode | string | yes | Receiver country (drives the scheme derivation). |
| endpointId | string | – | Peppol endpoint identifier (GLN or scheme-specific id). |
| endpointScheme | string | – | EAS scheme id. Derived when omitted (BE VAT → 0208, else 0088). |
| vatId | string | – | VAT / enterprise number, e.g. "BE0123456749". |
| Name | Type | Req | Description |
|---|---|---|---|
| billing | object | yes | – |
| capability | – | yes | – |
| data | object | yes | – |
| decision | string | yes | – |
| decisionCategory | string | yes | – |
| generatedAt | string | yes | – |
| limitations | array | yes | – |
| product | – | yes | – |
| provenance | object | yes | – |
| receipt | – | yes | – |
| receiptEnvelope | object | – | – |
| retryable | boolean | yes | – |
| schemaVersion | – | yes | – |
No examples provided.
validate_invoice Validate an EU invoice (structure) ~87
Structurally 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, fiscal or compliance guarantee.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice | object | yes | The invoice payload to check. |
| Name | Type | Req | Description |
|---|---|---|---|
| billing | object | yes | – |
| capability | – | yes | – |
| data | object | yes | – |
| decision | string | yes | – |
| decisionCategory | string | yes | – |
| generatedAt | string | yes | – |
| limitations | array | yes | – |
| product | – | yes | – |
| provenance | object | yes | – |
| receipt | – | yes | – |
| receiptEnvelope | object | – | – |
| retryable | boolean | yes | – |
| schemaVersion | – | yes | – |
No examples provided.
validate_vat_number Validate a VAT number (format) ~118
Deterministic 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 or compliance guarantee.
| Name | Type | Req | Description |
|---|---|---|---|
| countryCode | string | – | ISO alpha-2, used only when the VAT has no prefix. |
| vatNumber | string | yes | A VAT number, e.g. "BE0123456749". |
| Name | Type | Req | Description |
|---|---|---|---|
| billing | object | yes | – |
| capability | – | yes | – |
| data | object | yes | – |
| decision | string | yes | – |
| decisionCategory | string | yes | – |
| generatedAt | string | yes | – |
| limitations | array | yes | – |
| product | – | yes | – |
| provenance | object | yes | – |
| receipt | – | yes | – |
| receiptEnvelope | object | – | – |
| retryable | boolean | yes | – |
| schemaVersion | – | yes | – |
No examples provided.
verify_vat_vies Verify a VAT number in VIES (live) ~123
Check 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 and gives no legal, fiscal or compliance guarantee.
| Name | Type | Req | Description |
|---|---|---|---|
| countryCode | string | – | ISO alpha-2, used only when the VAT has no prefix. |
| vatNumber | string | yes | A VAT number, e.g. "BE0123456749". |
| Name | Type | Req | Description |
|---|---|---|---|
| billing | object | yes | – |
| capability | – | yes | – |
| data | object | yes | – |
| decision | string | yes | – |
| decisionCategory | string | yes | – |
| generatedAt | string | yes | – |
| limitations | array | yes | – |
| product | – | yes | – |
| provenance | object | yes | – |
| receipt | – | yes | – |
| receiptEnvelope | object | – | – |
| retryable | boolean | yes | – |
| schemaVersion | – | yes | – |
No examples provided.
How do I install the Jithox E-Invoice Readiness MCP server?
Jithox E-Invoice Readiness is a hosted endpoint at https://mcp.jithox.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 · mcp.jithox.com
claude mcp add --transport http com-jithox-einvoice-readiness 'https://mcp.jithox.com/mcp'
What is the Jithox E-Invoice Readiness MCP server?
Jithox E-Invoice Readiness is an MCP server listed in the public MCP registry as com.jithox/einvoice-readiness. Read-only EU e-invoice checks: VAT format, VIES, Peppol lookup. Returns evidence, no filing. This page covers its hosted endpoint (https://mcp.jithox.com/mcp).
Is the Jithox E-Invoice Readiness MCP server safe to use?
Jithox E-Invoice Readiness scores 53 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 Jithox E-Invoice Readiness MCP server expose?
Jithox E-Invoice Readiness exposes 5 tools: validate_invoice, validate_vat_number, verify_vat_vies, lookup_peppol_participant, get_einvoice_readiness. Their descriptions and schemas cost roughly 632 tokens of context every time the server is loaded.
Does the Jithox E-Invoice Readiness MCP server require authentication?
Its publisher declares no required credentials for Jithox E-Invoice Readiness. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Jithox E-Invoice Readiness MCP server still maintained?
Jithox E-Invoice Readiness is still listed in the MCP registry, but we have not been able to reach this channel for several days and its score is decaying. We last reached this channel on 1 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.