MCP servers / Jithox E-Invoice

Jithox E-Invoice

Check whether a counterparty and an invoice are ready for European e-invoicing before anything is sent.

Jithox · EU capability · global access · Finance operations · Available

Overview

Who it is for: Any business or agent invoicing into the EU, wherever the business itself is registered — a US supplier billing a German customer has the same question as a Belgian one.

Endpoint

https://mcp.jithox.com/mcp

Protocol

2026-07-28 (also 2025-11-25, 2025-06-18, 2025-03-26)

Authentication

OAuth 2.1 with PKCE (S256). The server is its own OAuth resource.

Source

Live VIES for VAT status and Peppol SML/SMP for participant lookup. A provider outage is reported as unavailable, never as invalid.

Tool explorer

Every tool this server prices, with its input schema, its output shape and an example. This explorer is read-only documentation: nothing on this page calls the server, so reading it executes nothing and costs nothing.

{ "vatNumber": "BE0403170701" }

{ "state": "valid",
  "countryCode": "BE",
  "normalisedVatNumber": "BE0403170701",
  "reasons": [] }

{ "vatNumber": "BE0403170701" }

{ "state": "registered",
  "requestDate": "2026-08-03",
  "sources": [{ "name": "VIES", "retrievedAt": "2026-08-03T09:12:04Z" }] }

{ "invoice": { "id": "INV-1", "issueDate": "2026-08-03",
              "supplier": { "vatNumber": "BE0403170701" } } }

{ "state": "invalid",
  "blocking": [{ "code": "BR-06", "message": "Seller name is required" }],
  "warnings": [] }

{ "participantId": "0208:0403170701" }

{ "state": "registered",
  "participantId": "0208:0403170701",
  "supportedDocuments": ["urn:cen.eu:en16931:2017"] }

{ "verifyWithProvider": false }

{ "state": "not_configured",
  "blocking": [{ "code": "NO_PEPPOL_ID", "message": "No Peppol participant id on this workspace" }],
  "nextActions": ["Register a Peppol participant id"] }

How charging works

• —Authorize — your credential, its scope and the product are checked.
• —Reserve — the price is held against your trial or balance before anything runs.
• —Execute — the tool does its work.
• —Capture or release — an accepted, usable answer captures; anything else releases the hold in full.
• —Receipt — an accepted call produces a signed receipt you can verify offline.

Failed calls cost €0.00. Errors, refusals, rate limits, kill switches and upstream outages never charge you and never consume a free call.

Your usage and balance

One workspace has one prepaid balance and one free allowance, both covering every available Jithox MCP server. You do not buy a balance per server, you do not get a fresh allowance per server, and a credential never holds money of its own.

How the balance works

One workspace → one free allowance → one prepaid EUR balance → a key per MCP server → paid calls → receipts.

• —You do not buy a balance per MCP server — one balance covers all of them.
• —Your workspace gets ONE free allowance: 25 accepted calls for 14 days, not 25 per server. Connecting a second server does not add more free calls.
• —The allowance is held on the first server you connect. A key for another server still works — its calls are charged from your balance.
• —Prices differ per server, so the same balance buys a different number of calls on each. The price list shows how many.
• —A credential holds no money. Rotating or replacing one leaves your balance and your free calls exactly as they were — and it does not restart the 14 days.
• —Future paid Jithox MCP servers draw on this same balance and this same allowance; they do not create a second one.
• —Tax is calculated separately and is never spendable balance.
• —There is no automatic top-up and no automatic subscription — funds are added only when you choose to add them.

Connect

• —Create an account and a workspace.
• —Create a credential — it is shown once.
• —Point your MCP client at the endpoint below.
• —Approve the consent screen with your access key.
• —initialize, then tools/list.
• —Call a tool and read the receipt in _meta.

# Remote MCP server — transport: streamable-http (Streamable HTTP)
https://mcp.jithox.com/mcp

# Your client discovers OAuth automatically (RFC 9728):
https://mcp.jithox.com/.well-known/oauth-protected-resource

# Client config (VS Code shape; other clients on the connect page):
{
  "servers": {
    "jithox-einvoice": {
      "type": "http",
      "url": "https://mcp.jithox.com/mcp"
    }
  }
}

Example call

initialize and tools/list are free and need no credential. The first priced call, with the documented example arguments of validate_invoice:

POST https://mcp.jithox.com/mcp
{"jsonrpc":"2.0","id":1,"method":"tools/call",
 "params":{"name":"validate_invoice",
           "arguments":{ "invoice": { "id": "INV-1", "issueDate": "2026-08-03",
                         "supplier": { "vatNumber": "BE0403170701" } } }}}

The response carries a decision state, the evidence behind it, and _meta.receipt. If the call is accepted and chargeable, €0.10 is captured from your balance — otherwise the hold is released.

What a first call proves

• —initialize and tools/list are discovery: free, no credential, and they execute nothing. Only tools/call runs a tool; a green handshake proves reachability, not a result.
• —tools/call needs a credential your MCP client obtains through the server's OAuth consent screen (or a connection you created once on your account page). Authentication is not payment: a call is charged from your prepaid balance only when it returns an accepted result; the first 25 accepted calls per workspace are free for 14 days.
• —A format check (validate_vat_number, check_registration_number_format) that answers valid or FORMAT_VALID proves only that the identifier is well-formed — not that it exists or is active; an invalid or needs_review answer proves the opposite or nothing. A registry check (verify_vat_vies, verify_company_registration) asks the official source and can answer unavailable when that source does not.
• —Add the server URL to your MCP client, let it complete the consent screen, then make one call from your client. If your client cannot open a browser, create a connection on your account page and send it as a bearer header — the same scopes, revocable there.
• —401 means no valid credential reached the server — not that the tool is missing or that anything ran. A JSON-RPC error carries a stable code and a recovery.next_step; under the published pricing contract only accepted results are charged, so an error is not an accepted result — your account page lists every charge. A transport failure or 5xx after tools/call was sent means the outcome is UNKNOWN: check before you retry, never retry blindly.

Errors

Limits and disclaimers

• —Read-only: it never sends an invoice and has no send capability.
• —Validation, not certification — no compliance guarantee and no fiscal or legal advice.
• —A provider outage returns a truthful unavailable rather than a guessed verdict.