Remote MCP · Endpoint

Token Command Center MCP server

No. Token Command Center answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://token-command-center-gamma.vercel.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.ysgjay/token-command-center
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
293 ms
Tools exposed
16 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Free token data: revenue, net flow after emissions, supply/unlock history, catalysts, errors marked
Listing
From the official MCP registry (active).
Recent checks of Token Command Center
CheckedResultHandshake
1 hour agoHandshake completed293 ms
2 days agoHandshake completed93 ms
5 days agoHandshake completed101 ms
7 days agoHandshake completed182 ms
9 days agoHandshake completed71 ms
11 days agoHandshake completed1.71 s
13 days agoHandshake completed112 ms
15 days agoHandshake completed78 ms
17 days agoHandshake completed246 ms
18 days agoHandshake completed81 ms
20 days agoHandshake completed274 ms
21 days agoHandshake completed73 ms
23 days agoHandshake completed52 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.

Listing data comes from the official MCP registry. Glide is not affiliated with Token Command Center and makes no claim about it beyond what these checks measured.