# Tethered Trust for builders (remote · tetheredtrust.com)

Launch and keep agent tools working: MCP checks, registry publishing, x402 payment checks.

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `tetheredtrust.com`: 76/100 (this document), [markdown](https://verifymcp.io/servers/com-tetheredtrust-builders/mcp-builders.md), [page](https://verifymcp.io/servers/com-tetheredtrust-builders/mcp-builders)

## Channel facts

- Endpoint: `https://tetheredtrust.com/mcp/builders`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.65.4`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1974 tokens (~164/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 70% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Tethered Trust for builders MCP server?

Tethered Trust for builders is a hosted endpoint at https://tetheredtrust.com/mcp/builders, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-tetheredtrust-builders 'https://tetheredtrust.com/mcp/builders'
```

### Cursor

```json
{
  "mcpServers": {
    "com-tetheredtrust-builders": {
      "url": "https://tetheredtrust.com/mcp/builders"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-tetheredtrust-builders": {
      "type": "http",
      "url": "https://tetheredtrust.com/mcp/builders"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-tetheredtrust-builders]
url = "https://tetheredtrust.com/mcp/builders"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-tetheredtrust-builders": {
      "type": "remote",
      "url": "https://tetheredtrust.com/mcp/builders",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-tetheredtrust-builders --url 'https://tetheredtrust.com/mcp/builders' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-tetheredtrust-builders:
    url: "https://tetheredtrust.com/mcp/builders"
```

### Netclaw

```json
{
  "McpServers": {
    "com-tetheredtrust-builders": {
      "Transport": "http",
      "Url": "https://tetheredtrust.com/mcp/builders"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-tetheredtrust-builders -t streamable-http -u 'https://tetheredtrust.com/mcp/builders'
```

### Other

```json
{
  "mcpServers": {
    "com-tetheredtrust-builders": {
      "type": "http",
      "url": "https://tetheredtrust.com/mcp/builders"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 76, 0)

- [functional] Server version: 0.65.2 → 0.65.4

### 2026-11-20 (score 76, +1)

- [functional] Server version: 0.65.0 → 0.65.2

### 2026-11-18 (score 75, +1)

- [functional] Server version: 0.64.0 → 0.65.0

### 2026-11-17 (score 74, 0)

- [functional] Server version: 0.63.1 → 0.64.0
- [functional] Server version: 0.62.5 → 0.63.1

### 2026-11-16 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 73, 0)

- [functional] Server version: 0.62.4 → 0.62.5

### 2026-11-14 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 72, 0)

- [functional] Server version: 0.62.3 → 0.62.4

## MCP tools (12)

### `how_it_works` (~31 tokens)

How Tethered Trust works

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

### `enrich_catalog` (~114 tokens)

Enrich a product 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 so agents can match it to what shoppers own.

Input parameters:

- `items` (array, required)
- `research` (boolean): Default true: research up to 10 items per call that aren't in our catalog (from the manufacturer's page).

### `verify_page` (~195 tokens)

Verify a web page works

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 to this address; no script errors; no broken same-site links. Pass / fail / couldn't-verify per check, with a screenshot and a signed receipt. Read-only: no logins, forms or purchases.

Input parameters:

- `checks` (array): What must be true. 'loads' is always included.
- `screenshot` (boolean): Return a screenshot link (default true).
- `url` (string, required): Public https:// page to check, e.g. the page you just built or changed.
- `viewport` (string): Check as a desktop (1280 px) or phone (390 px) browser. Default desktop.

### `verify_mcp` (~167 tokens)

Verify an MCP server works

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 sample call on a read-only tool. Pass / fail / couldn't-verify per check with a signed receipt. Never signs in or calls tools that change things.

Input parameters:

- `call` (object): Optional sample call. Only made if the server marks the tool read-only (annotations.readOnlyHint).
- `expect_tools` (array): Tool names that must be listed.
- `url` (string, required): The MCP server's public https:// endpoint (Streamable HTTP), e.g. https://example.com/mcp.

### `launch_check` (~264 tokens)

Is this MCP server findable?

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 and PyPI, plus its server card, llms.txt and robots.txt (Smithery, PulseMCP, mcp.so and Claude's directory are listed with links to check by hand). Returns a score, what's missing or stale, an ordered fix plan and a ready-to-publish server.json. Read-only.

Input parameters:

- `description` (string): Optional: one-line description for the generated server.json (max 100 characters).
- `name` (string): Optional: the server's display name, to search directories (defaults to the name the server reports).
- `npm` (string): Optional: npm package name to check.
- `pypi` (string): Optional: PyPI project name to check.
- `registry_name` (string): Optional: its official MCP Registry name, e.g. com.example/server.
- `url` (string, required): The MCP server's public https:// endpoint, e.g. https://example.com/mcp.

### `publish_to_registry` (~273 tokens)

Publish an MCP server to the official 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://<domain>/.well-known/mcp-registry-auth; once it's up, call again with publisher_id and we publish server.json under your domain's namespace, then re-publish every new version automatically for 90 days. $5, charged only when we publish. Remove the file to revoke.

Input parameters:

- `description` (string): One line, max 100 characters.
- `domain` (string): Optional: the domain to verify (default: the URL's main domain, e.g. example.com for mcp.example.com). Becomes the namespace (com.example/...).
- `publisher_id` (string): Second call: the publisher_id from the first call, after hosting the proof file.
- `repository` (string)
- `slug` (string): Optional: the part after the slash in the registry name.
- `title` (string)
- `url` (string): The MCP server's public https:// endpoint (Streamable HTTP).
- `version` (string): Optional: version to publish (default: the version your server reports).
- `website` (string)

### `check_payment_setup` (~174 tokens)

Will agents' payments go through?

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 usual cause of 'invalid signature' payments), network id, amount, payTo, timeout, CORS headers for browser agents, resource URL, description and Bazaar discovery. Pass / warn / fail per check with exact fixes. Never pays.

Input parameters:

- `body` (object): Optional example JSON body for POST endpoints.
- `method` (string): HTTP method the endpoint expects (default GET).
- `url` (string, required): The paid endpoint's public https:// URL (an x402 resource).

### `watch_listing` (~184 tokens)

Watch an MCP server's listings daily

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, robots.txt starts blocking. $3 per 30 days; call again with watch_id to renew. Returns today's full launch check.

Input parameters:

- `name` (string)
- `npm` (string)
- `pypi` (string)
- `registry_name` (string)
- `url` (string): The MCP server's public https:// endpoint to watch.
- `watch_id` (string): To renew: an existing watch_id (adds 30 days).
- `webhook` (string): Optional public https:// URL: we POST a signed listing.changed event when something changes.

### `reliability_score` (~90 tokens)

Can agents pay this API?

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.

Input parameters:

- `host` (string): The paid API's host, e.g. api.example.com.
- `url` (string): Or any URL on that host.

### `launch_plan` (~251 tokens)

Keep my MCP server / paid API findable and payable

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.

Input parameters:

- `api_host` (string): Host of your paid x402 API, e.g. api.example.com (we use the endpoints the x402 Bazaar lists for it).
- `description` (string)
- `domain` (string)
- `endpoints` (array): Or name up to 10 paid endpoints yourself.
- `npm` (string)
- `plan_id` (string): To renew: an existing plan_id (adds 30 days to everything).
- `publish` (boolean): Publish to the official MCP Registry (default true).
- `pypi` (string)
- `repository` (string)
- `title` (string)
- `url` (string): Your MCP server's public https:// endpoint (listing watch + registry publishing).
- `webhook` (string): Public https:// URL for signed listing.changed, payment.changed and plan.expiring events.

### `launch_plan_status` (~37 tokens)

Launch Plan status

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

Input parameters:

- `plan_id` (string, required)

### `listing_status` (~48 tokens)

Listing watch status

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

Input parameters:

- `watch_id` (string, required): The watch_id from watch_listing.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-tetheredtrust-builders/mcp-builders#diagnostics

## Score history

- 2026-11-21: 76
- 2026-11-20: 76
- 2026-11-19: 75
- 2026-11-18: 75
- 2026-11-17: 74
- 2026-11-16: 74
- 2026-11-15: 73
- 2026-11-14: 73
- 2026-11-13: 72
- 2026-11-12: 72
- 2026-11-11: 71
- 2026-11-10: 71
- 2026-11-09: 70

## Common questions

### What is the Tethered Trust for builders MCP server?

Tethered Trust for builders is an MCP server listed in the public MCP registry as com.tetheredtrust/builders. Launch and keep agent tools working: MCP checks, registry publishing, x402 payment checks. This page covers its hosted endpoint (https://tetheredtrust.com/mcp/builders).

### Is the Tethered Trust for builders MCP server safe to use?

Tethered Trust for builders scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Tethered Trust for builders MCP server expose?

Tethered Trust for builders exposes 12 tools: how_it_works, enrich_catalog, verify_page, verify_mcp, launch_check, and 7 more. Their descriptions and schemas cost roughly 1,828 tokens of context every time the server is loaded.

### Does the Tethered Trust for builders MCP server require authentication?

No. We connected to Tethered Trust for builders without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Tethered Trust for builders MCP server still maintained?

Tethered Trust for builders is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Tethered Trust for builders MCP server?

VerifyMCP ran 13 checks on Tethered Trust for builders, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://tetheredtrust.com/mcp/builders
- Website: https://tetheredtrust.com/launch
- Changelog RSS feed: https://verifymcp.io/servers/com-tetheredtrust-builders/mcp-builders.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-tetheredtrust-builders/mcp-builders/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-tetheredtrust-builders/mcp-builders.json
- HTML version of this page: https://verifymcp.io/servers/com-tetheredtrust-builders/mcp-builders
