Remote MCP · Endpoint

SocialDataX 今日头条 MCP MCP server

No. SocialDataX 今日头条 MCP answered an MCP handshake 49 minutes ago.

UpLast checked 49 minutes ago

Server URL

https://mcp.socialdatax.com/toutiao/mcp

The last check completed an MCP handshake.

Registry name
com.socialdatax/toutiao
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
954 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
今日头条热搜、内容关键词搜索、搜索建议、用户搜索、内容详情、一级评论、评论回复、用户资料与用户作品;内容搜索、评论和作品支持分页。
Listing
From the official MCP registry (active).
Recent checks of SocialDataX 今日头条 MCP
CheckedResultHandshake
49 minutes agoHandshake completed954 ms
10 days agoHandshake completed886 ms
10 days agoHandshake completed872 ms
11 days agoHandshake completed867 ms
12 days agoHandshake completed919 ms
14 days agoHandshake completed895 ms
14 days agoHandshake completed878 ms
15 days agoHandshake completed884 ms
17 days agoHandshake completed880 ms
19 days agoHandshake completed885 ms
21 days agoHandshake completed876 ms
24 days agoHandshake completed870 ms
26 days agoHandshake completed894 ms
28 days agoHandshake completed940 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 今日头条 MCP and makes no claim about it beyond what these checks measured.