Remote MCP · Endpoint

RugShield MCP server

Yes, as of 2 hours ago: the server returned an HTTP error.

DownLast checked 2 hours ago

Server URL

https://rugshield-x402.fly.dev/mcp/

The last check failed: the server returned an HTTP error.

Registry name
io.github.raphaelbgr/rugshield
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
5 tools
Uptime, last 30 days
37.5% from 16 checks
Described by its publisher as
Paid Solana transaction safety and token risk checks over x402. No account or API key required.
Listing
From the official MCP registry (active).
Recent checks of RugShield
CheckedResultHandshake
2 hours agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
6 days agoFailed - the server returned an HTTP error—
7 days agoFailed - the server returned an HTTP error—
9 days agoFailed - the server returned an HTTP error—
10 days agoFailed - the server returned an HTTP error—
11 days agoFailed - the server returned an HTTP error—
14 days agoFailed - the server returned an HTTP error—
15 days agoFailed - the server returned an HTTP error—
17 days agoHandshake completed41 ms
19 days agoHandshake completed27 ms
20 days agoHandshake completed33 ms
21 days agoHandshake completed30 ms
22 days agoHandshake completed30 ms
22 days agoHandshake completed62 ms

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

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