Tethered Trust MCP

Tethered Trust provides a compatibility intelligence layer for AI agents, allowing them to verify if products fit, plug in, or work together before purchase. It identifies products via URLs or SKUs, extracts specs, and returns structured verdicts with evidence and signed receipts to prevent incompatible purchases.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-18Operated by Tethered Trust

MCP endpoint (Streamable HTTP)

https://tetheredtrust.com/mcp

Vendor documentation

What you can do with it

Identify product specifications from URLs or model numbers
Check compatibility between existing equipment and candidate products
Validate purchase plans for hardware configurations
Generate signed receipts for compatibility decisions

Tools advertised by the last live check:

how_it_works
list_coverage
check_cart_before_checkout
enrich_catalog
identify_product
list_standards
resolve_product
validate_purchase_plan
fix_purchase_plan
plan_upgrade
identify_from_photo
recheck_plan
check_batch
check_compatibility
find_parts
check_fit
verify_receipt
report_outcome

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

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

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add tethered-trust-mcp --url https://tetheredtrust.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable tethered-trust-mcp in your MCP settings.

Cursor configuration

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

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

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

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start tethered-trust-mcp and inspect its tools.

VS Code configuration

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

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http tethered-trust-mcp https://tetheredtrust.com/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

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

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "tethered-trust-mcp": {
      "serverUrl": "https://tetheredtrust.com/mcp"
    }
  }
}

See all 480

Do you run Tethered Trust MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing