Remote MCP · Endpoint

TokenLab MCP Server MCP server

No. TokenLab MCP Server answered an MCP handshake 4 hours ago.

UpLast checked 4 hours ago

Server URL

https://mcp.tokenlab.sh/mcp

The last check completed an MCP handshake.

Registry name
io.github.hedging8563/tokenlab
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
185 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
TokenLab MCP server: 32 default and 89 full-profile tools for models, media, tasks, and files.
Listing
From the official MCP registry (active).
Recent checks of TokenLab MCP Server
CheckedResultHandshake
4 hours agoHandshake completed185 ms
10 days agoHandshake completed984 ms
11 days agoHandshake completed1.12 s
11 days agoHandshake completed1.04 s
13 days agoHandshake completed109 ms
14 days agoHandshake completed90 ms
15 days agoHandshake completed827 ms
16 days agoHandshake completed953 ms
17 days agoHandshake completed1.05 s
19 days agoHandshake completed125 ms
22 days agoHandshake completed169 ms
24 days agoHandshake completed1.02 s
26 days agoHandshake completed1.22 s
29 days agoHandshake completed139 ms

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

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