Jithox E-Invoice Readiness
REMOTE · MCP.JITHOX.COM · SCANNED SEP 20
Read-only e-invoice readiness over MCP: VAT format, VIES, Peppol lookup, invoice & readiness
Available components
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 666 tokens (~133/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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'
{
"mcpServers": {
"com-jithox-einvoice-readiness": {
"url": "https://mcp.jithox.com/mcp"
}
}
} {
"servers": {
"com-jithox-einvoice-readiness": {
"type": "http",
"url": "https://mcp.jithox.com/mcp"
}
}
} [mcp_servers.com-jithox-einvoice-readiness] url = "https://mcp.jithox.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-jithox-einvoice-readiness": {
"type": "remote",
"url": "https://mcp.jithox.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-jithox-einvoice-readiness --url 'https://mcp.jithox.com/mcp' --transport streamable-http
mcp_servers:
com-jithox-einvoice-readiness:
url: "https://mcp.jithox.com/mcp" {
"McpServers": {
"com-jithox-einvoice-readiness": {
"Transport": "http",
"Url": "https://mcp.jithox.com/mcp"
}
}
} assistant mcp add com-jithox-einvoice-readiness -t streamable-http -u 'https://mcp.jithox.com/mcp'
{
"mcpServers": {
"com-jithox-einvoice-readiness": {
"type": "http",
"url": "https://mcp.jithox.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 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 +1
- Stability: 0.97 → pass security
- 23 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 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
- 7 Aug 26 0
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- Server version: 1.1.0 → 1.2.0 functional
- 2 Aug 26 0
- Server version: 1.0.0-canary → 1.1.0 functional
- 31 Jul 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
- 27 Jul 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
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://mcp.jithox.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.jithox.com | CN=YE2,O=Let's Encrypt,C=US | 11 Sept 2026 | 10 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 699676338a499cd1f380491541a5ce50839 |
| SANs: mcp.jithox.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 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 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; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
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 | Verified | 200 | |
| http (plaintext) | http://mcp.jithox.com/mcp | HTTPS enforced | 308 | https://mcp.jithox.com/mcp |
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.
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 e-invoice readiness over MCP: VAT format, VIES, Peppol lookup, invoice & readiness. 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 88 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?
No. We connected to Jithox E-Invoice Readiness without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Jithox E-Invoice Readiness MCP server still maintained?
Jithox E-Invoice Readiness 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.