Remote MCP · Endpoint

Tangent MCP server

No. Tangent answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
147 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Hand-picked design references, UI patterns and the people behind them, each with why it fits.
Website
https://tangent.directory/mcp
Listing
From the official MCP registry (active).
Recent checks of Tangent
CheckedResultHandshake
1 hour agoHandshake completed147 ms
2 days agoHandshake completed184 ms
5 days agoHandshake completed1.32 s
7 days agoHandshake completed171 ms
9 days agoHandshake completed291 ms
11 days agoHandshake completed530 ms
13 days agoHandshake completed134 ms
15 days agoHandshake completed493 ms
17 days agoHandshake completed133 ms
19 days agoHandshake completed1.35 s
20 days agoHandshake completed209 ms
21 days agoHandshake completed1.29 s
22 days agoHandshake completed643 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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.