Remote MCP · Endpoint
StealthGuard 402 MCP server
Yes, as of 14 minutes ago: the server returned an HTTP error.
DownLast checked 14 minutes ago
Server URL
https://stealthguard-402.onrender.com/mcp
The last check failed: the server returned an HTTP error.
- Registry name
- io.github.ak10082247-max/stealthguard-402
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 15 tools
- Uptime, last 30 days
- 71.4% from 14 checks
- Described by its publisher as
- Stealth web extraction, Polymarket alpha, and on-chain pre-trade gating via x402 on Base.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 14 minutes ago | Failed - the server returned an HTTP error | — |
| 9 days ago | Failed - the server returned an HTTP error | — |
| 9 days ago | Failed - the server returned an HTTP error | — |
| 11 days ago | Handshake completed | 300 ms |
| 12 days ago | Handshake completed | 299 ms |
| 13 days ago | Handshake completed | 133 ms |
| 14 days ago | Handshake completed | 203 ms |
| 14 days ago | Handshake completed | 288 ms |
| 16 days ago | Handshake completed | 138 ms |
| 19 days ago | Handshake completed | 318 ms |
| 21 days ago | Failed - the server returned an HTTP error | — |
| 24 days ago | Handshake completed | 140 ms |
| 26 days ago | Handshake completed | 150 ms |
| 28 days ago | Handshake completed | 340 ms |
The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 11 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 StealthGuard 402 and makes no claim about it beyond what these checks measured.