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.

com.yaktool/labels

NPM · YAKTOOL-LABELS-MCP · SCANNED SEP 20

Labels: FBA (FNSKU) & GS1 SSCC pallet labels (PDF/ZPL), plus a ZPL-to-PDF renderer. Exact size.

Available components

+4 this week 75 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 Security100
  • 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
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency19
Schema Quality & AI Usability60
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1332 tokens (~444/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
  • Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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 com.yaktool/labels MCP server?

com.yaktool/labels runs locally as an npm package, launched with npx -y yaktool-labels-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 · yaktool-labels-mcp

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

  • 20 Sept 26 +1

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

  • 18 Sept 26 +1

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

  • 16 Sept 26 +1

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

  • 14 Sept 26 +1

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

  • 11 Sept 26 +1

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

  • 9 Sept 26 +1

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

  • 7 Sept 26 +1

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

  • 5 Sept 26 +1

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

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 20 Sept 2026 · Analysed npm/yaktool-labels-mcp@0.3.1

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 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~1,332 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
generate_fnsku_labels ~509

Lay out FNSKU labels as an exact-physical-size PDF for 30-up US Letter (Avery 5160 geometry), A4 24-up, or 2"×1" / 2.25"×1.25" thermal rolls, and write it to `out`. Code 128 bars are aligned to the target printer dot grid (203/300 dpi) — X-dimension is always a whole number of printer dots, which is what makes the printed label scan reliably. EVERY ROW IS VALIDATED FIRST: not 10 characters, lowercase, punctuation → the row is rejected and reported (LBL-F,* findings), never silently printed; a 12–13 digit input is called out as a UPC/EAN pasted into the wrong column. X00 and B0 (FNSKU=ASIN) prefixes are both accepted — the "always X00" rule of thumb is community consensus, not official grammar, and the tool says so. TITLES ARE PRINTED WITH A STANDARD PDF FONT (WinAnsi): characters outside it (CJK, emoji) are replaced or dropped WITH DISCLOSURE (LBL-T01) — relay that disclosure, never present the label as containing text it does not. THE PDF MUST BE PRINTED AT 100% / "Actual size" — fit-to-page scaling breaks bar widths and the label grid (LBL-P01 is attached to every result; tell the user). Pass `calibrationOnly: true` to get a ruler test page (1" must measure 25.4 mm) instead of labels. startCell (0-based) starts printing at a later position on a partly used 30-up/24-up sheet. Returns { summary{requested,printable,rejected,labels,pages}, items[{input,normalized?,valid,findings[]}], findings[], wrote }.

NameTypeReqDescription
calibrationOnlybooleanWrite the print-calibration test page for `format` instead of labels.
dpinumberTarget printer density for bar alignment (default 300; 203 for common thermal printers).
formatstringyesLabel sheet/roll format.
itemsarrayLabels to generate. Optional only when calibrationOnly is true.
outstringyesAbsolute path of the PDF to write. Never overwrites an existing file.
startCellinteger0-based first cell on page 1, to continue a partly used sheet (sheet formats only).

No output schema declared.

No examples provided.

generate_logistic_labels ~504

Lay out GS1-compliant logistic labels (A6/4"×6" SSCC pallet label, or A5/6"×8" with trade item data) and write them to `out` — as an exact-physical-size PDF, or as ZPL when `out` ends in .zpl (bar-by-bar geometry identical to the PDF; send the file straight to a Zebra-compatible thermal printer). THE LAYOUT AND NUMBERS ARE THE OFFICIAL ONES: three building blocks with the SSCC barcode always lowest, 31.75 mm bars (that is the official bar height — the "32 mm" people remember is a carton placement distance), X-dimension pinned to whole printer dots inside the 0.495–0.940 mm window (4 dots at 203 dpi, 6 at 300 dpi), ≥10X quiet zones, HRI below each symbol with parentheses around AIs. Every rule cites the GS1 General Specifications or the GS1 Logistic Label Guideline (both free official PDFs). VALIDATION IS A GATE, NOT A SUGGESTION: SSCC check digit verified (17 digits auto-complete it, and the result reports the completed SSCC); GTIN (02) and count (37) are only valid together; compact formats print the SSCC only (LGL-010 warning when trade fields are ignored); one symbol carries at most 48 data characters; dates are YYMMDD where day "00" legitimately means end-of-month. Rejected rows are reported with LGL-* findings, never silently printed. X-DIMENSION IS NEVER SHRUNK below the compliant window to squeeze data in — over-long data is an error (LGL-011/012) with a fix suggestion. Returns { summary{requested,printable,rejected,labels}, items[{input,sscc?,valid,findings[]}], findings[], wrote }.

NameTypeReqDescription
dpinumberPrinter density (default 300). Zebra "203/300 dpi" = 8/12 dots per mm.
formatstringyesLabel size. a6/4x6 = SSCC-only compact; a5/6x8 fit trade item data.
itemsarrayyesPallet labels to generate.
outstringyesAbsolute output path — .pdf for print-at-100% PDF, .zpl for raw ZPL. Never overwrites.

No output schema declared.

No examples provided.

render_zpl ~319

Parse ZPL II text, render every ^XA…^XZ label block, and write an exact-physical-size PDF to `out` — proof a label file before it costs a strip of label stock. SUPPORTED SUBSET: label framing (^XA ^XZ ^PW ^LL), positioning (^FO), boxes (^GB), text (^A0/^CF/^FD) and Code 128 barcodes (^BC modes N and A with >; / >8 escapes) — bars are drawn by the same encoder as this suite's generators, cross-checked against two independent barcode libraries. HONEST COVERAGE, NEVER GUESSES: commands outside the subset (other symbologies like ^B3/^BQ/^BX, images ^GF, rotated fields, firmware check-digit modes U/D) are SKIPPED AND LISTED in `coverage.ignored` and ZPV-* findings — a wrongly-guessed barcode is worse than a missing one. Relay the coverage report; never present a partial render as complete. Labels without ^PW/^LL get an inferred canvas (disclosed via ZPV-004). Returns { labels, coverage{rendered,ignored}, findings[], wrote }.

NameTypeReqDescription
dpmmnumberPrinter density the coordinates assume: 8 dots/mm (203 dpi, default) or 12 (300 dpi).
outstringyesAbsolute path of the PDF to write. Never overwrites.
zplstringyesThe ZPL II text (one or more ^XA…^XZ blocks).

No output schema declared.

No examples provided.

Common questions

What is the com.yaktool/labels MCP server?

com.yaktool/labels is an MCP server listed in the public MCP registry as com.yaktool/labels. Labels: FBA (FNSKU) & GS1 SSCC pallet labels (PDF/ZPL), plus a ZPL-to-PDF renderer. Exact size. This page covers its npm package (yaktool-labels-mcp).

Is the com.yaktool/labels MCP server safe to use?

com.yaktool/labels scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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 com.yaktool/labels MCP server expose?

com.yaktool/labels exposes 3 tools: generate_fnsku_labels, generate_logistic_labels, render_zpl. Their descriptions and schemas cost roughly 1,332 tokens of context every time the server is loaded.

Is the com.yaktool/labels MCP server still maintained?

com.yaktool/labels is still listed as active in the MCP registry. We last reached this channel on 20 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 com.yaktool/labels MCP server under?

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