Developers
Tools for developers and AI agents.
Connect Jithox tools to your AI client. Find MCP servers, supported connections, documentation and machine-readable contracts. Each tool has its own scope, availability, access requirements and price source.
Install Jithox in your AI client
Public MCP endpoint: https://jithox.com/api/mcp
8 tools on this address; 5 of them answer without an account or key.
This public endpoint is separate from the authenticated Jithox connection and product servers below. Client availability depends on your plan and workspace permissions.
These links open your installed client. Review the server configuration before adding it.
Claude Code
claude mcp add --transport http jithox https://jithox.com/api/mcpCodex
codex mcp add jithox --url https://jithox.com/api/mcpGrok Build CLI
grok mcp add --transport http jithox https://jithox.com/api/mcpGrok Build CLI 1.0.46 (2026-10-02): doctor exit 0, healthy=true, protocol 2025-11-25, 8 tools discovered. Discovery only; no tool call or grok.com test. Setup reference — Grok Build CLI
Claude.ai / Claude Desktop
- Open Customize → Connectors → Add custom connector. On Team and Enterprise, an owner first adds it in Organization settings → Connectors → Add → Custom → Web.
- Name: Jithox. Remote MCP server URL: https://jithox.com/api/mcp.
- For this public setup, choose No sign-in if Authentication is shown; leave OAuth credentials and request headers empty. Click Add, then enable the connector for your conversation.
ChatGPT developer mode
- On ChatGPT web, open Settings → Security and login → Developer mode and turn it on. Then go to https://chatgpt.com/plugins and select the plus button to add your MCP app (custom connector).
- Name: Jithox. Remote MCP server URL: https://jithox.com/api/mcp. Authentication: No Authentication.
- In the app details, enable only verify_iban for this demonstration. Select the app in a conversation when it fits the task; no search/fetch pair is required.
- The platform supports SSE and streaming HTTP, with OAuth, No Authentication or Mixed Authentication. No Authentication fits this free demonstration.
- ChatGPT asks for confirmation by default for write actions. It uses readOnlyHint to identify read-only tools and treats tools without that hint as writes. MCP annotations are not authorization.
- Expand the tool details and inspect the actual JSON input and output. A configured app is not proof that a call ran; surface errors or missing results rather than substituting model prose.
Gemini CLI
- Merge this block into ~/.gemini/settings.json; keep your other server entries.
{
"mcpServers": {
"jithox": {
"httpUrl": "https://jithox.com/api/mcp"
}
}
}n8n
- Use the community package n8n-nodes-jithox. Follow its README for installation and credentials. This is a separate n8n integration, not an MCP install link.
n8n-nodes-jithoxGrok (grok.com)
- According to xAI documentation: grok.com/connectors → New Connector → Custom → https://jithox.com/api/mcp.
- On Grok Business and Enterprise, a team admin must first provision the connector. The free tools on this public endpoint need no key.
- Not tested on grok.com. Inspect the actual tool result; a configured connector is not proof of a successful call.
Goose
- Use Add to Goose above, or run goose configure → Add Extension → Remote Extension (Streamable HTTP).
- Name: Jithox. URL: https://jithox.com/api/mcp.
- Deeplink decoded on 2026-10-02; not tested in Goose. Review the configuration before adding it.
Skills for dozens of agents
- skills.sh can add task instructions to supported agents. Review the skill and choose your agent before installing.
- Discovery on 2026-10-02 found pay-invoices-safely. This is a skill installation, not a completed tool call or an MCP connection test.
npx skills add victor-emmanuel-c/jithox-mcpClient setup only. A saved configuration is not proof of a tool call. Check the actual tool output; do not substitute model prose for a missing result.
Connect Kit: Published on npm as `jithox` (0.2.4). Install: npm install -g jithox@0.2.4. Commands in the published version: auth, call, connect, disconnect, discover, doctor, init, status, test. Not yet installable (0.3.0, approved artefact): --version, file-to-data, run. Setup availability and alternatives.
Free access, right now
25 accepted tool calls, 14 days, no card. Activation is automatic — there is no form to fill in, nobody to email and nothing to wait for.
One IBAN check, three ways in
This check is free (€0): MCP and CLI need no account; REST needs a Jithox connection-key. Checks structure and check digits, not account existence or ownership. Use MCP or CLI below to try this without a key.
MCP client
Claude, Cursor, or anything else that speaks MCP.
Access: Anonymous for this free check on the public MCP endpoint.
Connect your MCP client to https://jithox.com/api/mcp using the installation guide above, then send:
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "verify_iban",
"arguments": {
"iban": "BE68 5390 0754 7034"
}
}
}Expected result: data.status is valid and data.countryCode is BE.
Terminal
Run this command in bash with Node.js 20 or newer.
Access: Anonymous for this free check; no login or connection-key needed.
npx jithox call verify_iban --input '{"iban":"BE68 5390 0754 7034"}'Expected result: data.status is valid and data.countryCode is BE.
REST with a key
Post JSON from your backend; this curl command is for bash.
Access: A Jithox connection-key is required for /api/v1/*, including free checks; without it the response is 401 missing_credential.
Already have a connection-key? Replace <YOUR_CONNECTION_KEY> locally; never share the key in a chat or ticket.
On Your Jithox connection, a signed-in person creates a connection and copies its key, shown once.
curl -X POST https://jithox.com/api/v1/iban/verify \
-H "Authorization: Bearer <YOUR_CONNECTION_KEY>" \
-H "Content-Type: application/json" \
-d '{"iban":"BE68 5390 0754 7034"}'Expected result: data.status is valid and data.countryCode is BE.
POST /api/invoice/review is a separate, anonymous route for local invoice checks.
What is publicly available
Jithox E-Invoice Readiness
Before you send a structured e-invoice you need to know whether the counterparty's VAT number resolves and whether they can actually receive one on the Peppol network — two checks that are easy to get wrong by hand and expensive to get wrong at scale.
5 read-only tools: validate_invoice, validate_vat_number, verify_vat_vies, lookup_peppol_participant, get_einvoice_readiness
Jithox EU Energy Label Preflight
A product listing that shows the wrong energy class or a missing EPREL registration is a listing that gets pulled, and checking a catalogue against the official EPREL database by hand does not scale past a handful of models.
5 read-only tools: search_eprel_products, get_eprel_product_record, get_eprel_energy_label_data, compare_eprel_product_metrics, prepare_energy_label_preflight_receipt
Jithox EU Import Preflight
Before goods are ordered from outside the EU, somebody has to find the right commodity code, check which import measures attach to it, and confirm the counterparty's EORI number — usually by hand, across several official portals.
5 read-only tools: validate_eori, search_taric_codes, check_eu_import_measures, estimate_low_value_import_cost, prepare_import_preflight_receipt
Jithox EU Counterparty Sanctions Preflight
Onboarding a new supplier or counterparty means screening them against the EU sanctions list, and the screening is only worth anything if you can show afterwards exactly what was checked, against which list version, and when.
5 read-only tools: screen_sanctioned_name, screen_sanctioned_identifier, get_sanctions_listing, list_sanctions_regimes, prepare_screening_receipt
Machine-readable sources
If you are an agent rather than a person, start at the agent context. It names every document below and says what each one is authoritative for, so you never have to guess which answer is current.
- Agent context /api/agent-context/v1
- Start here if you are a machine. Names every document below and what each one is authoritative for.
- Gateway bootstrap v2 /api/agent-bootstrap/v2
- Gateway endpoints, native client setup and the verified availability of Connect Kit distribution.
- Capabilities /api/capabilities/v1
- What Jithox can do, which endpoints answer publicly (publicly_available), and which capabilities are offered for sale (release_state, access_mode).
- Pricing /api/pricing/v1
- What access costs and what the free tier includes.
- Changelog /api/changelog/v1
- What changed, and how well each change is known.
- llms.txt /llms.txt
- A compact overview of Jithox as a whole.
- Agent skill /SKILL.md
- Instructions an agent can load: every endpoint, the three access routes, and what each error means.
- Quickstart /docs/quickstart
- Copyable terminal commands from discovery to a first call and its receipt.
Honest limits
- A readiness answer describes what the consulted sources returned at the stated time. It is not a legal, fiscal or compliance statement.
- It does not combine the VAT, company and Peppol checks into a single counterparty verdict. Each check is its own tool, and your agent decides what the combination means.
- It does not send an invoice, to Peppol or anywhere else.
- It does not create, book or file an invoice.
- There is no SLA, and no independent penetration test has been performed.
Related
- Engineering blog
- Verifying a receipt offline
- What a VAT check actually returns
- Trust and controlled execution
- Pricing
- Privacy
- Terms
Three different things called paying
Paying for Jithox use — an agent does this on its own. A priced tool deducts from your balance per answer, and the remaining balance comes back on every call. No human is in that loop.
Adding to the balance — a person, once, on the top-up page. An agent cannot buy credits, and nothing on this page is a purchase.
Buying something from a third party for your customer — Jithox does not do this at all, in any route.