Binary & Thread

com.binaryandthreadPublished by binaryandthread.comv0.4.7Updated Oct 24, 2026

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

The publisher's own server: ThreadPage

VerifiedSTDIODesktop onlyBusiness & Commerce

Overview

AI-generated overview

Lets an assistant browse the Binary & Thread catalogue, stage a shopping cart, and produce a checkout link, without card data in chat.

What you can do
  • Browse the Binary & Thread product catalogue.
  • Stage items in a cart.
  • Get a checkout link to finish the purchase.
When to use it
Useful when you want an assistant to help find Binary & Thread products, assemble a cart, and hand you a link to complete checkout yourself.
Requirements
Runs as a local process over stdio, installed from the npm package @binaryandthread/mcp; desktop only. No authentication, environment variables or headers are declared.
Before you install
It stages carts and produces checkout links, so it affects a real shopping session; the description states no card data is handled in chat, but payment details should still be entered only on the checkout page. No credentials are declared.

Installation

In SourceWeft

  1. Open Binary & Thread in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.4.7LatestSep 17, 2026

Score

15% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Thread integrations