# Jithox E-Invoice Readiness (remote · mcp.jithox.com)

Read-only e-invoice readiness over MCP: VAT format, VIES, Peppol lookup, invoice & readiness

- Trust score: 76/100 (medium)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.jithox.com`: 76/100 (this document), [markdown](https://verifymcp.io/servers/com-jithox-einvoice-readiness/mcp.md), [page](https://verifymcp.io/servers/com-jithox-einvoice-readiness/mcp)

## Channel facts

- Endpoint: `https://mcp.jithox.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-jithox-einvoice-readiness https://mcp.jithox.com/mcp
```

### Codex

```toml
[mcp_servers.com-jithox-einvoice-readiness]
url = "https://mcp.jithox.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-jithox-einvoice-readiness": {
      "type": "remote",
      "url": "https://mcp.jithox.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-jithox-einvoice-readiness --url https://mcp.jithox.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-jithox-einvoice-readiness:
    url: "https://mcp.jithox.com/mcp"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-02 (score 75, 0)

- [functional] Server version: 1.0.0-canary → 1.1.0

### 2026-08-01 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 74, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 69, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 69)

First indexed and scored.

## MCP tools (5)

### `validate_invoice` (~87 tokens)

Validate an EU invoice (structure)

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.

Input parameters:

- `invoice` (object, required): The invoice payload to check.

Output parameters:

- `billing` (object)
- `capability`
- `data` (object)
- `decision` (string)
- `decisionCategory` (string)
- `generatedAt` (string)
- `limitations` (array)
- `product`
- `provenance` (object)
- `receipt`
- `receiptEnvelope` (object)
- `retryable` (boolean)
- `schemaVersion`

### `validate_vat_number` (~118 tokens)

Validate a VAT number (format)

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.

Input parameters:

- `countryCode` (string): ISO alpha-2, used only when the VAT has no prefix.
- `vatNumber` (string, required): A VAT number, e.g. "BE0123456749".

Output parameters:

- `billing` (object)
- `capability`
- `data` (object)
- `decision` (string)
- `decisionCategory` (string)
- `generatedAt` (string)
- `limitations` (array)
- `product`
- `provenance` (object)
- `receipt`
- `receiptEnvelope` (object)
- `retryable` (boolean)
- `schemaVersion`

### `verify_vat_vies` (~123 tokens)

Verify a VAT number in VIES (live)

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.

Input parameters:

- `countryCode` (string): ISO alpha-2, used only when the VAT has no prefix.
- `vatNumber` (string, required): A VAT number, e.g. "BE0123456749".

Output parameters:

- `billing` (object)
- `capability`
- `data` (object)
- `decision` (string)
- `decisionCategory` (string)
- `generatedAt` (string)
- `limitations` (array)
- `product`
- `provenance` (object)
- `receipt`
- `receiptEnvelope` (object)
- `retryable` (boolean)
- `schemaVersion`

### `lookup_peppol_participant` (~215 tokens)

Look up a Peppol participant

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.

Input parameters:

- `countryCode` (string, required): 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".

Output parameters:

- `billing` (object)
- `capability`
- `data` (object)
- `decision` (string)
- `decisionCategory` (string)
- `generatedAt` (string)
- `limitations` (array)
- `product`
- `provenance` (object)
- `receipt`
- `receiptEnvelope` (object)
- `retryable` (boolean)
- `schemaVersion`

### `get_einvoice_readiness` (~89 tokens)

Assess e-invoice readiness

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.

Input parameters:

- `verifyWithProvider` (boolean): Also confirm the bound legal entity with the provider (one provider call).

Output parameters:

- `billing` (object)
- `capability`
- `data` (object)
- `decision` (string)
- `decisionCategory` (string)
- `generatedAt` (string)
- `limitations` (array)
- `product`
- `provenance` (object)
- `receipt`
- `receiptEnvelope` (object)
- `retryable` (boolean)
- `schemaVersion`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-jithox-einvoice-readiness/mcp#diagnostics

## Score history

- 2026-08-03: 76
- 2026-08-02: 75
- 2026-08-01: 75
- 2026-07-31: 74
- 2026-07-30: 71
- 2026-07-29: 71
- 2026-07-28: 70
- 2026-07-27: 69
- 2026-07-26: 69

## Links

- Remote endpoint: https://mcp.jithox.com/mcp
- Website: https://jithox.com/mcp/e-invoice
- Changelog RSS feed: https://verifymcp.io/servers/com-jithox-einvoice-readiness/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-jithox-einvoice-readiness/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-jithox-einvoice-readiness/mcp