Remote MCP · Endpoint

Glyt MCP server

No. Glyt answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://glyt.net/mcp

The last check completed an MCP handshake.

Registry name
net.glyt/glyt
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
372 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Human-in-the-loop approval for agent actions, with verifiable action-bound receipts.
Listing
From the official MCP registry (active).
Recent checks of Glyt
CheckedResultHandshake
1 hour agoHandshake completed372 ms
2 days agoHandshake completed230 ms
4 days agoHandshake completed348 ms
5 days agoHandshake completed221 ms
7 days agoHandshake completed212 ms
8 days agoHandshake completed227 ms
9 days agoHandshake completed222 ms
12 days agoHandshake completed217 ms
13 days agoHandshake completed352 ms
15 days agoHandshake completed239 ms
17 days agoHandshake completed216 ms
18 days agoHandshake completed217 ms
19 days agoHandshake completed214 ms
20 days agoHandshake completed326 ms
21 days agoHandshake completed210 ms
21 days agoHandshake completed216 ms
23 days agoHandshake completed354 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 Glyt and makes no claim about it beyond what these checks measured.