com.tetheredtrust/builders · v0.60.0 · agents-and-memory
Tethered Trust for builders is healthy: it completed an MCP handshake in 2624 ms and exposes 12 tools.
Launch and keep agent tools working: MCP checks, registry publishing, x402 payment checks.
Endpoint: https://tetheredtrust.com/mcp/builders (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 12 |
| Latency | 2624 ms |
| Last checked (UTC) | 2026-11-09T16:15:46.351Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-11-09T16:15:46.351Z | Healthy | 2624 |
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 so agents can match |
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 to this address; no |
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 sample call on a read-o |
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 and PyPI, plus its s |
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://<domain>/.well-known/mcp-registry-auth; once it's up, call again with publisher_id and we publish |
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 usual cause of 'invalid |
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, robots.txt starts |
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. |