Skip to content
Chimes In LLC logo

Chimes In LLC MCP server

Which MCP servers are Chimes In LLC's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-27

← Back to Chimes In LLC

Whose server it is
  • Registry namecom.tetheredtrust/tethered-trustverified in the MCP registry

The registry name sits under tetheredtrust.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-27
  • Stateanswerschecked 2026-10-27
  • Tools18
  • Server calls itselftethered-trust
  • Server version0.16.0
  • Protocol version2025-06-18

On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 21 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: check whether a candidate product fits what the customer already owns; validate a full purchase plan for parts and memory slots; verify a checkout cart before the order is placed.
  • Checked on 2 of the 7 days it takes to judge reliability.

Once connected

  • For "check whether a candidate product fits what the customer already owns", the likely first call is check_compatibility.
  • For "validate a full purchase plan for parts and memory slots", the likely first call is validate_purchase_plan.
  • For "verify a checkout cart before the order is placed", the likely first call is check_cart_before_checkout.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 2, the first on 2026-10-27
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
  • What an agent can do with it3 of 3 use cases
  • Answeredmeasuring2 of the 7 daily checks it takes to print a share
  • Median first answer205 ms
  • Space in an agent's context≈ 5,358 tokensthe definitions of all its tools (18), which an agent carries on every turn
  • Tool definitionsA · 96 of 100
  • Typed results18 of 18 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 4 of 18

What an agent can do with it

  • can do · check whether a candidate product fits what the customer already owns
  • can do · validate a full purchase plan for parts and memory slots
  • can do · verify a checkout cart before the order is placed

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers18 tools · read 2026-10-27
  • how_it_works

    What Tethered Trust is, what it covers, where its data comes from, pricing and terms.

  • list_coverage

    Which product categories and models are in the compatibility graph, with counts. Pass a category to list its models. Covers anything that has to fit, plug in, mount, run on or charge with something someone owns. Verified catalog (specs…

  • check_cart_before_checkout

    Checks a cart at checkout. Takes the checkout session exactly as a commerce protocol returns it (a UCP checkout or an ACP CheckoutSession) or plain line items, plus what the customer already owns. Returns a decision per line item…

  • enrich_catalog

    For retailers and marketplaces (API key required): up to 50 products per call (SKU with title, URL or GTIN) in; each product's compatibility attributes out (standards it takes and provides, numeric limits, evidence level, freshness)…

  • identify_product

    Identify a product from a URL, model number, SKU, ASIN, UPC/EAN or description, and get its compatibility profile: the standards it takes and provides (mounts, sockets, connectors, platforms, part numbers, sizes), numeric limits (OS…

  • list_standards

    Every compatibility standard family (with reviewed values), the open formats used for new values, and the numeric limit keys. How Tethered Trust represents physical connections, dimensional fit, vehicles, software and services.

  • resolve_product

    Look up one product in the Tethered Trust graph by name or model number and get its structured specs, what it accepts (mounts, battery platforms, cartridges, protocols) and what it fits. If the text could mean several models, returns them…

  • validate_purchase_plan

    Check a whole purchase before recommending or ordering it: the setup the person owns (with current configuration) plus everything in the cart. Returns one decision (supported / conditional / incompatible / insufficient_evidence), a result…

  • fix_purchase_plan

    When a plan comes back incompatible or conditional: the smallest set of changes that makes it work (swap a part for a verified one that fits everything else, add a missing cooler, hub or adapter, trim quantities that exceed slots)…

  • plan_upgrade

    What can be upgraded on this device and with what: memory (type, slots, maximum), storage (M.2 slots, lengths, PCIe generation), power, CPU and cooling for motherboards, graphics card and cooler clearance for PC cases, plus the parts in…

  • identify_from_photo

    Read the brand, model and part numbers from a photo of a label or nameplate and match them to products. Matches are returned as candidates, with what was read. The photo isn't stored.

  • recheck_plan

    Re-run a saved purchase plan against today's data before ordering, and see what changed since it was issued: decisions, product records, or receipt status.

  • check_batch

    Up to 25 independent compatibility checks in one call (e.g. ranking candidate products for one device). Each result has its own decision, evidence and receipt.

  • check_compatibility

    Will this exact part or accessory work with that exact device? Use before recommending or buying. Covers anything that has to fit, plug in, mount, run on or charge with something someone owns. Verified catalog (specs checked against cited…

  • find_parts

    Which parts and accessories fit this model? OEM parts first, then verified alternatives: e.g. a refrigerator's water filter, a printer's cartridges, a camera's lenses and batteries, a tool's batteries, or the RAM, SSDs and chargers that…

  • check_fit

    Will this appliance physically fit this space? Compares dimensions plus typical installation clearances and required connections (power, water, gas).

  • verify_receipt

    Check a Tethered Trust receipt: is the signature ours, is it still within valid_until, and have the records behind it changed since? A valid receipt proves what we said and when; it doesn't guarantee the verdict was right.

  • report_outcome

    After a purchase, report whether it actually fit. Free, safe to call, and only the first report per check counts. Reports are weighted by level: self_reported (website), agent_reported (anonymous API/MCP), partner_reported (API key…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "tethered-trust": {
      "type": "http",
      "url": "https://tetheredtrust.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http tetheredtrust https://tetheredtrust.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://tetheredtrust.com/mcp as a custom connector in the settings.

OpenAPI spec

37 paths, read 2026-10-27. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.