Remote MCP · Endpoint
com.einvoicewiz/einvoicewiz MCP server
No. com.einvoicewiz/einvoicewiz answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://einvoicewiz.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.einvoicewiz/einvoicewiz
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 261 ms
- Tools exposed
- 7 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Generate & validate EN 16931 e-invoices (Factur-X, ZUGFeRD, XRechnung); verification certificates
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 261 ms |
| 18 hours ago | Handshake completed | 246 ms |
| 2 days ago | Handshake completed | 267 ms |
| 3 days ago | Handshake completed | 267 ms |
| 4 days ago | Handshake completed | 246 ms |
| 5 days ago | Handshake completed | 665 ms |
| 6 days ago | Handshake completed | 263 ms |
| 7 days ago | Handshake completed | 262 ms |
| 10 days ago | Handshake completed | 1.31 s |
| 13 days ago | Handshake completed | 687 ms |
| 15 days ago | Handshake completed | 257 ms |
| 17 days ago | Handshake completed | 294 ms |
| 19 days ago | Handshake completed | 247 ms |
| 21 days ago | Handshake completed | 254 ms |
| 23 days ago | Handshake completed | 292 ms |
| 25 days ago | Handshake completed | 246 ms |
| 27 days ago | Handshake completed | 263 ms |
| 28 days ago | Handshake completed | 248 ms |
| 29 days ago | Handshake completed | 362 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 30 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 com.einvoicewiz/einvoicewiz and makes no claim about it beyond what these checks measured.