Home / MCP registry index / com.labelixa/zpl
Labelixa
com.labelixa/zpl in the official MCP registry.
Endpoint https://api.labelixa.com/mcp. Source: github.com/Labelixa/labelixa-mcp.
The registry describes it as: Thermal label MCP server: render, validate, debug and convert ZPL, EPL, TSPL and CPCL labels.
We read its 23 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
zpl_preview zpl_validate zpl_command_help barcode_png language_detect epl_validate tspl_validate cpcl_validate explain_zpl convert_zpl_dpi template_list template_get save_label epl_preview tspl_preview cpcl_preview image_to_zpl barcode_verify zpl_compatibility bulk_submit bulk_status bulk_list printer_language_to_zpl
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-labelixa-zpl)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.