How to connect
Same URL, five paste targets. Ready surface · Live OK. Not a safe-to-install badge. Handshake this URL
Paste into Settings → MCP or .cursor/mcp.json.
{
"mcpServers": {
"jithox": {
"url": "https://jithox.com/api/mcp"
}
}
}
Paste into .vscode/mcp.json.
{
"mcpServers": {
"jithox": {
"url": "https://jithox.com/api/mcp"
}
}
}
Settings → Connectors → Add → Custom → Web. Paste the URL. Enable in a new chat.
Claude → Settings → Connectors → Add → Custom → Web
Name: Jithox
URL: https://jithox.com/api/mcp
OAuth only if this server requires it.
Save, start a new chat, enable the connector.
Developer mode custom connector. ChatGPT cannot reach localhost.
Settings → Apps & Connectors → Advanced → Developer mode ON
Create custom connector
Name: Jithox
MCP server URL: https://jithox.com/api/mcp
Auth: none unless the server requires OAuth
New chat → + → Developer mode → enable the connector
Register the HTTPS URL, then claude mcp list.
claude mcp add --transport http jithox \
https://jithox.com/api/mcp
Pass on session/new as mcpServers when the agent advertised HTTP MCP.
[
{
"type": "http",
"name": "jithox",
"url": "https://jithox.com/api/mcp"
}
]
Paste into a README or docs site. The widget loads snippets from Influzer — still not a SAFE badge.
Same handshake clock as this listing (overlay / warm / seed; live tools/list only if that is missing). Indigo is live_ok, amber is auth_required, gray is unreachable. Not a SAFE badge. Stdio listings have no badge.
[](https://www.influzer.ai/mcp/probe?url=https%3A%2F%2Fjithox.com%2Fapi%2Fmcp)
<div data-influzer-install="jithox"></div>
<script async src="https://www.influzer.ai/embed/install.js"></script>
https://www.influzer.ai/embed/mcp/jithox.md
Recipes using this server
No published recipes yet for this server.
Listing quality
Observable facts from our catalog and daily probe — not a safe-to-install badge.
- Surface
- Ready surface
- Auth gate
- No auth gate seen
- Tools source
- tools/list (live)
Observable catalog + probe facts — not a safe-to-install badge. How we verify.
Verification summary
Stored signals only. Not a safety score.
- Verification grade
- A (100)
- Last verified
- Status
- Live OK
- Response time
- 299 ms
- Auth
- No auth gate seen
- Transport
- http, HTTPS
- Tools indexed
- 5
Probe history
- · live_ok · 299 ms
- · live_ok · 298 ms
Tools
(5)-
verify_ibanVerify an IBAN structure and checksum
-
check_peppol_readyCheck if a party is Peppol-ready
-
check_payment_changeDetect payment-detail change risk before paying
-
lookup_peppol_participantLook up a Peppol participant
-
preflight_paymentPreflight a payment for common failure modes
Tool source: tools/list (live) · last probed 2026-11-10