Remote MCP · Endpoint

RugShield — Solana Token Safety Scanner MCP server

No. RugShield — Solana Token Safety Scanner answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://165-227-136-26.sslip.io/shield/mcp

The last check completed an MCP handshake.

Registry name
io.github.zikriz/rugshield
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
304 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Solana token rug-pull detection for AI trading agents. Score, authorities, liquidity.
Listing
From the official MCP registry (active).
Recent checks of RugShield — Solana Token Safety Scanner
CheckedResultHandshake
7 hours agoHandshake completed304 ms
4 days agoHandshake completed316 ms
14 days agoHandshake completed298 ms
15 days agoHandshake completed298 ms
15 days agoHandshake completed308 ms
17 days agoHandshake completed304 ms
18 days agoHandshake completed302 ms
19 days agoHandshake completed297 ms
20 days agoHandshake completed299 ms
21 days agoHandshake completed317 ms
23 days agoHandshake completed292 ms
26 days agoHandshake completed301 ms
28 days agoHandshake completed301 ms

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

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 RugShield — Solana Token Safety Scanner and makes no claim about it beyond what these checks measured.