mcp-registry/io.github.northy9/labelchop-mcp-server · v0.1.2
As of 2026-10-23 22:21 UTC, the Northy9 Labelchop MCP server is up with a Glimind reliability score of 99/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 2 minutes.
AI tools for MyPost A4 labels, 4x6 thermal printers and LabelChop resources.
Claude Code
claude mcp add --transport http northy9-labelchop-mcp-server https://labelchop.com/api/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"northy9-labelchop-mcp-server": {
"type": "http",
"url": "https://labelchop.com/api/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
3 of 3 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Negotiates MCP 2024-11-05. Structured output, tool output schemas and elicitation arrived in 2025-06-18.
Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.northy9%2Flabelchop-mcp-server/fixes
{
"name": "find_labelchop_resources",
"description": "Find the best LabelChop resource links for A4 shipping labels, 4x6 thermal printing, MyPost Business, Australia Post, eBay, Shopify, Etsy, or label troubleshooting.",
"inputSchema": {
"type": "object",
"required": [
"query"
],
"properties": {
"query": {
"type": "string",
"description": "What the user is trying to solve"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "recommend_label_printing_setup",
"description": "Recommend a practical 4x6 thermal-label printing setup for Australian ecommerce sellers.",
"inputSchema": {
"type": "object",
"properties": {
"platform": {
"type": "string",
"description": "Shipping or ecommerce platform"
},
"labelSize": {
"type": "string",
"default": "4x6 / 100x150mm",
"description": "Label stock size"
},
"printerModel": {
"type": "string",
"description": "Thermal printer model"
},
"wantsAutomation": {
"type": "boolean",
"description": "Whether the seller wants automatic printing after downloading labels"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.northy9/labelchop-mcp-server"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.northy9/labelchop-mcp-server"}) over MCP.
diagnose_shipping_label_workflow ~230 tokensrecommend_label_printing_setup ~154 tokensfind_labelchop_resources ~100 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.northy9%2Flabelchop-mcp-server?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.northy9%2Flabelchop-mcp-server?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.northy9%2Flabelchop-mcp-server.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.northy9%2Flabelchop-mcp-server.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.northy9%2Flabelchop-mcp-server?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:7c41c693bd8da88f…, first seen 2026-10-17, included at leaf 6547 of 54,931. Version history · verify what your client received.
Compare: most reliable ecommerce servers · most reliable knowledge servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-23 22:21 UTC, the Northy9 Labelchop MCP server is up with a Glimind reliability score of 99/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 3 outages in 90 days, with a median recovery of 2 minutes.
Northy9 Labelchop MCP server advertises 3 tools, including diagnose_shipping_label_workflow, find_labelchop_resources, recommend_label_printing_setup.
Point your MCP client at this streamable-http endpoint: https://labelchop.com/api/mcp
Glimind scanned all 3 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.