Remote MCP · Endpoint

Degenscan Intel MCP server

No. Degenscan Intel answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://degenscan-intel.onrender.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.tradewr333-lgtm/degenscan-intel
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
102 ms
Tools exposed
39 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Cross-asset market event intelligence for AI trading agents. Pay per call (USDC/x402) or API key.
Listing
From the official MCP registry (active).
Recent checks of Degenscan Intel
CheckedResultHandshake
1 hour agoHandshake completed102 ms
2 days agoHandshake completed99 ms
4 days agoHandshake completed91 ms
6 days agoHandshake completed107 ms
8 days agoHandshake completed111 ms
10 days agoHandshake completed95 ms
12 days agoHandshake completed89 ms
13 days agoHandshake completed105 ms
14 days agoHandshake completed65 ms
15 days agoHandshake completed59 ms
18 days agoHandshake completed120 ms
19 days agoHandshake completed103 ms
21 days agoHandshake completed71 ms
23 days agoHandshake completed115 ms
24 days agoHandshake completed85 ms

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