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
What a call costs
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
- 2025-06-18
- 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.
validate_vat_number
Structural validation of an EU VAT number.
When to use it: Before any lookup that costs time — a malformed number is rejected without touching a provider.
- Required input
- vatNumber
- Optional input
- —
- Output fields
- state, countryCode, normalisedVatNumber, reasons[], sources[]
- Price
- €0.10 per accepted call
Example input
{ "vatNumber": "BE0403170701" }Example output
{ "state": "valid",
"countryCode": "BE",
"normalisedVatNumber": "BE0403170701",
"reasons": [] }- Charges you
- valid, invalid, needs_review
- Costs €0.00
- every error
verify_vat_vies
Authoritative VAT status from the EU VIES service.
When to use it: When you need the registry's answer, not just a well-formed number.
- Required input
- vatNumber
- Optional input
- requesterVatNumber
- Output fields
- state, requestDate, name, address, sources[]
- Price
- €0.10 per accepted call
Example input
{ "vatNumber": "BE0403170701" }Example output
{ "state": "registered",
"requestDate": "2026-08-03",
"sources": [{ "name": "VIES", "retrievedAt": "2026-08-03T09:12:04Z" }] }- Charges you
- registered, not_registered
- Costs €0.00
- unavailable, plus every error
validate_invoice
Structural validation of an invoice against BIS 3.0 expectations.
When to use it: Before submitting a document to a network that will reject it silently.
- Required input
- invoice
- Optional input
- profile
- Output fields
- state, findings[], blocking[], warnings[]
- Price
- €0.10 per accepted call
Example input
{ "invoice": { "id": "INV-1", "issueDate": "2026-08-03",
"supplier": { "vatNumber": "BE0403170701" } } }Example output
{ "state": "invalid",
"blocking": [{ "code": "BR-06", "message": "Seller name is required" }],
"warnings": [] }- Charges you
- valid, invalid, partial, needs_review
- Costs €0.00
- every error
lookup_peppol_participant
Discover whether a party can receive documents over Peppol.
When to use it: Before assuming a counterparty is reachable on the network.
- Required input
- participantId
- Optional input
- documentType
- Output fields
- state, participantId, supportedDocuments[], sources[]
- Price
- €0.10 per accepted call
Example input
{ "participantId": "0208:0403170701" }Example output
{ "state": "registered",
"participantId": "0208:0403170701",
"supportedDocuments": ["urn:cen.eu:en16931:2017"] }- Charges you
- registered, not_registered
- Costs €0.00
- unavailable, plus every error
get_einvoice_readiness
Whether YOUR OWN workspace is configured to issue European e-invoices, and what is missing.
When to use it: Before you rely on your own setup — it diagnoses your configuration. For a counterparty, use verify_vat_vies and lookup_peppol_participant instead.
- Required input
- —
- Optional input
- verifyWithProvider
- Output fields
- state, blocking[], warnings[], nextActions[], sources[]
- Price
- €0.10 per accepted call
Example input
{ "verifyWithProvider": false }Example output
{ "state": "not_configured",
"blocking": [{ "code": "NO_PEPPOL_ID", "message": "No Peppol participant id on this workspace" }],
"nextActions": ["Register a Peppol participant id"] }- Charges you
- needs_review, not_configured
- Costs €0.00
- ready, not_ready, unavailable, plus every error
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.
Shared usage and balance
One workspace has one free trial and one prepaid balance. Both are shared across every available Jithox MCP server — you do not buy a balance per server, and a credential never holds money of its own.
Free trial
25 accepted calls
14 days, shared across the available MCP servers. No card. The trial starts at your first call, not at sign-up.
Balance
One prepaid EUR balance
For all available Jithox MCP servers. Spend it wherever you like. No subscription and no automatic top-up.
How the balance works
One workspace → one shared trial → one shared EUR balance → several authorized MCP servers → paid calls → receipts.
- You do not buy a balance per MCP server — one balance covers all of them.
- 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.
- Future paid Jithox MCP servers draw on this same balance; 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 (Streamable HTTP) https://mcp.jithox.com/mcp # Your client discovers OAuth automatically: https://mcp.jithox.com/.well-known/oauth-protected-resource # Placeholders — never commit real values YOUR_CLIENT_ID YOUR_CREDENTIAL
Example call
POST https://mcp.jithox.com/mcp
{"jsonrpc":"2.0","id":1,"method":"tools/call",
"params":{"name":"validate_vat_number","arguments":{ /* see required input above */ }}}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.
Errors
| Code | Meaning |
|---|---|
| 401 | Authentication required — re-run the OAuth flow. |
| 403 | Insufficient scope, or a token for a different server. |
| 402 | Free calls used up and the balance cannot cover this call. Nothing ran, nothing was charged. |
| 429 | Rate limited. Honour retry-after; nothing was charged. |
| 503 | The product or its source is unavailable. This does NOT mean the server crashed — it means we will not answer without a source we trust. |
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.