# Binary & Thread (npm · @binaryandthread/mcp)

Browse the Binary & Thread catalogue, stage a cart, get a checkout link. No card data in chat.

- Trust score: 64/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-26

## Components

- npm · `@binaryandthread/mcp`: 64/100 (this document), [markdown](https://verifymcp.io/servers/com-binaryandthread-store/binaryandthread-mcp.md), [page](https://verifymcp.io/servers/com-binaryandthread-store/binaryandthread-mcp)

## Channel facts

- Registry: `npm`
- Package: `@binaryandthread/mcp`
- Version: `0.4.7`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-26.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 8 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 55/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (poor).
  - Tool/resource definitions use about 1173 tokens (~106/item across 11 items; 10 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - Manipulation check failed: an AI judge found 1 of 11 captured unit(s) of tool text manipulative, the first being "tool: get_product".
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add com-binaryandthread-store -- npx -y @binaryandthread/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-binaryandthread-store": {
      "command": "npx",
      "args": [
        "-y",
        "@binaryandthread/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-binaryandthread-store": {
      "command": "npx",
      "args": [
        "-y",
        "@binaryandthread/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-binaryandthread-store -- npx -y @binaryandthread/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-binaryandthread-store": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@binaryandthread/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-binaryandthread-store --command npx --arg -y --arg @binaryandthread/mcp
```

### Hermes

```yaml
mcp_servers:
  com-binaryandthread-store:
    command: "npx"
    args: ["-y", "@binaryandthread/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-binaryandthread-store": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@binaryandthread/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-binaryandthread-store -t stdio -c npx -a -y @binaryandthread/mcp
```

### Other

```json
{
  "mcpServers": {
    "com-binaryandthread-store": {
      "command": "npx",
      "args": [
        "-y",
        "@binaryandthread/mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-26 (score 64, +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.

### 2026-09-25 (score 63, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-17 (score 60)

First indexed and scored.

## MCP tools (10)

### `list_products` (~131 tokens)

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.

Input parameters:

- `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'

### `get_product` (~218 tokens)

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.

Input parameters:

- `fit` (string): regular or oversize: narrow sizes, price and image to that fit (omit to see both)
- `handle` (string, required): 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

### `add_to_cart` (~339 tokens)

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.

Input parameters:

- `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)

### `get_cart` (~42 tokens)

Show a cart's current contents and total (VAT included where applicable), straight from the server.

Input parameters:

- `cart_id` (string, required): the cart handle from add_to_cart

### `checkout` (~114 tokens)

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.

Input parameters:

- `cart_id` (string, required): the cart handle to check out
- `email` (string): the buyer's email for the receipt (optional)

### `check_payment` (~55 tokens)

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.

Input parameters:

- `session_id` (string, required): the session_id from checkout

### `get_order_status` (~79 tokens)

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).

Input parameters:

- `display_id` (string, required): the order's display id (e.g. 1042)
- `email` (string, required): the exact email on the order

### `report_issue` (~106 tokens)

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.

Input parameters:

- `context` (object): optional structured context (versions, ids) — tokens/emails are redacted server-side
- `message` (string, required): what went wrong / the feedback (one or two sentences)

### `teapot` (~25 tokens)

Returns 418. Always. It's a teapot. (RFC 2324)

### `fortune` (~45 tokens)

A coding fortune — a real dev aphorism. Optional seed for a specific one.

Input parameters:

- `seed` (integer): pick a specific fortune (0..N); omit for the first

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-binaryandthread-store/binaryandthread-mcp#diagnostics

## Score history

- 2026-09-26: 64
- 2026-09-25: 63
- 2026-09-24: 60
- 2026-09-23: 60
- 2026-09-22: 60
- 2026-09-21: 60
- 2026-09-20: 60
- 2026-09-19: 60
- 2026-09-18: 60
- 2026-09-17: 60

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@binaryandthread/mcp
- Socket report: https://socket.dev/npm/package/@binaryandthread/mcp
- Website: https://binaryandthread.com/docs
- Changelog RSS feed: https://verifymcp.io/servers/com-binaryandthread-store/binaryandthread-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-binaryandthread-store/binaryandthread-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-binaryandthread-store/binaryandthread-mcp