Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Tethered Trust for builders

REMOTE · TETHEREDTRUST.COM

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

+3 this week 76 Trust /100

Last scanned (12 minutes ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category CI/CD and DevOps

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability62
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management40
  • Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 70% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 0
    • Server version: 0.65.2 → 0.65.4 functional
  • 20 Nov 26 +1
    • Server version: 0.65.0 → 0.65.2 functional
  • 18 Nov 26 +1
    • Server version: 0.64.0 → 0.65.0 functional
  • 17 Nov 26 0
    • Server version: 0.63.1 → 0.64.0 functional
    • Server version: 0.62.5 → 0.63.1 functional
  • 16 Nov 26 +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.

  • 15 Nov 26 0
    • Server version: 0.62.4 → 0.62.5 functional
  • 14 Nov 26 +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.

  • 13 Nov 26 0
    • Server version: 0.62.3 → 0.62.4 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://tetheredtrust.com/mcp/builders

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=tetheredtrust.com CN=WE1,O=Google Trust Services,C=US 5 Oct 2026 3 Jan 2027 ECDSA 256 ECDSA-SHA256 e7c82f792058583b1371f731bb2e58d6
SANs: tetheredtrust.com, www.tetheredtrust.com, *.www.tetheredtrust.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of tetheredtrust.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
tetheredtrust.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://tetheredtrust.com/mcp/builders Verified 200
http (plaintext) http://tetheredtrust.com/mcp/builders HTTPS enforced 301 https://tetheredtrust.com/mcp/builders
MCP tools · 12 exposed · ~1,828 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_payment_setup ~174

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.

NameTypeReqDescription
bodyobject–Optional example JSON body for POST endpoints.
methodstring–HTTP method the endpoint expects (default GET).
urlstringyesThe paid endpoint's public https:// URL (an x402 resource).

No output schema declared.

No examples provided.

enrich_catalog ~114

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.

NameTypeReqDescription
itemsarrayyes–
researchboolean–Default true: research up to 10 items per call that aren't in our catalog (from the manufacturer's page).

No output schema declared.

No examples provided.

how_it_works ~31

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

launch_check ~264

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.

NameTypeReqDescription
descriptionstring–Optional: one-line description for the generated server.json (max 100 characters).
namestring–Optional: the server's display name, to search directories (defaults to the name the server reports).
npmstring–Optional: npm package name to check.
pypistring–Optional: PyPI project name to check.
registry_namestring–Optional: its official MCP Registry name, e.g. com.example/server.
urlstringyesThe MCP server's public https:// endpoint, e.g. https://example.com/mcp.

No output schema declared.

No examples provided.

launch_plan ~251

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.

NameTypeReqDescription
api_hoststring–Host of your paid x402 API, e.g. api.example.com (we use the endpoints the x402 Bazaar lists for it).
descriptionstring––
domainstring––
endpointsarray–Or name up to 10 paid endpoints yourself.
npmstring––
plan_idstring–To renew: an existing plan_id (adds 30 days to everything).
publishboolean–Publish to the official MCP Registry (default true).
pypistring––
repositorystring––
titlestring––
urlstring–Your MCP server's public https:// endpoint (listing watch + registry publishing).
webhookstring–Public https:// URL for signed listing.changed, payment.changed and plan.expiring events.

No output schema declared.

No examples provided.

launch_plan_status ~37

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

NameTypeReqDescription
plan_idstringyes–

No output schema declared.

No examples provided.

listing_status ~48

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

NameTypeReqDescription
watch_idstringyesThe watch_id from watch_listing.

No output schema declared.

No examples provided.

publish_to_registry ~273

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.

NameTypeReqDescription
descriptionstring–One line, max 100 characters.
domainstring–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_idstring–Second call: the publisher_id from the first call, after hosting the proof file.
repositorystring––
slugstring–Optional: the part after the slash in the registry name.
titlestring––
urlstring–The MCP server's public https:// endpoint (Streamable HTTP).
versionstring–Optional: version to publish (default: the version your server reports).
websitestring––

No output schema declared.

No examples provided.

reliability_score ~90

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.

NameTypeReqDescription
hoststring–The paid API's host, e.g. api.example.com.
urlstring–Or any URL on that host.

No output schema declared.

No examples provided.

verify_mcp ~167

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.

NameTypeReqDescription
callobject–Optional sample call. Only made if the server marks the tool read-only (annotations.readOnlyHint).
expect_toolsarray–Tool names that must be listed.
urlstringyesThe MCP server's public https:// endpoint (Streamable HTTP), e.g. https://example.com/mcp.

No output schema declared.

No examples provided.

verify_page ~195

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.

NameTypeReqDescription
checksarray–What must be true. 'loads' is always included.
screenshotboolean–Return a screenshot link (default true).
urlstringyesPublic https:// page to check, e.g. the page you just built or changed.
viewportstring–Check as a desktop (1280 px) or phone (390 px) browser. Default desktop.

No output schema declared.

No examples provided.

watch_listing ~184

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.

NameTypeReqDescription
namestring––
npmstring––
pypistring––
registry_namestring––
urlstring–The MCP server's public https:// endpoint to watch.
watch_idstring–To renew: an existing watch_id (adds 30 days).
webhookstring–Optional public https:// URL: we POST a signed listing.changed event when something changes.

No output schema declared.

No examples provided.

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.

remote · tetheredtrust.com

# add to Claude Code
claude mcp add --transport http com-tetheredtrust-builders 'https://tetheredtrust.com/mcp/builders'
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.