Remote MCP · Endpoint

SocialDataX 好看视频 Haokan MCP MCP server

No. SocialDataX 好看视频 Haokan MCP answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://mcp.socialdatax.com/haokan/mcp

The last check completed an MCP handshake.

Registry name
com.socialdatax/haokan
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
951 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Haokan video/user search, details, comments/replies, creators, creator videos and hot searches.
Listing
From the official MCP registry (active).
Recent checks of SocialDataX 好看视频 Haokan MCP
CheckedResultHandshake
43 minutes agoHandshake completed951 ms
9 days agoHandshake completed861 ms
10 days agoHandshake completed904 ms
11 days agoHandshake completed870 ms
12 days agoHandshake completed862 ms
14 days agoHandshake completed883 ms
14 days agoHandshake completed891 ms
15 days agoHandshake completed910 ms
17 days agoHandshake completed873 ms
19 days agoHandshake completed884 ms
21 days agoHandshake completed867 ms
24 days agoHandshake completed859 ms
26 days agoHandshake completed955 ms
28 days agoHandshake completed935 ms

The last 14 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 SocialDataX 好看视频 Haokan MCP and makes no claim about it beyond what these checks measured.