SocialDataX 今日头条 MCP
REMOTE · MCP.SOCIALDATAX.COM
今日头条热搜、内容关键词搜索、搜索建议、用户搜索、内容详情、一级评论、评论回复、用户资料与用户作品；内容搜索、评论和作品支持分页。
Available components
Last scanned (6 hours ago)
Scores higher than 76% of remote servers
Reachable. Last reached 5 Nov 2026.
Category News and Social
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security71
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- 50% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1597 tokens (~99/item across 16 items; 14 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://mcp.socialdatax.com/toutiao/mcp
TLS valid
Negotiated TLS 1.2 with TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.socialdatax.com | CN=TrustAsia DV TLS RSA CA 2024,O=TrustAsia Technologies\, Inc.,C=CN | 25 Sept 2026 | 24 Dec 2026 | RSA 2048 | SHA256-RSA | 75b0095b0f85e15a5e121c7ea4a0ec94f659cadc |
| SANs: mcp.socialdatax.com | ||||||
| CN=TrustAsia DV TLS RSA CA 2024,O=TrustAsia Technologies\, Inc.,C=CN (CA) | CN=TrustAsia TLS RSA Root CA,O=TrustAsia Technologies\, Inc.,C=CN | 15 May 2024 | 15 May 2034 | RSA 4096 | SHA384-RSA | 1c9e6b412deb0a85461de03dbe30984d0573888b |
| CN=TrustAsia TLS RSA Root CA,O=TrustAsia Technologies\, Inc.,C=CN (CA) | CN=Certum Trusted Network CA,OU=Certum Certification Authority,O=Unizeto Technologies S.A.,C=PL | 7 Oct 2025 | 14 Jan 2029 | RSA 4096 | SHA384-RSA | b2dc4c34932d709cd4bf0b099401695c |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.socialdatax.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| socialdatax.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer error="missing_api_key", error_description="API Key required"
Bearer error="missing_api_key", error_description="API Key required"Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.socialdatax.com/toutiao/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.socialdatax.com/toutiao/mcp | Inconclusive | 404 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
socialdatax_get_points_balance ~53
查询当前 API Key 账户的 SocialDataX 积分余额、剩余积分或点数 / remaining points balance。需要充值时请访问 https://socialdatax.com/dashboard/billing。
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
toutiao_get_hot_search_list ~34
读取今日头条热搜榜，返回头条当前热门关键词及上游热度信息。
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | 普通热搜条目。 |
| pinned_items | array | yes | 平台置顶内容。 |
| points | object | yes | 本次成功调用的积分消耗与账户积分余额。 |
No examples provided.
toutiao_get_post_comment_replies_by_comment_id ~137
读取指定一级评论下的回复，按头条默认顺序分页；comment_id 取一级评论结果，续页保持该 ID，不要改用回复项自身的 ID。
| Name | Type | Req | Description |
|---|---|---|---|
| comment_id | string | yes | 一级评论 ID，取一级评论结果的 comment_id；不要传内容 ID、链接或回复项自身的 comment_id。 |
| page_token | string | – | 首次留空；续页原样传入同一一级评论上一页回复结果的 next_page_token，并保持 comment_id 不变；不要使用一级评论或搜索的分页令牌。 |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | 当前页评论回复列表。 |
| next_page_token | string | yes | 下一页完整分页令牌；为空表示结束。 |
| points | object | yes | 本次成功调用的积分消耗与账户积分余额。 |
No examples provided.
toutiao_get_post_comments_by_post_id ~130
读取头条文章、视频或微头条的一级评论，按头条默认顺序返回，支持分页，不包含评论回复；输入内容数字 ID，支持接续搜索结果；有链接时使用 toutiao_get_post_comments_by_url。
| Name | Type | Req | Description |
|---|---|---|---|
| page_token | string | – | 首次留空；续页原样传入同一内容上一页评论结果的 next_page_token；不要使用搜索结果的分页令牌。 |
| post_id | string | yes | 头条内容数字 ID，可取搜索结果 post_id；不要传链接。 |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | 当前页一级评论列表。 |
| next_page_token | string | yes | 下一页完整分页令牌；为空表示结束。 |
| points | object | yes | 本次成功调用的积分消耗与账户积分余额。 |
No examples provided.
toutiao_get_post_comments_by_url ~151
通过头条内容链接或分享文案读取一级评论，按头条默认顺序返回，支持分页，不包含评论回复；只有内容 ID 时使用 toutiao_get_post_comments_by_post_id。
| Name | Type | Req | Description |
|---|---|---|---|
| page_token | string | – | 首次留空；续页原样传入同一内容上一页评论结果的 next_page_token；不要使用搜索结果的分页令牌。 |
| url | string | yes | 头条内容链接或包含该链接的分享文案，支持 /article/ID/、/aID/、/video/ID/ 和 /w/ID/，可取搜索结果 post_url；不要传纯 ID。 |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | 当前页一级评论列表。 |
| next_page_token | string | yes | 下一页完整分页令牌；为空表示结束。 |
| points | object | yes | 本次成功调用的积分消耗与账户积分余额。 |
No examples provided.
toutiao_get_post_detail_by_post_id ~95
读取头条文章、视频或微头条详情，包含正文、图片、作者和互动数据，视频含播放信息；输入内容数字 ID，可接续搜索结果。有链接时使用 toutiao_get_post_detail_by_url。视频说明不是语音转写。
| Name | Type | Req | Description |
|---|---|---|---|
| post_id | string | yes | 头条内容数字 ID，可取搜索结果 post_id；不要传链接。 |
| Name | Type | Req | Description |
|---|---|---|---|
| author | object | yes | 内容作者，包含作者主页链接。 |
| collect_count | – | yes | 收藏数；未提供时为 null。 |
| comment_count | – | yes | 评论数；未提供时为 null。 |
| content | string | yes | 正文纯文本；纯图片内容或视频可能为空，请结合 images 和 video 阅读。视频说明不是语音转写。 |
| cover_image_url | – | yes | 封面图片链接；未提供时为 null。 |
| images | array | yes | 按正文顺序返回的图片，包含链接和像素宽高；无图片时为空数组。 |
| like_count | – | yes | 点赞数；未提供时为 null。 |
| points | object | yes | 本次成功调用的积分消耗与账户积分余额。 |
| post_id | string | yes | 内容 ID，以字符串表示。 |
| post_url | string | yes | 头条内容页面链接。 |
| publish_time | – | yes | 发布时间，秒级 Unix 时间戳；未提供时为 null。 |
| read_count | – | yes | 阅读数；未提供时为 null。 |
| share_count | – | yes | 分享数；未提供时为 null。 |
| title | string | yes | 内容标题；无独立标题的微头条可为空，请阅读 content。 |
| video | – | – | 视频播放信息；当前返回无视频信息时省略。 |
No examples provided.
toutiao_get_post_detail_by_url ~111
通过头条内容链接或分享文案读取文章、视频或微头条详情；只有内容 ID 时使用 toutiao_get_post_detail_by_post_id。视频说明不是语音转写。
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | 头条内容链接或包含该链接的分享文案，支持 /article/ID/、/aID/、/video/ID/ 和 /w/ID/，可取搜索结果 post_url；不要传纯 ID。 |
| Name | Type | Req | Description |
|---|---|---|---|
| author | object | yes | 内容作者，包含作者主页链接。 |
| collect_count | – | yes | 收藏数；未提供时为 null。 |
| comment_count | – | yes | 评论数；未提供时为 null。 |
| content | string | yes | 正文纯文本；纯图片内容或视频可能为空，请结合 images 和 video 阅读。视频说明不是语音转写。 |
| cover_image_url | – | yes | 封面图片链接；未提供时为 null。 |
| images | array | yes | 按正文顺序返回的图片，包含链接和像素宽高；无图片时为空数组。 |
| like_count | – | yes | 点赞数；未提供时为 null。 |
| points | object | yes | 本次成功调用的积分消耗与账户积分余额。 |
| post_id | string | yes | 内容 ID，以字符串表示。 |
| post_url | string | yes | 头条内容页面链接。 |
| publish_time | – | yes | 发布时间，秒级 Unix 时间戳；未提供时为 null。 |
| read_count | – | yes | 阅读数；未提供时为 null。 |
| share_count | – | yes | 分享数；未提供时为 null。 |
| title | string | yes | 内容标题；无独立标题的微头条可为空，请阅读 content。 |
| video | – | – | 视频播放信息；当前返回无视频信息时省略。 |
No examples provided.
toutiao_get_user_info_by_profile_url ~94
通过用户主页链接或分享文案读取头条用户资料和主页统计，缩略统计为近似值；同时有数字用户 ID 时优先使用 toutiao_get_user_info_by_user_id。
| Name | Type | Req | Description |
|---|---|---|---|
| profile_url | string | yes | 头条用户主页链接或包含主页链接的分享文案，可取详情 author.profile_url；不要传内容链接或纯 ID。 |
| Name | Type | Req | Description |
|---|---|---|---|
| avatar_url | – | yes | 用户头像链接；未提供时为 null。 |
| bio | string | yes | 用户简介；未填写时为空字符串。 |
| follower_count | integer | yes | 粉丝数；头条使用万等缩略显示时为换算的近似值。 |
| following_count | integer | yes | 关注数；头条使用万等缩略显示时为换算的近似值。 |
| ip_location | string | yes | 主页显示的 IP 属地；未提供时为空字符串。 |
| name | string | yes | 用户显示名称。 |
| points | object | yes | 本次成功调用的积分消耗与账户积分余额。 |
| profile_url | string | yes | 用户主页链接，可用于再次查询用户资料。 |
| received_like_count | integer | yes | 累计获赞数；头条使用万等缩略显示时为换算的近似值。 |
| user_id | string | yes | 数字用户 ID，可用于查询用户资料。 |
| verification_label | string | yes | 认证说明；无认证说明时为空字符串。 |
| verified | boolean | yes | 用户是否已认证。 |
No examples provided.
toutiao_get_user_info_by_user_id ~92
读取头条用户资料和主页统计，缩略统计为近似值；已有数字用户 ID 时优先使用本工具，只有主页链接时使用 toutiao_get_user_info_by_profile_url。
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | 头条数字用户 ID，可取搜索或详情的 author.user_id；不要传内容 ID、主页链接或主页标识。 |
| Name | Type | Req | Description |
|---|---|---|---|
| avatar_url | – | yes | 用户头像链接；未提供时为 null。 |
| bio | string | yes | 用户简介；未填写时为空字符串。 |
| follower_count | integer | yes | 粉丝数；头条使用万等缩略显示时为换算的近似值。 |
| following_count | integer | yes | 关注数；头条使用万等缩略显示时为换算的近似值。 |
| ip_location | string | yes | 主页显示的 IP 属地；未提供时为空字符串。 |
| name | string | yes | 用户显示名称。 |
| points | object | yes | 本次成功调用的积分消耗与账户积分余额。 |
| profile_url | string | yes | 用户主页链接，可用于再次查询用户资料。 |
| received_like_count | integer | yes | 累计获赞数；头条使用万等缩略显示时为换算的近似值。 |
| user_id | string | yes | 数字用户 ID，可用于查询用户资料。 |
| verification_label | string | yes | 认证说明；无认证说明时为空字符串。 |
| verified | boolean | yes | 用户是否已认证。 |
No examples provided.
toutiao_get_user_posts_by_profile_url ~125
通过头条用户主页链接读取其发布的作品；支持文章、视频和微头条及分页。
| Name | Type | Req | Description |
|---|---|---|---|
| content_type | string | – | 作品筛选：all、article、video、micro_post。 |
| page_token | string | – | 上一页返回的分页令牌；首次留空，不能跨用户或作品类型复用。 |
| profile_url | string | yes | 头条用户主页链接或包含主页链接的分享文案；只有数字用户 ID 时使用 toutiao_get_user_posts_by_user_id。 |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | 用户发布的作品列表。 |
| next_page_token | string | yes | 下一页分页令牌；为空表示结束。 |
| points | object | yes | 本次成功调用的积分消耗与账户积分余额。 |
No examples provided.
toutiao_get_user_posts_by_user_id ~132
读取头条用户发布的作品；已有数字用户 ID 时使用本工具，有主页链接时使用按主页链接查询的工具。
| Name | Type | Req | Description |
|---|---|---|---|
| content_type | string | – | 作品筛选：all、article、video、micro_post。 |
| page_token | string | – | 上一页返回的分页令牌；首次留空，不能跨用户或作品类型复用。 |
| user_id | string | yes | 头条数字用户 ID，可取用户信息或内容作者的 author.user_id；有主页链接时使用 toutiao_get_user_posts_by_profile_url。 |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | 用户发布的作品列表。 |
| next_page_token | string | yes | 下一页分页令牌；为空表示结束。 |
| points | object | yes | 本次成功调用的积分消耗与账户积分余额。 |
No examples provided.
toutiao_search_posts ~113
按关键词或短语查找今日头条公开内容，支持分页。不用于读取指定链接的详情或查找用户；不返回导航、百科、用户及视频聚合面板。
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | yes | 搜索词或关键词短语，例如 NBA、旅行攻略；不要传作品链接、用户主页链接或内容 ID。 |
| page_token | string | – | 首次留空；续页原样传入上一页的 next_page_token，并保持 keyword 不变。 |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | 当前页内容列表，不包含聚合面板。 |
| next_page_token | string | yes | 下一页完整分页令牌；为空表示结束。 |
| points | object | yes | 本次成功调用的积分消耗与账户积分余额。 |
No examples provided.
toutiao_search_suggestions ~61
获取今日头条搜索输入框的联想词；不返回用户或内容详情，不支持分页。
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | yes | 搜索关键词或短语，例如美食、旅行；不要传链接、用户 ID 或 page_token。 |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | 搜索建议列表；无匹配建议时为空数组。 |
| points | object | yes | 本次成功调用的积分消耗与账户积分余额。 |
No examples provided.
toutiao_search_users ~115
按关键词查找今日头条用户，返回用户 ID、名称、简介、粉丝数和认证说明，支持分页；已有用户 ID 或主页链接时直接查询用户资料。
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | yes | 用户名称或关键词，例如 NBA、美食；不要传内容链接或用户主页链接。 |
| page_token | string | – | 首次留空；续页原样传入同一用户搜索上一页的 next_page_token，并保持 keyword 不变；不能使用内容搜索令牌。 |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | 当前页用户列表。 |
| next_page_token | string | yes | 下一页完整分页令牌；为空表示结束。 |
| points | object | yes | 本次成功调用的积分消耗与账户积分余额。 |
No examples provided.
How do I install the SocialDataX 今日头条 MCP server?
SocialDataX 今日头条 MCP is a hosted endpoint at https://mcp.socialdatax.com/toutiao/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.socialdatax.com
claude mcp add --transport http com-socialdatax-toutiao 'https://mcp.socialdatax.com/toutiao/mcp'
What is the SocialDataX 今日头条 MCP server?
SocialDataX 今日头条 MCP is listed in the public MCP registry as com.socialdatax/toutiao. 今日头条热搜、内容关键词搜索、搜索建议、用户搜索、内容详情、一级评论、评论回复、用户资料与用户作品；内容搜索、评论和作品支持分页。 This page covers its hosted endpoint (https://mcp.socialdatax.com/toutiao/mcp).
Is the SocialDataX 今日头条 MCP server safe to use?
SocialDataX 今日头条 MCP scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the SocialDataX 今日头条 MCP server expose?
SocialDataX 今日头条 MCP exposes 14 tools: toutiao_get_hot_search_list, toutiao_search_suggestions, toutiao_search_users, toutiao_get_user_info_by_user_id, toutiao_get_user_info_by_profile_url, and 9 more. Their descriptions and schemas cost roughly 1,443 tokens of context every time the server is loaded.
Does the SocialDataX 今日头条 MCP server require authentication?
Yes. SocialDataX 今日头条 MCP asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the SocialDataX 今日头条 MCP server still maintained?
SocialDataX 今日头条 MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.