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.

io.github.theluckystrike/packing-list

REMOTE · MCP.ZOVO.ONE · 2 COMPONENTS

Packing slips: cartons, contents, weights, chargeable weight and what is still to pack.

−13 this week 81 Trust /100

Last scanned (21 hours ago)

Scores higher than 79% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Documents and Files

Recent critical change

Authorization (17 Nov 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability82
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2324 tokens (~145/item across 16 items; 14 tools + 2 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 Management96
  • Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 0 breaking changes, 1 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 92% 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
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 16 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 17 Nov 26 −13
    • Authorization: pass → fail ▼ critical
    • Stability: pass → fail ▼ security
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 7 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 2 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 26 Oct 26 0
    • Stability: 0.97 → pass security
  • 24 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.

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 Nov 2026 · Probed https://mcp.zovo.one/mcp/packing-slip

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=zovo.one CN=WE1,O=Google Trust Services,C=US 31 Oct 2026 29 Jan 2027 ECDSA 256 ECDSA-SHA256 39e1adfa4eb6500e0e3d48868766e3e9
SANs: zovo.one, mcp.zovo.one, *.mcp.zovo.one
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.zovo.one. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
one. DS published 64939 8 Verified
zovo.one. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=15552000; includeSubDomains; preload
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.zovo.one/mcp/packing-slip Verified 200
http (plaintext) http://mcp.zovo.one/mcp/packing-slip HTTPS enforced 301 https://mcp.zovo.one/mcp/packing-slip
MCP tools · 14 exposed · ~2,091 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
carton_add ~203

Add a carton to a packing list and return its C01-style id: a label, the empty weight in WHOLE GRAMS, and optionally length, width and height in WHOLE CENTIMETRES. Dimensions are what make a chargeable weight possible.

NameTypeReqDescription
height_cminteger–Outer height in whole centimetres
labelstringyesWhat is written on the box, e.g. Box 1 of 3 or Pallet A
length_cminteger–Outer length in whole centimetres. All three dimensions or none
notestring––
packing_liststringyesThe packing list id, e.g. PL-2026-0001, or the order reference when only one list carries it
tare_gramsintegeryesThe EMPTY carton with its packaging, in whole grams. 0 when it is not known
width_cminteger–Outer width in whole centimetres

No output schema declared.

No examples provided.

carton_report ~128

Per carton and for the shipment: tare, net, gross, volume, volumetric weight and the chargeable weight, the greater of gross and volumetric. A carton with no dimensions makes the chargeable total null, never a guess.

NameTypeReqDescription
divisorinteger–Volumetric divisor in cm3 per kg: 5000 courier air (default), 6000 IATA air, 4000 some road tariffs
packing_liststringyesThe packing list id, e.g. PL-2026-0001, or the order reference when only one list carries it

No output schema declared.

No examples provided.

license_activate ~76

Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.

NameTypeReqDescription
keystringyesLicense key from checkout, MCPL1.<payload>.<signature>

No output schema declared.

No examples provided.

license_status ~55

Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pack_item ~223

Put a quantity of one item into a named carton: a description, how many, and the per-unit weight in WHOLE GRAMS. Leave unit_grams out when it was not weighed and the carton gross comes back as a lower bound.

NameTypeReqDescription
cartonstringyesThe carton id, e.g. C01, or its exact label
descriptionstringyesThe goods going in, e.g. Oak shelf 900mm
notestring––
packing_liststringyesThe packing list id, e.g. PL-2026-0001, or the order reference when only one list carries it
quantityintegeryesHow many units go into THIS carton. Split across cartons with one call each
skustring–Stock code, upper-cased and stripped of spaces. Lines with a SKU are matched on it, lines without on their description
unit_gramsinteger–Weight of ONE unit in whole grams. Omit when not weighed; the carton is then a lower bound

No output schema declared.

No examples provided.

packing_expect ~160

Add an ordered line to a packing list so the shortfall is real: a SKU, a description and a quantity. Nothing is read from the quotes, work order or invoice store; what the order says is stated here.

NameTypeReqDescription
descriptionstringyesThe goods as the order names them, e.g. Oak shelf 900mm
packing_liststringyesThe packing list id, e.g. PL-2026-0001, or the order reference when only one list carries it
quantityintegeryesHow many units the order says should ship. Whole units
skustring–Stock code, upper-cased and stripped of spaces. Lines with a SKU are matched on it, lines without on their description

No output schema declared.

No examples provided.

packing_list_create ~227

Open a packing list against an order and return its PL-YYYY-NNNN number: the order reference, the consignee, where it ships to and the date. Free tier: 3 open at once; shipping or cancelling frees a slot.

NameTypeReqDescription
consigneestringyesWho receives the goods, as named on the order
datestring–The day the list was raised, YYYY-MM-DD. Default today
duplicate_okboolean–Open it even though an OPEN list already exists on this reference. Default false
notestring––
referencestringyesThe order this ships against, by id, e.g. WO-2026-0001, INV-2026-0007 or PO-4471
reference_kindstring–What the reference is. Inferred from the id when omitted: WO- work order, INV- invoice, Q- quote, otherwise a plain order
ship_tostring–The delivery address, printed on the slip. Omit to leave it off

No output schema declared.

No examples provided.

packing_list_delete ~108

Delete a packing list for good, with its cartons and packed lines. A shipped list is refused: it is the record of what left the building. Cancel a list you no longer want instead of deleting a real shipment.

NameTypeReqDescription
confirmbooleanyesMust be true. There is no undo and nothing is copied anywhere first
packing_liststringyesThe packing list id, e.g. PL-2026-0001, or the order reference when only one list carries it

No output schema declared.

No examples provided.

packing_list_list ~160

Packing lists newest first, with cartons, units, gross weight and how many ordered lines are still short. Filter by status, by order reference or by consignee. Returns at most 500 rows.

NameTypeReqDescription
consigneestring–Only lists whose consignee contains this text
divisorinteger–Volumetric divisor in cm3 per kg: 5000 courier air (default), 6000 IATA air, 4000 some road tariffs
open_onlyboolean–Only draft and packed lists, the ones that count against the free tier. Default false
referencestring–Only lists against this order reference, matched case-insensitively
statusstring–Only lists in this status

No output schema declared.

No examples provided.

packing_list_show ~126

The whole packing list: its cartons with contents and derived weights, the ordered lines, the shortfall, whether it is ready to ship and why not, and its status history. Nothing here is stored; it is computed.

NameTypeReqDescription
divisorinteger–Volumetric divisor in cm3 per kg: 5000 courier air (default), 6000 IATA air, 4000 some road tariffs
packing_liststringyesThe packing list id, e.g. PL-2026-0001, or the order reference when only one list carries it

No output schema declared.

No examples provided.

packing_list_status ~204

Move a packing list draft to packed to shipped, or cancel it. Shipping records the carrier, the tracking number and the date, and freezes the list. A shipped list cannot be reopened or edited.

NameTypeReqDescription
carrierstring–Who is carrying it, recorded when moving to shipped
datestring–The day the step happened, YYYY-MM-DD. Default today
forceboolean–Ship even though lines are short, over-packed or not on the order. Default false, and the reasons come back either way
notestring––
packing_liststringyesThe packing list id, e.g. PL-2026-0001, or the order reference when only one list carries it
statusstringyesThe status to move to. draft to packed to shipped, or cancelled from either open status
trackingstring–The carrier's consignment or tracking number, recorded when moving to shipped

No output schema declared.

No examples provided.

packing_shortfall ~87

Ordered against packed, line by line: what is still short, what was over-packed, and what was packed that is not on the order at all. A packed line with no ordered line is reported, never dropped.

NameTypeReqDescription
packing_liststringyesThe packing list id, e.g. PL-2026-0001, or the order reference when only one list carries it

No output schema declared.

No examples provided.

packing_slip ~222

The packing slip as plain text on every tier: cartons, contents, weights and a signature line, and no prices anywhere. Pro also gets it back as a .txt download link valid for one hour, named by out_path; an existing name is refused unless told to overwrite.

NameTypeReqDescription
divisorinteger–Volumetric divisor in cm3 per kg: 5000 courier air (default), 6000 IATA air, 4000 some road tariffs
out_pathstring–Name for the downloaded .txt file, e.g. order-4471-slip. Pro only. Omit to get the slip back as text, which every tier can do; the file comes back as a download link valid for one hour
overwriteboolean–Replace out_path if a file is already there. Default false, and an existing file is refused with nothing written
packing_liststringyesThe packing list id, e.g. PL-2026-0001, or the order reference when only one list carries it

No output schema declared.

No examples provided.

unpack_item ~112

Remove one packed line from a packing list by its L01-style id and return the carton it came out of. The line is deleted, not zeroed, so the slip does not print an item nobody packed.

NameTypeReqDescription
linestringyesThe packed line id, e.g. L03, as shown by packing_list_show or carton_report
packing_liststringyesThe packing list id, e.g. PL-2026-0001, or the order reference when only one list carries it

No output schema declared.

No examples provided.

Install

How do I install the io.github.theluckystrike/packing-list MCP server?

io.github.theluckystrike/packing-list is a hosted endpoint at https://mcp.zovo.one/mcp/packing-slip, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.zovo.one

# add to Claude Code
claude mcp add --transport http theluckystrike-packing-list 'https://mcp.zovo.one/mcp/packing-slip'
Common questions

What is the io.github.theluckystrike/packing-list MCP server?

io.github.theluckystrike/packing-list is an MCP server listed in the public MCP registry as io.github.theluckystrike/packing-list. Packing slips: cartons, contents, weights, chargeable weight and what is still to pack. This page covers its hosted endpoint (https://mcp.zovo.one/mcp/packing-slip).

Is the io.github.theluckystrike/packing-list MCP server safe to use?

io.github.theluckystrike/packing-list scores 81 out of 100 on VerifyMCP. 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 io.github.theluckystrike/packing-list MCP server expose?

io.github.theluckystrike/packing-list exposes 14 tools: packing_list_create, packing_expect, carton_add, pack_item, unpack_item, and 9 more. Their descriptions and schemas cost roughly 2,091 tokens of context every time the server is loaded.

Does the io.github.theluckystrike/packing-list MCP server require authentication?

No. We connected to io.github.theluckystrike/packing-list without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.theluckystrike/packing-list MCP server still maintained?

io.github.theluckystrike/packing-list is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.theluckystrike/packing-list MCP server?

VerifyMCP ran 13 checks on io.github.theluckystrike/packing-list, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.