Remote MCP · Endpoint

Tangent MCP server

No. Tangent answered an MCP handshake 17 hours ago.

UpLast checked 17 hours ago

Server URL

https://tangent.directory/api/mcp

The last check completed an MCP handshake.

Registry name
directory.tangent/tangent
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
206 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Hand-picked design references, UI patterns and the people behind them, each with why it fits.
Listing
From the official MCP registry (active).
Recent checks of Tangent
CheckedResultHandshake
17 hours agoHandshake completed206 ms
11 days agoHandshake completed144 ms
11 days agoHandshake completed206 ms
12 days agoHandshake completed216 ms
14 days agoHandshake completed230 ms
15 days agoHandshake completed138 ms
15 days agoHandshake completed166 ms
16 days agoHandshake completed220 ms
18 days agoHandshake completed159 ms
19 days agoHandshake completed147 ms
22 days agoHandshake completed184 ms
25 days agoHandshake completed1.32 s
27 days agoHandshake completed171 ms
29 days agoHandshake completed291 ms

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

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