Remote MCP · Endpoint

Tseha MCP server

No. Tseha answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://tseha.io/mcp

The last check completed an MCP handshake.

Registry name
io.tseha/tseha
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
257 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Serves your design system and coding standards to coding agents, so they stop guessing.
Listing
From the official MCP registry (active).
Recent checks of Tseha
CheckedResultHandshake
9 hours agoHandshake completed257 ms
2 days agoHandshake completed379 ms
4 days agoHandshake completed342 ms
5 days agoHandshake completed180 ms
7 days agoHandshake completed276 ms
8 days agoHandshake completed207 ms
9 days agoHandshake completed274 ms
12 days agoHandshake completed234 ms
13 days agoHandshake completed204 ms
15 days agoHandshake completed530 ms
16 days agoHandshake completed243 ms
17 days agoHandshake completed167 ms
19 days agoHandshake completed172 ms
19 days agoHandshake completed318 ms
20 days agoHandshake completed190 ms
21 days agoHandshake completed297 ms
23 days agoHandshake completed197 ms

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

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