Tethered Trust for builders

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 网店与支付
• 你需要填写：Authorization

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

claude mcp add --transport http builders https://tetheredtrust.com/mcp/builders --header 'Authorization: your-value'

{
  "mcpServers": {
    "builders": {
      "url": "https://tetheredtrust.com/mcp/builders",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

{
  "servers": {
    "builders": {
      "type": "http",
      "url": "https://tetheredtrust.com/mcp/builders",
      "headers": {
        "Authorization": "your-value"
      }
    }
  }
}

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

• Authorization 机密 HTTP header
  Optional. Bearer tt_... API key with credits; x402 works without one.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月9日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• how_it_works

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

• 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), ready to add to a product feed or UCP catalog

• verify_page

  Call this before you tell someone a web page, site or deploy is done or working, or before relying on another agent's "it's live": we open the public page in a separate browser (desktop or mobile) and check what you list. It loads; this text is visible; this link or button leads

• verify_mcp

  Call this before you recommend, install or rely on an MCP server, after deploying one, or when a connector seems broken: we connect as an MCP client, list its tools, check each has a usable input schema and description, confirm the tools you name exist, and optionally run one sam

• launch_check

  Call this after building or deploying an MCP server or paid agent API, or when its listings may be out of date: we check it works (as verify_mcp does), then look it up in the official MCP Registry (and whether the listed version is current), Glama, PulseMCP, the x402 Bazaar, npm

• publish_to_registry

  Call this to get an MCP server into the official MCP Registry (which Glama, PulseMCP and others import from) without mcp-publisher or DNS: first call with url returns a one-line file to host at https:// /.well-known/mcp-registry-auth; once it's up, call again with publisher_id an

• check_payment_setup

  Call this after building or changing a paid (x402) endpoint, or when agents' payments fail: we call it unpaid like a paying agent, read the 402, and check the payment request parses (v1 or v2), the token's EIP-712 domain (extra.name/version) matches the contract on-chain (the usu

• watch_listing

  Call this after launching an MCP server or paid agent API to keep it findable: we run launch_check today and every day for 30 days, and tell your webhook (signed) when something changes: the server stops answering, the registry listing falls behind a release, a directory drops it

• reliability_score

  Before paying an unfamiliar x402 API, look up its payment-readiness score (0-100) from our daily unpaid checks of the x402 Bazaar: how many of its endpoints would accept an agent's payment, and the common problems. Free.

• launch_plan

  For sellers: 30 days of official MCP Registry publishing on every new version, a daily listing watch (registry, Glama, x402 Bazaar, npm, PyPI, health) and daily payment checks of up to 10 x402 endpoints, with one signed webhook. $12 per 30 days; renew with plan_id.

• launch_plan_status

  Where a Launch Plan stands: listings, registry version and each paid endpoint's payment check. Free.

• listing_status

  Where a watched MCP server stands right now: each directory's status, the latest changes, and when the watch ends. Free.

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月10日

• ! 注意

  作者与仓库一致

  注册中心没有列出源代码仓库，因此无法将发布者（tetheredtrust.com）与代码对应起来

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 482 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 12 个工具描述，未发现针对 AI 的隐藏指令

与“网店与支付”中的其他服务器比较i

• 星标数多于此分类中其他 2625 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 2625 个服务器的 100% 更新
• 基础检查结果等于或优于此分类中其他 2625 个服务器的 53%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

仓库中没有找到 README