_ registry / mcp streamable-http · checked 1h ago

labelchop-mcp-server

https://labelchop.com

Registry code: b43ee12a15c9e740

api record

AI tools for MyPost A4 labels, 4x6 thermal printers and LabelChop resources.

from a public catalogue that lists it, not from the operator

endpoint
https://labelchop.com/api/mcp
protocol
streamable-http ·2024-11-05
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is labelchop-mcp-server live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is labelchop-mcp-server free to use?
Yes — the hub reached it with no key and no payment.
What tools does labelchop-mcp-server have?
3 tools: diagnose_shipping_label_workflow, recommend_label_printing_setup, find_labelchop_resources.
Is labelchop-mcp-server safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.5%

90 days 99%· all time 99%

latency
427ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 395 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
maps travel & places logistics & shipping
used for
  • diagnose a shipping label printing workflow
  • recommend a thermal label printer setup
  • find guides for printing a4 labels as 4x6
takes → gives
text → text, data
tools
3 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
1 open 2 never probed 1 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • find_labelchop_resources reads open 15h ago

    Find the best LabelChop resource links for A4 shipping labels, 4x6 thermal printing, MyPost Business, Australia Post, eBay, Shopify, Etsy, or label troubleshooting.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "description": "What the user is trying to solve"
    }
  }
}
    arguments 12 lines
  • diagnose_shipping_label_workflow reads unknown never probed

    Diagnose an ecommerce seller shipping-label workflow and recommend whether to use LabelChop or the free A4-to-4x6 converter.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "country": {
      "type": "string",
      "default": "Australia",
      "description": "Seller country, e.g. Australia"
    },
    "printer": {
      "type": "string",
      "description": "Thermal printer model, e.g. Zebra ZD420, Dymo 4XL, Brother QL-1110NWB, Munbyn"
    },
    "problem": {
      "type": "string",
      "description": "The current problem, e.g. labels print too small, A4 labels, barcode will not scan, manual cropping"
    },
    "platform": {
      "type": "string",
      "description": "Shipping or ecommerce platform, e.g. MyPost Business, eBay, Shopify, Etsy, Sendle"
    },
    "volumePerWeek": {
      "type": "number",
      "description": "Approximate number of shipping labels printed per week"
    }
  }
}
    arguments 26 lines
  • recommend_label_printing_setup reads unknown never probed

    Recommend a practical 4x6 thermal-label printing setup for Australian ecommerce sellers.

    mcp-tool

    {
  "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"
    }
  }
}
    arguments 22 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id b43ee12a15c9e740.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b43ee12a15c9e740/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/b43ee12a15c9e740/badge.svg)](https://brick.blue/agent/b43ee12a15c9e740?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.