Binary & Thread MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Binary and Thread product browsing and checkout handoff: Does the purchase boundary still prevent an agent from entering card data or completing checkout?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Browse products, stage a cart and hand off checkout without exposing payment card data to the agent.

What we know

Small deterministic store MCP for catalog browsing, cart creation and checkout-link generation. The agent cannot complete purchase or set shipping address; card entry stays in the user's browser on Stripe.

Maintenance / activity evidence

@binaryandthread/mcp 0.4.12 published 2026-10-04T17:35:24.100Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Catalog/cart/checkout-session authority only; no admin/shell/payment-card access. Writes: Create/reuse cart; Mint checkout session; Report issue.
Optional customer JWT.
Sensitive access: Cart contents, Order-status email/display ID, Optional customer token

Checkout handoff is intentionally bounded; agent cannot complete payment or set shipping address.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Does the purchase boundary still prevent an agent from entering card data or completing checkout?

The bounded review of the publisher's documented Binary and Thread product browsing and checkout handoff and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Checkout handoff is intentionally bounded; agent cannot complete payment or set shipping address.
Catalog/cart/checkout-session authority only; no admin/shell/payment-card access.
Optional customer JWT.
Cart/order queries hit store API; payment card/shipping entry remains in external browser checkout.
Reviewed write actions: Create/reuse cart; Mint checkout session; Report issue
Sensitive access: Cart contents, Order-status email/display ID, Optional customer token
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
The agent can stage a cart and initiate checkout but cannot finalize payment/address.
Order status requires display ID plus exact email.
Checkout still creates a real payment session, so product/amount should be reviewed.

Original activity observations

@binaryandthread/mcp 0.4.12 published 2026-10-04T17:35:24.100Z

Technical identity

npm/@binaryandthread/mcp

Exact implementation source: https://www.npmjs.com/package/@binaryandthread/mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:@binaryandthread/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
@binaryandthread/mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Runs over stdio; Stripe checkout is opened for the user to complete in their browser, not by the agent. Optional BT_TOKEN is a customer JWT, BT_PUBLISHABLE_KEY is public; never supply a secret Stripe key.
publisher install or stdio launch · Publisher instructions
npx -y @binaryandthread/mcp
Configure / authenticate
MCP100 setup guide
Run local stdio via `npx -y @binaryandthread/mcp` and register that command in an MCP client. Customer token `BT_TOKEN` is optional; do not confuse public BT_PUBLISHABLE_KEY with Stripe secret keys.
Check connection
Suggested check
Discover `list_products` and inspect a product; do not use checkout or purchase as connection test.
Remove / uninstall / revoke
MCP100 setup guide
For a Claude Code registration named `binaryandthread-mcp`, run `claude mcp remove binaryandthread-mcp`; otherwise remove the exact entry in the chosen MCP client settings and restart/reconnect. This client-host removal command is MCP100-composed from Claude Code lifecycle documentation, not a vendor-authored uninstall. With `npx`, a separate global package uninstall normally is unnecessary. Do not delete provider data or credentials by default.
Client unregister, package uninstall, data deletion, and OAuth/API token/wallet permissions are distinct.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove binaryandthread-mcp

Official Documentation & Sources

What it does

Small deterministic store MCP for catalog browsing, cart creation and checkout-link generation. The agent cannot complete purchase or set shipping address; card entry stays in the user's browser on Stripe.

Capability: Productivity & Collaboration
Resource type: MCP Server
Industry: Retail & E-commerce
Best fit: Browse products, stage a cart and hand off checkout without exposing payment card data to the agent.

Representative uses

Browse catalog/product specs
Add products to cart
Get authoritative cart total
Mint checkout URL
Check payment/order status

Limitations

The agent can stage a cart and initiate checkout but cannot finalize payment/address.
Order status requires display ID plus exact email.
Checkout still creates a real payment session, so product/amount should be reviewed.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Optional customer JWT.
Permissions: Catalog/cart/checkout-session authority only; no admin/shell/payment-card access.
Data handling: Cart/order queries hit store API; payment card/shipping entry remains in external browser checkout.
Cost: retail_purchase
Risk and cautions: Checkout handoff is intentionally bounded; agent cannot complete payment or set shipping address.

Access scope and cautions

Write actions: Create/reuse cart Mint checkout session Report issue
Sensitive access: Cart contents Order-status email/display ID Optional customer token
Risk level: moderate

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Browse catalog/product specs; Add products to cart; Get authoritative cart total; Mint checkout URL; Check payment/order status.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @binaryandthread/mcp. Recorded transport: stdio. Recorded environment-variable notes: BT_STORE_URL (optional); BT_PUBLISHABLE_KEY (optional/public); BT_REGION (optional); BT_TOKEN (optional customer JWT). No configuration values are supplied here. Prerequisites: MCP client. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Zero-config public storefront; optional customer JWT for own-scope functions.

Can it modify data or perform write operations?

Documented write actions include: Create/reuse cart; Mint checkout session; Report issue. Recorded permission boundary: Catalog/cart/checkout-session authority only; no admin/shell/payment-card access.

What data-handling boundary should I consider?

Cart/order queries hit store API; payment card/shipping entry remains in external browser checkout. Recorded sensitive-access context: Cart contents; Order-status email/display ID; Optional customer token.

What limitations and risks should I check before use?

Checkout handoff is intentionally bounded; agent cannot complete payment or set shipping address. The agent can stage a cart and initiate checkout but cannot finalize payment/address. Order status requires display ID plus exact email. Checkout still creates a real payment session, so product/amount should be reviewed. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

What cost model is recorded?

The reviewed cost model is retail purchase. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.