Remote MCP · Endpoint

SocialDataX 微博 Weibo MCP MCP server

No. SocialDataX 微博 Weibo MCP answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://mcp.socialdatax.com/weibo/mcp

The last check completed an MCP handshake.

Registry name
com.52choujiang/weibo-insights
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
963 ms
Tools exposed
22 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Weibo user/post search, suggestions, trends, details, comments, likes/reposts, transcript.
Listing
From the official MCP registry (active).
Recent checks of SocialDataX 微博 Weibo MCP
CheckedResultHandshake
5 hours agoHandshake completed963 ms
9 days agoHandshake completed863 ms
10 days agoHandshake completed961 ms
11 days agoHandshake completed871 ms
12 days agoHandshake completed864 ms
14 days agoHandshake completed905 ms
14 days agoHandshake completed894 ms
15 days agoHandshake completed889 ms
17 days agoHandshake completed873 ms
19 days agoHandshake completed1.04 s
21 days agoHandshake completed883 ms
24 days agoHandshake completed866 ms
26 days agoHandshake completed920 ms
28 days agoHandshake completed942 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 25 responding of 25.

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 微博 Weibo MCP and makes no claim about it beyond what these checks measured.