Remote MCP · Endpoint
Tethered Trust for builders MCP server
No. Tethered Trust for builders answered an MCP handshake 7 hours ago.
UpLast checked 7 hours ago
Server URL
https://tetheredtrust.com/mcp/builders
The last check completed an MCP handshake.
- Registry name
- com.tetheredtrust/builders
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 657 ms
- Tools exposed
- 12 tools
- Uptime, last 30 days
- 3 checks from 3 checks
- Described by its publisher as
- Launch and keep agent tools working: MCP checks, registry publishing, x402 payment checks.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 7 hours ago | Handshake completed | 657 ms |
| 4 days ago | Handshake completed | 408 ms |
| 7 days ago | Handshake completed | 130 ms |
The last 3 checks. Full history is kept for 30 days; the all-time counter stands at 3 responding of 3.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with Tethered Trust for builders and makes no claim about it beyond what these checks measured.