Remote MCP · Endpoint

CN HotRank MCP server

No. CN HotRank answered an MCP handshake 13 minutes ago.

UpLast checked 13 minutes ago

Server URL

https://cn-hotrank.7388603.workers.dev/http

The last check completed an MCP handshake.

Registry name
io.github.Aiearn-lab/cn-hotrank
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
277 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Real-time trending from major Chinese platforms (Weibo, Douyin, Baidu, Zhihu).
Listing
From the official MCP registry (active).
Recent checks of CN HotRank
CheckedResultHandshake
13 minutes agoHandshake completed277 ms
10 days agoHandshake completed304 ms
10 days agoHandshake completed606 ms
11 days agoHandshake completed456 ms
13 days agoHandshake completed371 ms
14 days agoHandshake completed828 ms
14 days agoHandshake completed308 ms
15 days agoHandshake completed588 ms
17 days agoHandshake completed319 ms
19 days agoHandshake completed254 ms
21 days agoHandshake completed306 ms
24 days agoHandshake completed276 ms
26 days agoHandshake completed69 ms
28 days agoHandshake completed259 ms

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