Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Labelixa

NPM · LABELIXA-MCP · 2 COMPONENTS · SCANNED SEP 21

Thermal label MCP server: render, validate, debug and convert ZPL, EPL, TSPL and CPCL labels.

+24 this week 84 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 1024 tokens (~93/item across 11 items; 11 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 96% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the Labelixa MCP server?

Labelixa runs locally as an npm package, launched with npx -y labelixa-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · labelixa-mcp

# add to Claude Code
claude mcp add com-labelixa-zpl -- npx -y labelixa-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "com-labelixa-zpl": {
      "command": "npx",
      "args": [
        "-y",
        "labelixa-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-labelixa-zpl": {
      "command": "npx",
      "args": [
        "-y",
        "labelixa-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add com-labelixa-zpl -- npx -y labelixa-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-labelixa-zpl": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "labelixa-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-labelixa-zpl --command npx --arg -y --arg labelixa-mcp
# ~/.hermes/config.yaml
mcp_servers:
  com-labelixa-zpl:
    command: "npx"
    args: ["-y", "labelixa-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-labelixa-zpl": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "labelixa-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add com-labelixa-zpl -t stdio -c npx -a -y labelixa-mcp
// mcp.json
{
  "mcpServers": {
    "com-labelixa-zpl": {
      "command": "npx",
      "args": [
        "-y",
        "labelixa-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +16
    • Tool safety: pass → unverified security
    • Stability: 0.73 → unverified security
    • Malware scan: unverified → pass security
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
    • Package version: 0.3.5 → 0.4.0 functional
  • 16 Sept 26 −10
    • Malware scan: pass → unverified security
    • Source repository: fail → pass security
    • Package version: 0.3.4 → 0.3.5 functional
  • 15 Sept 26 +16
    • Malware scan: unverified → pass security
  • 14 Sept 26 −15
    • Tool safety: pass → unverified security
    • Stability: 0.63 → unverified security
    • Malware scan: pass → unverified security
    • Capabilities: pass → unverified functional
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
    • Package version: 0.3.3 → 0.3.4 functional
  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +16
    • Malware scan: unverified → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Sept 2026 · Analysed npm/labelixa-mcp@0.4.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 96 packages
Packages resolved 96
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 11 exposed · ~1,024 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
barcode_generate ~87

Generate a standalone barcode (SVG text or PNG image). Supported types include code128, code39, ean13, upca, upce, itf14, msi, qrcode, datamatrix, pdf417.

NameTypeReqDescription
datastringyesData to encode
formatstring
typestringyesBarcode type, e.g. code128

No output schema declared.

No examples provided.

convert_zpl_dpi ~113

Rescale ZPL coordinates between printer resolutions (203/300/600 dpi). Embedded ^GF/~DG bitmap data is NOT rescaled — when present, a Warnings block precedes the output instead of silently passing.

NameTypeReqDescription
sourceintegerSource resolution in dpi (152, 203, 300 or 600)
targetintegerTarget resolution in dpi (152, 203, 300 or 600)
zplstringyesRaw ZPL code to convert

No output schema declared.

No examples provided.

cpcl_validate ~46

Lint/validate CPCL label code and return the structured diagnostics report (findings with positions and severity) as JSON.

NameTypeReqDescription
cpclstringyesRaw CPCL code

No output schema declared.

No examples provided.

epl_validate ~50

Lint/validate EPL/EPL2 label code and return the structured diagnostics report (findings with positions and severity) as JSON.

NameTypeReqDescription
eplstringyesRaw EPL/EPL2 code

No output schema declared.

No examples provided.

explain_zpl ~155

Full sectioned health report for a ZPL label (syntax, size/DPI, orientation, barcodes, fonts, memory) with an honest score: only assessable sections count, the rest say 'not assessed'. Pass the real label size — findings depend on it.

NameTypeReqDescription
dpmmintegerPrinter density in dots per mm (6, 8, 12 or 24)
height_innumberLabel height in inches
modelstringOptional printer model as manufacturer/model (e.g. zebra/zd421) to add a model-compatibility section
width_innumberLabel width in inches
zplstringyesRaw ZPL code

No output schema declared.

No examples provided.

language_detect ~68

Detect which printer language raw label code is written in (ZPL, EPL, TSPL or CPCL). Heuristic: returns the language plus a confidence TIER (high/medium/low) and signal codes — not a probability.

NameTypeReqDescription
codestringyesRaw label code to classify

No output schema declared.

No examples provided.

tspl_validate ~54

Lint/validate TSPL/TSPL2 label code and return the structured diagnostics report (findings with positions and severity) as JSON.

NameTypeReqDescription
tsplstringyesRaw TSPL/TSPL2 code

No output schema declared.

No examples provided.

zpl_command_help ~108

Look up one ZPL command in the maintained catalog: name, syntax, parameters (types, ranges, defaults) and whether the preview engine actually renders it — printer-side commands are honestly marked as not rendered.

NameTypeReqDescription
commandstringyesCommand code with or without prefix, e.g. ^PO, BC, ~DG
localestringLanguage for the name and descriptions (default English). Command codes, syntax strings, examples and parameter names are protocol and never change.

No output schema declared.

No examples provided.

zpl_compatibility ~102

Compatibility RISK analysis of ZPL code against a specific printer model, given as manufacturer/model (e.g. 'zebra/zd421'). NOT an emulator and never says 'it works': reports the model's language posture with evidence level, size-rule findings and the scope of our preview.

NameTypeReqDescription
modelstringyesPrinter model as manufacturer/model, e.g. zebra/zd421
zplstringyesRaw ZPL code

No output schema declared.

No examples provided.

zpl_preview ~132

Render ZPL label code to a PNG image via the Labelixa API. This is a SERVER-SIDE render for inspection — it is not a guarantee of how a specific physical printer will output the label.

NameTypeReqDescription
dpmmintegerPrinter density in dots per mm (6, 8, 12 or 24)
height_innumberLabel height in inches
indexintegerWhich label to render when the stream contains several
width_innumberLabel width in inches
zplstringyesRaw ZPL code (^XA ... ^XZ)

No output schema declared.

No examples provided.

zpl_validate ~109

Lint/validate ZPL and return the structured diagnostics report (unknown commands, parameter range errors, layout overflow, etc.) as JSON. Pass the real label size — checks depend on it.

NameTypeReqDescription
dpmmintegerPrinter density in dots per mm (6, 8, 12 or 24)
height_innumberLabel height in inches
width_innumberLabel width in inches
zplstringyesRaw ZPL code

No output schema declared.

No examples provided.

Common questions

What is the Labelixa MCP server?

Labelixa is an MCP server listed in the public MCP registry as com.labelixa/zpl. Thermal label MCP server: render, validate, debug and convert ZPL, EPL, TSPL and CPCL labels. This page covers its npm package (labelixa-mcp).

Is the Labelixa MCP server safe to use?

Labelixa scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Labelixa MCP server expose?

Labelixa exposes 11 tools: zpl_preview, zpl_validate, barcode_generate, language_detect, epl_validate, and 6 more. Their descriptions and schemas cost roughly 1,024 tokens of context every time the server is loaded.

Is the Labelixa MCP server still maintained?

Labelixa is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Labelixa MCP server under?

Labelixa declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.