Remote MCP · Endpoint

Tethered Trust MCP server

No. Tethered Trust answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://tetheredtrust.com/mcp

The last check completed an MCP handshake.

Registry name
com.tetheredtrust/tethered-trust
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
227 ms
Tools exposed
23 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Fit, compatibility and recall checks for AI agents before they buy: verdicts, evidence, receipts.
Listing
From the official MCP registry (active).
Recent checks of Tethered Trust
CheckedResultHandshake
20 minutes agoHandshake completed227 ms
9 days agoHandshake completed114 ms
9 days agoHandshake completed147 ms
11 days agoHandshake completed161 ms
12 days agoHandshake completed258 ms
13 days agoHandshake completed431 ms
14 days agoHandshake completed186 ms
15 days agoHandshake completed118 ms
16 days agoHandshake completed136 ms
19 days agoHandshake completed246 ms
21 days agoHandshake completed179 ms
24 days agoHandshake completed638 ms
26 days agoHandshake completed253 ms
28 days agoHandshake completed320 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

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 and makes no claim about it beyond what these checks measured.