Remote MCP · Endpoint
Labelixa MCP server
No. Labelixa answered an MCP handshake 2 hours ago.
UpLast checked 2 hours ago
Server URL
https://api.labelixa.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.labelixa/zpl
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 232 ms
- Tools exposed
- 23 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Thermal label MCP server: render, validate, debug and convert ZPL, EPL, TSPL and CPCL labels.
- Website
- https://labelixa.com/mcp
- Repository
- https://github.com/Labelixa/labelixa-mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 2 hours ago | Handshake completed | 232 ms |
| 19 hours ago | Handshake completed | 139 ms |
| 2 days ago | Handshake completed | 153 ms |
| 3 days ago | Handshake completed | 181 ms |
| 4 days ago | Handshake completed | 235 ms |
| 5 days ago | Handshake completed | 139 ms |
| 6 days ago | Handshake completed | 166 ms |
| 7 days ago | Handshake completed | 169 ms |
| 10 days ago | Handshake completed | 145 ms |
| 13 days ago | Handshake completed | 159 ms |
| 15 days ago | Handshake completed | 901 ms |
| 17 days ago | Handshake completed | 145 ms |
| 19 days ago | Handshake completed | 121 ms |
| 21 days ago | Handshake completed | 143 ms |
| 23 days ago | Handshake completed | 150 ms |
| 25 days ago | Handshake completed | 133 ms |
| 27 days ago | Handshake completed | 303 ms |
| 28 days ago | Handshake completed | 201 ms |
| 29 days ago | Handshake completed | 436 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 Labelixa and makes no claim about it beyond what these checks measured.