Jithox E-Invoice Readiness — for AI systems & agent runtimes

A remote MCP capability provider for EU B2B invoice preflight. This page states, in machine-actionable terms, what an agent runtime needs to admit Jithox. Machine-readable form: https://sanctions.mcp.jithox.com/.well-known/jithox-capability.json (informational, not an MCP standard).

Identity & connection

• Organization: Jithox · domain jithox.com · server com.jithox/einvoice-readiness.
• Endpoint: POST https://sanctions.mcp.jithox.com/mcp — Streamable HTTP (MCP). Protocol versions negotiated: 2025-11-25, 2025-06-18, 2025-03-26.
• Auth: OAuth 2.1 + PKCE. Discovery: https://sanctions.mcp.jithox.com/.well-known/oauth-protected-resource. No hardcoded bearer; tokens refresh.

Capabilities — exactly five, read-only

• validate_invoice (scope einvoice:validate) · validate_vat_number (vat:format) · verify_vat_vies (vat:vies) · lookup_peppol_participant (peppol:lookup) · get_einvoice_readiness (einvoice:readiness).
• Every tool is readOnlyHint:true. There is no send and no sixth tool; send_peppol_invoice does not exist. A host may grant a subset of scopes — a tool outside the granted scopes is refused with 403 insufficient_scope, is not billed, and triggers no provider call.

Results your agent must read correctly

• Uniform decision: ready · not_ready · needs_review · unavailable, with blockingReasons, warnings, nextActions, evidence, provenance, requestId, receiptId.
• HTTP 200 is not "ready". An accepted (billed) call can carry not_ready/needs_review/unavailable. Read decision.status, not the HTTP code. unavailable is never invalid and never not_registered — it is an unknown. Do not hide warnings; pass blockingReasons and nextActions through.
• On needs_review your agent must not conclude on its own — human or additional checks are required.
• See the three decisions concretely (fixture demo) — ready / needs_review / unavailable, with a verifiable demo receipt.

Trust & lifecycle

• Quota: 30 days · 10,000 accepted checks · 60/min · 5,000/day · hard stop · no overage · no auto-renewal. A rejected call consumes nothing; retried identical calls replay and never double-bill.
• Receipts: Ed25519, committing the whole decision — verify offline with https://sanctions.mcp.jithox.com/receipts/public-key.pem (metadata at https://sanctions.mcp.jithox.com/receipts/verification). A valid signature is not a legal/fiscal certification.
• Revoke any time from your client (or the OAuth revocation endpoint). Recovery + errors: /docs §5.

Not supported (do not attempt)

Sending invoices, Peppol/invoice submission, accounting, tax/legal advice, guaranteed receiver acceptance, general search/Gmail/calendar/browser/computer tools. This is a bounded read-only preflight.

Connect from your runtime

Only the MCP Streamable-HTTP + OAuth contract is tested in clean-room (official MCP SDK + conformance). The examples below use each runtime's official configuration; they are compatible with the tested contract but are not an endorsement by, or partnership with, any vendor.

Claude Code: claude mcp add --transport http jithox-einvoice https://sanctions.mcp.jithox.com/mcp, then /mcp to authenticate.

Cursor / VS Code: add a remote MCP server with URL https://sanctions.mcp.jithox.com/mcp and approve OAuth (see /docs §2).

OpenAI (Responses API / Agents SDK): add a remote MCP server (Streamable HTTP) at https://sanctions.mcp.jithox.com/mcp; use allowed_tools to restrict to a subset and require_approval for tool-call approval.

OpenClaw: openclaw mcp add the URL with --auth oauth; use toolFilter.include to allowlist tools.

Any MCP SDK / generic host: connect over Streamable HTTP, complete OAuth, call tools/list (five tools), then tools/call.

Contact

General & support: info.jithox@gmail.com. Security: https://sanctions.mcp.jithox.com/.well-known/security.txt. Docs: /docs. This is a public developer pilot — not independently penetration-tested, not certified.