Remote MCP · Endpoint

RugShield MCP server

No. RugShield answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://getrugshield.com/mcp/

The last check completed an MCP handshake.

Registry name
io.github.raphaelbgr/rugshield
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
56 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Solana checks and free panel quote via MCP; paid parallel advisor panel via HTTP. USDC x402.
Listing
From the official MCP registry (active).
Recent checks of RugShield
CheckedResultHandshake
5 hours agoHandshake completed56 ms
9 days agoHandshake completed29 ms
10 days agoHandshake completed43 ms
11 days agoHandshake completed46 ms
12 days agoHandshake completed32 ms
14 days agoHandshake completed39 ms
14 days agoHandshake completed42 ms
15 days agoHandshake completed34 ms
17 days agoHandshake completed49 ms
19 days agoHandshake completed28 ms
21 days agoHandshake completed104 ms
24 days agoHandshake completed46 ms
26 days agoHandshake completed44 ms
28 days agoHandshake completed41 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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