Remote MCP · Endpoint

Labelixa MCP server

No. Labelixa answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
143 ms
Tools exposed
21 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Thermal label MCP server: render, validate, debug and convert ZPL, EPL, TSPL and CPCL labels.
Listing
From the official MCP registry (active).
Recent checks of Labelixa
CheckedResultHandshake
1 hour agoHandshake completed143 ms
2 days agoHandshake completed150 ms
4 days agoHandshake completed133 ms
5 days agoHandshake completed303 ms
7 days agoHandshake completed201 ms
8 days agoHandshake completed436 ms
9 days agoHandshake completed156 ms
12 days agoHandshake completed141 ms
13 days agoHandshake completed213 ms
15 days agoHandshake completed154 ms
16 days agoHandshake completed137 ms
17 days agoHandshake completed116 ms
18 days agoHandshake completed146 ms
19 days agoHandshake completed136 ms
20 days agoHandshake completed129 ms
21 days agoHandshake completed128 ms
22 days agoHandshake completed145 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

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.