Binary & Thread
NPM · @BINARYANDTHREAD/MCP · SCANNED SEP 26
Browse the Binary & Thread catalogue, stage a cart, get a checkout link. No card data in chat.
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. 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 8 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability55
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (poor).Fail
- Tool/resource definitions use about 1173 tokens (~106/item across 11 items; 10 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- Manipulation check failed: an AI judge found 1 of 11 captured unit(s) of tool text manipulative, the first being "tool: get_product". See how to fix → Fail
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Binary & Thread MCP server?
Binary & Thread runs locally as an npm package, launched with npx -y @binaryandthread/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @binaryandthread/mcp
claude mcp add com-binaryandthread-store -- npx -y @binaryandthread/mcp
{
"mcpServers": {
"com-binaryandthread-store": {
"command": "npx",
"args": [
"-y",
"@binaryandthread/mcp"
]
}
}
} {
"servers": {
"com-binaryandthread-store": {
"command": "npx",
"args": [
"-y",
"@binaryandthread/mcp"
]
}
}
} codex mcp add com-binaryandthread-store -- npx -y @binaryandthread/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-binaryandthread-store": {
"type": "local",
"command": [
"npx",
"-y",
"@binaryandthread/mcp"
],
"enabled": true
}
}
} openclaw mcp add com-binaryandthread-store --command npx --arg -y --arg @binaryandthread/mcp
mcp_servers:
com-binaryandthread-store:
command: "npx"
args: ["-y", "@binaryandthread/mcp"] {
"McpServers": {
"com-binaryandthread-store": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@binaryandthread/mcp"
]
}
}
} assistant mcp add com-binaryandthread-store -t stdio -c npx -a -y @binaryandthread/mcp
{
"mcpServers": {
"com-binaryandthread-store": {
"command": "npx",
"args": [
"-y",
"@binaryandthread/mcp"
]
}
}
} 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.
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 17 Sept 26 60
First indexed and scored.
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 26 Sept 2026 · Analysed npm/@binaryandthread/mcp@0.4.7
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 →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| 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 →
add_to_cart ~339
Add a piece to a cart. Pass cart_id to reuse an existing cart (the durable handle), or omit it to start a fresh one. Call get_product first to get valid sizes/colours (or an exact variant_id); for a design sold in two fits (regular / oversize, priced apart) you MUST pass `fit`. qty is capped at 20. Returns the cart_id and the server-side cart summary (VAT included where applicable). `region` (ISO-2) sets the currency for a NEW cart only — a reused cart keeps its original region.
| Name | Type | Req | Description |
|---|---|---|---|
| cart_id | string | – | reuse this cart; omit to create a new one |
| colour | string | – | piece colour from get_product, e.g. black / white / khaki (khaki: US oversize only; default: the first colour you can buy) |
| fit | string | – | regular or oversize; REQUIRED when the design comes in both (get_product lists them) |
| handle | string | – | product handle (resolves a variant by size + colour; call get_product for valid values) |
| qty | integer | – | quantity, 1–20 (default 1) |
| region | string | – | ISO-2 ship-to country for a NEW cart (e.g. se / us / de); ignored when reusing a cart_id |
| size | string | – | size label from get_product (Regular S / M / L / XL / 2XL; Oversize XS … 3XL) |
| variant_id | string | – | a specific variant id from get_product (overrides handle/size/colour) |
No output schema declared.
No examples provided.
check_payment ~55
Check a checkout's payment status ONCE (call again later to re-check — this never blocks/loops). Returns the status and, once placed, the order_id.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | the session_id from checkout |
No output schema declared.
No examples provided.
checkout ~114
Mint a checkout hand-off for a cart. Returns a checkout_url + a session_id INSTANTLY — it does NOT poll and does NOT complete the purchase. The human must open the link in their own browser to enter their payment + ship-to details on the storefront (those details never enter this chat). After they pay, call check_payment with the session_id to see the status.
| Name | Type | Req | Description |
|---|---|---|---|
| cart_id | string | yes | the cart handle to check out |
| string | – | the buyer's email for the receipt (optional) |
No output schema declared.
No examples provided.
fortune ~45
A coding fortune — a real dev aphorism. Optional seed for a specific one.
| Name | Type | Req | Description |
|---|---|---|---|
| seed | integer | – | pick a specific fortune (0..N); omit for the first |
No output schema declared.
No examples provided.
get_cart ~42
Show a cart's current contents and total (VAT included where applicable), straight from the server.
| Name | Type | Req | Description |
|---|---|---|---|
| cart_id | string | yes | the cart handle from add_to_cart |
No output schema declared.
No examples provided.
get_order_status ~79
Look up an order's status by its display id + the EXACT email on the order. Returns status only (no shipping address). A wrong id/email returns not-found (no enumeration).
| Name | Type | Req | Description |
|---|---|---|---|
| display_id | string | yes | the order's display id (e.g. 1042) |
| string | yes | the exact email on the order |
No output schema declared.
No examples provided.
get_product ~218
Get one piece in full: its readme, the spec sheet (material/weight/fit/print/delivery/care), sizes + price (VAT included where applicable), the lore (the story behind it, with sources), and its image (rendered + the Blob URL as a text floor). Prices are in the region's currency — pass `region` (ISO-2) to price for a market. Designs sold in two fits (regular / oversize) are priced per fit: pass `fit` to narrow, and ALWAYS pass `fit` to add_to_cart for them. // you read the schema. that's the contributor instinct. ask me about the next branch.
| Name | Type | Req | Description |
|---|---|---|---|
| fit | string | – | regular or oversize: narrow sizes, price and image to that fit (omit to see both) |
| handle | string | yes | the product handle/slug (from list_products) |
| region | string | – | ISO-2 ship-to country to price for (e.g. se / us / de); overrides the server default |
No output schema declared.
No examples provided.
list_products ~131
List the pieces in stock (text-only — no images, to keep the agent's context lean). Returns each product's handle, price (VAT included where applicable), and stage. Use get_product for one item's image. Prices are in the region's currency — pass `region` (an ISO-2 country) to price for a specific market, else the server default.
| Name | Type | Req | Description |
|---|---|---|---|
| region | string | – | ISO-2 ship-to country to price for (e.g. se / us / de); overrides the server default |
| stage | string | – | filter by channel stage: 'main' or 'next' |
No output schema declared.
No examples provided.
report_issue ~106
File a bug report or feedback to the maintainers. Pass a short message (and optional structured context like versions/ids). Returns a reference id. It sends no payment details and cannot change any order — it just files the report. Tokens/emails are redacted server-side.
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | – | optional structured context (versions, ids) — tokens/emails are redacted server-side |
| message | string | yes | what went wrong / the feedback (one or two sentences) |
No output schema declared.
No examples provided.
teapot ~25
Returns 418. Always. It's a teapot. (RFC 2324)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the Binary & Thread MCP server?
Binary & Thread is an MCP server listed in the public MCP registry as com.binaryandthread/store. Browse the Binary & Thread catalogue, stage a cart, get a checkout link. No card data in chat. This page covers its npm package (@binaryandthread/mcp).
Is the Binary & Thread MCP server safe to use?
Binary & Thread scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 26 September 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 Binary & Thread MCP server expose?
Binary & Thread exposes 10 tools: list_products, get_product, add_to_cart, get_cart, checkout, and 5 more. Their descriptions and schemas cost roughly 1,154 tokens of context every time the server is loaded.
Is the Binary & Thread MCP server still maintained?
Binary & Thread is still listed as active in the MCP registry. We last reached this channel on 26 September 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 Binary & Thread MCP server under?
Binary & Thread declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.