Tethered Trust for builders
com.tetheredtrust/buildersVersion 0.62.4Launch and keep agent tools working: MCP checks, registry publishing, x402 payment checks.
Status
Responds594 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:19 UTC
- Latency
- 594 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://tetheredtrust.com/mcp/buildersResponds594 msNo sign-in
Claude Code
claude mcp add --transport http builders https://tetheredtrust.com/mcp/buildersClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: builders
Remote MCP server URL: https://tetheredtrust.com/mcp/buildersCursor
{
"mcpServers": {
"builders": {
"url": "https://tetheredtrust.com/mcp/builders"
}
}
}VS Code
code --add-mcp '{"name":"builders","type":"http","url":"https://tetheredtrust.com/mcp/builders"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
12 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
check_payment_setupCall 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. | No | Yes | No | Yes |
enrich_catalogFor 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. | No | Yes | No | Yes |
how_it_worksWhat Tethered Trust is, what it covers, where its data comes from, pricing and terms. | No | Yes | Yes | No |
launch_checkCall 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. | No | Yes | No | Yes |
launch_planFor 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. | No | No | No | Yes |
launch_plan_statusWhere a Launch Plan stands: listings, registry version and each paid endpoint's payment check. Free. | No | Yes | Yes | No |
listing_statusWhere a watched MCP server stands right now: each directory's status, the latest changes, and when the watch ends. Free. | No | Yes | Yes | No |
publish_to_registryCall 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. | No | No | No | Yes |
reliability_scoreBefore 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. | No | Yes | Yes | No |
verify_mcpCall 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. | No | Yes | No | Yes |
verify_pageCall 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. | No | Yes | No | Yes |
watch_listingCall 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. | No | No | No | Yes |
Details
- Registry status
- Active
- Published
- Nov 13, 2026
- Updated
- Nov 13, 2026
- Repository
- Not given
- Categories (suggested)
- CRMFinance and paymentsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared