DEV Community: jithox

How to connect Grok or Cursor to Jithox MCP (prepaid EU business checks)

jithox — Sat, 19 Sep 2026 10:53:54 +0000

Your agent stays the brain. Jithox adds read-only EU business checks with clear rights, costs, and receipts.

LIVE prices

E-Invoice (VIES/Peppol): EUR 0.10
EU Import Preflight: EUR 0.25
EU Energy Label Preflight (EPREL): EUR 0.25
EU Sanctions Preflight (EU list only): EUR 0.50

Trial: 25 accepted calls / 14 days, no card (per workspace). Failed, unavailable, timed-out, or unauthorized calls are not charged.

Jithox is not an Access Point: it does not send invoices or file with authorities. x402 is a canary reference only; use prepaid MCP connect for production.

Prices: https://jithox.com/api/pricing/v1

Machine pointer: https://jithox.com/llms.txt

Connect: https://jithox.com/connect-your-ai

Cursor (`mcp.json`)

Use the Streamable HTTP endpoint:

{"mcpServers":{"jithox-einvoice":{"url":"https://mcp.jithox.com/mcp","headers":{"Authorization":"Bearer YOUR_JITHOX_ACCESS_KEY"}}}}

Reload Cursor and ask: “Verify this EU VAT number via VIES and return the receipt fields.” Follow the connect wizard for auth details.

Grok

Grok-based MCP clients use the same endpoint, https://mcp.jithox.com/mcp. Open https://jithox.com/connect-your-ai and choose Grok / Cursor, then run an accepted call and keep its receipt.

First useful checks

validate_vat_number — structure only
verify_vat_vies — live VIES (unavailable ≠ invalid)
lookup_peppol_participant — directory lookup, not send

Keep the receipt beside your CRM/ERP result. A source outage is not a negative verdict. Sanctions are EU-list-only; TARIC results are candidates; EPREL fields are supplier-declared.

Ready? https://jithox.com/connect-your-ai

A VAT format check is not an invoice delivery check

jithox — Thu, 17 Sep 2026 19:45:35 +0000

An EU e-invoice workflow can pass the format step and still fail downstream.

Generating a VAT number in the right format is not the same as checking it against live VIES, or confirming that the recipient is a reachable Peppol participant. Those are separate checks, and an agent should say which one it actually completed.

For teams wiring agents into business workflows, two small details prevent expensive ambiguity:

Keep a dated receipt with the result, inputs, and check type.
Make budgets explicit: accepted E-Invoice calls are €0.10; unavailable or failed calls are €0, not silent success.

Jithox provides prepaid EUR, read-only MCP tools for agents: live VIES + Peppol participant preflight and invoice readiness, plus EU Import Preflight, EU Energy Label, and EU Sanctions checks. It does not send or pay invoices.

Try 25 accepted calls for 14 days without a card, then connect your AI agent:
https://jithox.com/connect-your-ai

When your agent says the VAT number is fine, ask for the dated receipt

jithox — Mon, 14 Sep 2026 19:53:45 +0000

Your AI agent can draft an invoice, pull a VAT number out of a PDF, and sound very sure that everything checks out.

That confidence is not a receipt.

If you build agents or MCP tools for EU B2B work, you already know the gap: the model can claim a VAT number is valid, or that a buyer is Peppol-reachable. What it often cannot show you is a dated trail of what was looked up, when, and with what result.

This post is for people shipping agents on Claude, ChatGPT, Cursor, Codex, Grok, and similar hosts. The agent stays the brain. What you wire in next is prepaid, read-only evidence.

Agents are great at language. Registries are not language.

VIES does not care how persuasive your prompt was. Peppol participant lookup is not a vibe check. Invoice readiness is not "looks fine in the chat."

When an agent says "VAT is fine," you want answers to questions like:

Was the format check run, or did the model just recognize a familiar pattern?
Was live VIES called, and on which date?
Was the result valid, invalid, or unavailable (registry did not answer)?
Did anyone look up Peppol reachability for that counterparty, or did the agent assume e-invoicing readiness from a website or a memory?

Without those answers, you have a fluent assistant. You do not have an audit trail.

Dated receipts matter because EU work is time-bound. Last month's VIES hit is not today's reverse-charge proof. "Probably on Peppol" is not a participant lookup with a timestamp.

What "receipt" means here

A useful tool receipt for an agent is something you can store next to the task:

which tool ran
which inputs were sent (normalized VAT / participant id, and so on)
what the upstream check returned
when it happened
what it cost

