Remote MCP · Endpoint
Jithox E-Invoice Readiness MCP server
Yes, as of 1 hour ago: the connection was refused or dropped.
DownLast checked 1 hour ago
Server URL
https://mcp.jithox.com/mcp
The last check failed: the connection was refused or dropped.
- Registry name
- com.jithox/einvoice-readiness
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 5 tools
- Uptime, last 30 days
- 78.9% from 19 checks
- Described by its publisher as
- Read-only EU e-invoice checks: VAT format, VIES, Peppol lookup. Returns evidence, no filing.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Failed - the connection was refused or dropped | — |
| 18 hours ago | Failed - the connection was refused or dropped | — |
| 2 days ago | Failed - the connection was refused or dropped | — |
| 3 days ago | Failed - the connection was refused or dropped | — |
| 4 days ago | Handshake completed | 330 ms |
| 5 days ago | Handshake completed | 338 ms |
| 6 days ago | Handshake completed | 328 ms |
| 7 days ago | Handshake completed | 327 ms |
| 10 days ago | Handshake completed | 362 ms |
| 13 days ago | Handshake completed | 372 ms |
| 15 days ago | Handshake completed | 328 ms |
| 17 days ago | Handshake completed | 402 ms |
| 19 days ago | Handshake completed | 327 ms |
| 21 days ago | Handshake completed | 342 ms |
| 23 days ago | Handshake completed | 325 ms |
| 25 days ago | Handshake completed | 347 ms |
| 27 days ago | Handshake completed | 415 ms |
| 28 days ago | Handshake completed | 385 ms |
| 29 days ago | Handshake completed | 329 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 26 responding of 30.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with Jithox E-Invoice Readiness and makes no claim about it beyond what these checks measured.