# Jithox > Jithox ships TWO separate products. They share a brand and nothing else. > > Jithox MCP International, English-first, for developers and AI > agents. Read-only EU checks over the Model Context > Protocol. This file describes it. > Jithox WhatsApp For a self-employed person turning customer messages > into quotes and invoices — English at /whatsapp, > Dutch at /nl/whatsapp. It is NOT an MCP capability, > has no endpoint and no tools, and nothing in this > file applies to it. Everything below is about Jithox MCP. This file is a pointer, not a replacement for the crawlable pages: the canonical product pages carry the authoritative claims. ## Start here if you are a machine https://jithox.com/api/agent-context/v1 names every canonical Jithox source and what each is authoritative for: capabilities, pricing, changelog, /developers and this file. Read it first, and prefer it over this file for anything you intend to repeat as fact. Pricing, chargeable result states, trial limits and the delegation rules are a versioned machine-readable document at https://jithox.com/api/pricing/v1 — read it before making a call, not this file. ## Canonical pages - https://jithox.com/ — Jithox MCP, English. Canonical, and the x-default. - https://jithox.com/nl — the same product in Dutch (nl-BE). - https://jithox.com/mcp — the E-Invoice capability page, with JSON-LD. - https://jithox.com/mcp/playground — every response shape, free, no account. - https://jithox.com/mcp/pricing — the price list and the billing rules. - https://jithox.com/mcp/e-invoice — developer documentation and connection. - https://jithox.com/api/pricing/v1 — the versioned pricing contract. There is deliberately no geo-redirect. `/` is English for every visitor; a Dutch reader chooses `/nl` from a visible link. ## Jithox E-Invoice — the one product on sale A remote Streamable HTTP MCP server with OAuth 2.1 (Dynamic Client Registration and PKCE S256). `initialize` and `tools/list` are open for discovery; a tool call needs access. Every result carries source, date and provenance and uses explicit decision states; every server serves a receipt-verification public key at /receipts/public-key.pem, so a signed receipt can be verified without any secret. Read-only: none sends, writes, files, pays or transmits anything. Endpoint: https://mcp.jithox.com/mcp Five tools: validate_vat_number, verify_vat_vies, lookup_peppol_participant, validate_invoice, get_einvoice_readiness. No send capability exists (send_peppol_invoice is not a tool): Jithox does not send invoices through this MCP, and validation output carries no compliance guarantee. get_einvoice_readiness reports the CALLER'S OWN workspace configuration — it takes no company or VAT number and says nothing about a counterparty. Decision states include not_found, not_configured, needs_review and unavailable; a provider outage is never converted into a business verdict. Status (2026-08-01): LIVE TECHNICAL BETA. THE OFFER, IN FULL: - Free playground: example data, no account, no live source queried. - Free trial: 25 live calls over 14 days, no card. Self-service — activation runs a browser check at https://mcp.jithox.com/onboarding/free and issues a key. There is no form, no waiting list and nobody to e-mail. - Then prepaid pay-as-you-go at €0.10 per accepted call, from a €10 minimum (€10 = 100 prepaid calls). Balances add up. - No subscription, no automatic renewal, no overage. When the balance runs out, calls are refused rather than billed. - A truthful negative is an answer and is charged. An outage, timeout, rejected input, auth failure, rate limit or replayed request is never charged. - Guided technical integration at €299 is optional, not a gate. - The price is introductory and subject to review as real usage data arrives. Nothing about the trial requires a Belgian postcode, phone number, company form or VAT number. These are EU checks, usable by a team anywhere with European workflows. Measured claim correction (2026-07-27, JX-140C): we tested whether routing these checks through Jithox produces safer conclusions than calling EU VIES and the Peppol SMP directly. Across 360 blinded paired runs the unsafe-decision rate was 0/180 on BOTH sides. We therefore do NOT claim better answers, safer reasoning or a composed readiness verdict, and we do not price on answer quality. What differs from a direct API call is the evidence: an explicit source state, a scoped budget, accounting, and a signed receipt that verifies offline. Not independently penetration-tested. No paying external developers yet. Official MCP Registry: com.jithox/einvoice-readiness v1.0.0-canary — https://registry.modelcontextprotocol.io/v0/servers/com.jithox%2Feinvoice-readiness/versions/1.0.0-canary ## The other three capabilities — NOT for sale Listed because a withdrawn product must still be described truthfully to anyone holding a receipt from it. Withdrawing a product commercially and destroying its evidence are different acts, and only the first has happened: endpoints, registry records and every receipt ever issued are preserved and keep working. - Jithox EU Import Preflight — PRIVATE EVALUATION, not for sale. Five read-only tools over the official July-2026 TARIC baseline: search_taric_codes, check_eu_import_measures, estimate_low_value_import_cost, validate_eori, prepare_import_preflight_receipt. Endpoint: https://import.mcp.jithox.com/mcp. Results are candidates only, never binding — only a Binding Tariff Information decision binds. It runs and its answers are correct, but the receipt-verification page still carries another product's name, so there is no price, no trial and no connection offer. The endpoint is documented rather than advertised: someone holding a receipt from it has to be able to find where it came from. Official MCP Registry: com.jithox/eu-import-preflight v0.1.0 — https://registry.modelcontextprotocol.io/v0/servers/com.jithox%2Feu-import-preflight/versions/0.1.0 - Jithox EU Sanctions Preflight — WITHDRAWN FROM SALE: not offered, not priced, not promoted. Five read-only tools over the official EU Consolidated Financial Sanctions List: screen_sanctioned_name, screen_sanctioned_identifier, get_sanctions_listing, list_sanctions_regimes, prepare_screening_receipt. Endpoint: https://sanctions.mcp.jithox.com/mcp. EU list only, not global; a not-listed result is never clear, safe or approved and is not a guarantee of non-designation. EU FSF reuse rests on Commission Decision 2011/833/EU with attribution (JX-107). Official MCP Registry: com.jithox/eu-sanctions-preflight v0.1.0 — https://registry.modelcontextprotocol.io/v0/servers/com.jithox%2Feu-sanctions-preflight/versions/0.1.0 - Jithox EU Energy Label Preflight — UNAVAILABLE. Never publicly released: no public endpoint, no DNS record, no registry entry. There is nothing to connect to, and no endpoint is published for it anywhere. ## Agent purchasing No agent can purchase autonomously. A purchase needs either explicit human approval, or a bounded, product-scoped, expiring, revocable delegation registered by its human owner — accepted today only by the x402 SANDBOX settlement rail, which settles testnet value behind a default-off flag. No production rail accepts a delegation, and there is no automatic agent payment with real money. ## Key facts - [For AI systems and developers](https://jithox.com/ai-systems): product identity, capability boundaries, the exact five MCP tools, authentication, approval semantics, receipts, unsupported actions. - [Trust and limits](https://jithox.com/trust): mechanisms and their honest limits — internal tests are not an independent pentest; delivery does not prove a human read a document; receipts do not prove legal correctness. - No sending without human approval. No bulk mail. The MCP is read-only. ## Jithox for WhatsApp — deliberately not described here https://jithox.com/whatsapp (English) and https://jithox.com/nl/whatsapp (Dutch) are a separate product for self-employed people. It exposes no MCP endpoint, no tools and no scopes, it is not part of the MCP fleet, and it must not be presented as an MCP capability. Its own pages state what it does and does not do today. Do not infer anything about it from this file. ## Contact - info.jithox@gmail.com