LabelChop MCP Server
NPM · LABELCHOP-MCP-SERVER · 2 COMPONENTS
AI tools for MyPost A4 labels, 4x6 thermal printers and LabelChop resources.
Available components
Last scanned (7 hours ago)
Scores higher than 49% of npm servers
Category E-commerce
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 168 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 305 tokens (~101/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 2 Nov 26 +1
- Stability: 0.97 → pass security
- 1 Nov 26 −1
- Stability: pass → 0.97 functional
- 26 Oct 26 +1
- Stability: 0.97 → pass security
- 25 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 19 Oct 26 +1
- Stability: 0.97 → pass security
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 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.
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 5 Nov 2026 · Analysed npm/labelchop-mcp-server@0.1.2
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
diagnose_shipping_label_workflow ~164
Diagnose an ecommerce seller shipping-label workflow and recommend whether to use LabelChop or the free A4-to-4x6 converter.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Seller country, e.g. Australia |
| platform | string | – | Shipping or ecommerce platform, e.g. MyPost Business, eBay, Shopify, Etsy, Sendle |
| printer | string | – | Thermal printer model, e.g. Zebra ZD420, Dymo 4XL, Brother QL-1110NWB, Munbyn |
| problem | string | – | The current problem, e.g. labels print too small, A4 labels, barcode will not scan, manual cropping |
| volumePerWeek | number | – | Approximate number of shipping labels printed per week |
No output schema declared.
No examples provided.
find_labelchop_resources ~64
Find the best LabelChop resource links for A4 shipping labels, 4x6 thermal printing, MyPost Business, Australia Post, eBay, Shopify, Etsy, or label troubleshooting.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | What the user is trying to solve |
No output schema declared.
No examples provided.
recommend_label_printing_setup ~77
Recommend a practical 4x6 thermal-label printing setup for Australian ecommerce sellers.
| Name | Type | Req | Description |
|---|---|---|---|
| labelSize | string | – | Label stock size |
| platform | string | – | Shipping or ecommerce platform |
| printerModel | string | – | Thermal printer model |
| wantsAutomation | boolean | – | Whether the seller wants automatic printing after downloading labels |
No output schema declared.
No examples provided.
How do I install the LabelChop MCP Server server?
LabelChop MCP Server runs locally as an npm package, launched with npx -y labelchop-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · labelchop-mcp-server
claude mcp add northy9-labelchop-mcp-server -- npx -y labelchop-mcp-server
What is the LabelChop MCP Server server?
LabelChop MCP Server is listed in the public MCP registry as io.github.Northy9/labelchop-mcp-server. AI tools for MyPost A4 labels, 4x6 thermal printers and LabelChop resources. This page covers its npm package (labelchop-mcp-server).
Is the LabelChop MCP Server server safe to use?
LabelChop MCP Server scores 74 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 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 LabelChop MCP Server server expose?
LabelChop MCP Server exposes 3 tools: diagnose_shipping_label_workflow, recommend_label_printing_setup, find_labelchop_resources. Their descriptions and schemas cost roughly 305 tokens of context every time the server is loaded.
Is the LabelChop MCP Server server still maintained?
LabelChop MCP Server is still listed as active in the MCP registry. We last reached this channel on 5 November 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 LabelChop MCP Server server under?
LabelChop MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the LabelChop MCP Server server?
VerifyMCP ran 15 checks on LabelChop MCP Server, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about LabelChop MCP Server: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.