That is "the agent said so" versus "the agent called a bounded tool and kept the proof."

Jithox: read-only prepaid MCP tools, not a new brain

Jithox does not replace Claude, ChatGPT, Cursor, Codex, or Grok. Those stay the reasoning layer.

Jithox is a set of read-only MCP tools billed in prepaid EUR, with clear limits, permissions, budgets, and receipts. You connect once to the MCP host, then your agent can call the tools when a workflow needs EU registry facts instead of guesses.

What is live today

Tool	Price (accepted call)	What it is for
E-Invoice	€0.10	VAT format checks, live VIES, Peppol participant lookup, invoice validation / readiness
Import	€0.25	Import / customs preflight helpers
Energy Label	€0.25	Energy label lookups
Sanctions	€0.50	Sanctions screening lookups

Failed or unavailable calls are €0. You are not charged for a registry outage dressed up as a success.

These tools are read-only. They do not execute payments, send invoices, or act as a Peppol Access Point. Your agent still decides what to do with the evidence. Jithox supplies the check and the receipt.

Why VIES + Peppol reachability belong in the same agent path

Many EU B2B flows need both:

Is this VAT number structurally and registry-valid right now? Live VIES (plus format validation) answers that with a dated result, including unavailable when VIES cannot be reached.
Can this party be reached on Peppol as a participant? Participant lookup is how you stop treating "they do e-invoicing somewhere" as "they are reachable for this network path today."

Agents that only do (1) still invent (2). Agents that only scrape a directory still invent (1). MCP tools with budgets and receipts keep the model on workflow language and the registries on facts.
Invoice validation / readiness sits beside those lookups so the agent can ask whether a document is shaped for the next step, without claiming anything was sent.

Connect once. Keep permissions and budgets boring.

MCP builders already fight Excess Agency: too many tools, too much write power, unclear spend. Keep it narrow:

connect your host to https://mcp.jithox.com/mcp (or start from connect your AI)
grant only the read-only tools you need
set a prepaid budget so a runaway loop cannot surprise you
require the agent to keep the tool receipt next to the business decision

For VAT and Peppol preflight, boring is a feature.

Try it without a card

There is a trial: 25 accepted calls / 14 days, no card. Enough to wire a Claude / Cursor / ChatGPT / Codex / Grok path, fire real VIES and Peppol participant lookups, and see what a dated receipt looks like in your own logs.

Failed and unavailable calls do not eat that budget the way a silent "success" hallucination would. That is deliberate.

Build-in-public note

We ship this for agent and MCP builders who need EU registry truth without replacing their model stack. No fake logos, no invented metrics. The offer is the tools, the prices, the receipts, and the trial.

If your agent still answers "VAT is fine" with only confidence and no dated trail, give it a tool that leaves a receipt.

Connect once: https://jithox.com/connect-your-ai

MCP host: https://mcp.jithox.com/mcp

AI agents still invent "done" — EU invoice checks need dated receipts

jithox — Mon, 14 Sep 2026 09:18:16 +0000

AI agents are getting good at sounding finished.

They are less good at proving a tool call actually happened — and what the authoritative source said.

For European e-invoicing that gap is expensive. A chat that says "VAT looks fine" is not the same as a dated VIES answer that separates invalid from unavailable. Peppol participant reachability is the same class of problem: the agent needs a receipt, not prose confidence.

What we ship today (honest)

Jithox is not another chat brain. Your agent stays the brain. We supply small read-only prepaid EUR MCP tools with receipts:

E-Invoice — €0.10 / accepted call (VAT/VIES, Peppol participant lookup, invoice validation)
EU Import Preflight — €0.25
EU Energy Label Preflight — €0.25
EU Counterparty Sanctions Preflight — €0.50 (candidates, never "clearance")

Failed or unavailable calls are not charged as success. Execution (send / pay / book) is not enabled. We are not a Peppol access point.

Connect path: https://jithox.com/connect-your-ai

Level 1 only

We publish a six-level ladder from VERIFY to EXECUTE. Only Level 1 VERIFY is live. Levels that are not proven are not claimed. That is deliberate product honesty, not a tease.

Who this complements

If you already build local XRechnung / ZUGFeRD / Factur-X format tools, keep that lane. Agents still often need a live registry preflight before they treat a counterparty as ready. That is the complementary gap we focus on.

Try it

Open https://jithox.com/connect-your-ai
Pick the AI you already use
Pick a live check
Connect and keep the receipt

Build in public note: we will keep posting what is actually live versus Labs / not claimed. No invented traction.

— Victor / Jithox