Binary & Thread vs McpStamp Packing Lists
Binary & Thread is an MCP server published by binaryandthread.com. Marketplaces we read that list it: 1 (Official MCP Registry). McpStamp Packing Lists is an MCP server published by theluckystrike. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Binary & Thread |  McpStamp Packing Lists |
|---|---|---|
| Official MCP Registry | Listed Version: 0.4.7 Downloads/month (npm): 1 207 Downloads/week (npm): 289 Not marked · First seen |
Listed Version: 0.23.0 Forks (GitHub): 3 Stars (GitHub): 2 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Binary & Thread | McpStamp Packing Lists |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 2 |
| Forks (GitHub) (differs) | No figure on GitHub | 3 |
| Last release (differs) | Not published | 2026-11-02 |
| Where it runs (differs) | On your machine (@binaryandthread/mcp) | Remote server or your machine |
| Transport (differs) | stdio | Streamable HTTP, stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/theluckystrike/mcp-servers |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 5 h ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Binary & Thread
Browse the Binary & Thread catalogue, stage a cart, get a checkout link. No card data in chat.
McpStamp Packing Lists
Packing lists for shipments: cartons, weights, shortfalls against the order, packing slips.
How to run each
Binary & Thread As a local MCP server: npm package
claude mcp add --transport stdio store -- npx -y @binaryandthread/mcpMcpStamp Packing Lists As a remote MCP server
claude mcp add --transport http carton-consignment-waybill-pack-list https://mcp.zovo.one/mcp/packing-listRequires: MCP_LICENSE_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only McpStamp Packing Lists has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of Binary & Thread nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
The marketplaces of Binary & Thread publish no settings it asks for, so we do not compare settings.
What it can do: Binary & Thread · What it can do: McpStamp Packing Lists · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.