Remote MCP · Endpoint

TokenGuard MCP server

No. TokenGuard answered an MCP handshake 19 minutes ago.

UpLast checked 19 minutes ago

Server URL

https://gdzlcxskuhupymyxywzm.supabase.co/functions/v1/tokenguard-mcp?v=2

The last check completed an MCP handshake.

Registry name
io.github.ryosukedesigner-cmd/tokenguard
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.26 s
Tools exposed
4 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Solana rug check before you buy: SAFE/CAUTION/DANGER from chain state. Free key or x402.
Listing
From the official MCP registry (active).
Recent checks of TokenGuard
CheckedResultHandshake
19 minutes agoHandshake completed1.26 s
9 days agoHandshake completed914 ms
9 days agoHandshake completed1.41 s
11 days agoHandshake completed1.09 s
12 days agoHandshake completed1.08 s
13 days agoHandshake completed1.07 s
14 days agoHandshake completed1.01 s
15 days agoHandshake completed1.42 s
16 days agoHandshake completed969 ms
19 days agoHandshake completed1.17 s
21 days agoHandshake completed1.09 s
24 days agoHandshake completed1.28 s

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

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