Remote MCP · Endpoint

RugShield 402 MCP server

No. RugShield 402 answered an MCP handshake 14 minutes ago.

UpLast checked 14 minutes ago

Server URL

https://rugshield-402.onrender.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.ak10082247-max/rugshield-402
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
266 ms
Tools exposed
14 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Real-time token contract safety scanner and honeypot auditor via x402 on Base.
Listing
From the official MCP registry (active).
Recent checks of RugShield 402
CheckedResultHandshake
14 minutes agoHandshake completed266 ms
9 days agoHandshake completed284 ms
9 days agoHandshake completed293 ms
11 days agoHandshake completed158 ms
12 days agoHandshake completed268 ms
13 days agoHandshake completed136 ms
14 days agoHandshake completed403 ms
14 days agoHandshake completed130 ms
16 days agoHandshake completed138 ms
19 days agoHandshake completed155 ms
21 days agoFailed - the server returned an HTTP error—
24 days agoHandshake completed139 ms
26 days agoHandshake completed144 ms
28 days agoHandshake completed314 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 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 402 and makes no claim about it beyond what these checks measured.