SocialDataX 好看视频 Haokan MCP
REMOTE · MCP.SOCIALDATAX.COM
Haokan video/user search, details, comments/replies, creators, creator videos and hot searches.
Available components
Last scanned (46 minutes ago)
Scores higher than 85% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Search and Retrieval
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 Usability88
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1703 tokens (~106/item across 16 items; 15 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 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.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 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/haokan/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/haokan/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.socialdatax.com/haokan/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 →
haokan_get_comment_replies_by_url ~150
按视频页面链接和一级评论 ID 读取完整回复列表，支持分页；comment_id 取视频评论列表，另一入口使用 haokan_get_comment_replies_by_video_id。
| Name | Type | Req | Description |
|---|---|---|---|
| comment_id | string | yes | 所属一级评论 ID，取视频评论列表中的 comment_id；不要传回复自身的 ID。 |
| page_token | string | – | 分页令牌，首次留空；续页原样传回 next_page_token，保持同一视频和一级评论。 |
| url | string | yes | 好看视频页面链接，格式为 https://haokan.baidu.com/v?vid=数字ID，可取视频搜索结果的 share_url。 |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | 当前页评论回复，保持平台返回顺序。 |
| next_page_token | string | yes | 下一页分页令牌；为空表示没有下一页。 |
| points | object | yes | 本次成功调用的积分消耗与账户积分余额。 |
| reply_count | integer | yes | 平台返回的该一级评论下的回复总数。 |
No examples provided.
haokan_get_comment_replies_by_video_id ~150
按视频 ID和一级评论 ID 读取完整回复列表，支持分页；comment_id 取视频评论列表，另一入口使用 haokan_get_comment_replies_by_url。
| Name | Type | Req | Description |
|---|---|---|---|
| comment_id | string | yes | 所属一级评论 ID，取视频评论列表中的 comment_id；不要传回复自身的 ID。 |
| page_token | string | – | 分页令牌，首次留空；续页原样传回 next_page_token，保持同一视频和一级评论。 |
| video_id | string | yes | 好看视频数字 ID，以字符串传入，例如 6148991337208256393；可从视频搜索结果的 video_id 获取。 |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | 当前页评论回复，保持平台返回顺序。 |
| next_page_token | string | yes | 下一页分页令牌；为空表示没有下一页。 |
| points | object | yes | 本次成功调用的积分消耗与账户积分余额。 |
| reply_count | integer | yes | 平台返回的该一级评论下的回复总数。 |
No examples provided.
haokan_get_hot_search_list ~33
获取好看视频当前搜索热词及热度；不返回热门视频列表，不支持分页。
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | 当前搜索热词，保持平台返回顺序。 |
| points | object | yes | 本次成功调用的积分消耗与账户积分余额。 |
No examples provided.
haokan_get_user_info_by_url ~90
按用户主页链接获取好看视频用户资料；只有用户 ID 时使用 haokan_get_user_info_by_user_id；不返回作品列表。
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | 好看视频用户主页链接，格式为 https://haokan.baidu.com/author/用户ID，可取用户搜索结果的 profile_url，或视频详情、评论作者的 author.profile_url。 |
| Name | Type | Req | Description |
|---|---|---|---|
| avatar_url | – | yes | 用户头像链接；不可用时为 null。 |
| bio | string | yes | 用户简介；不可用时为空字符串。 |
| follower_count | – | yes | 粉丝数量；不可用时为 null。 |
| is_verified | – | yes | 是否已认证；不可用时为 null。 |
| name | string | yes | 用户名称；不可用时为空字符串。 |
| points | object | yes | 本次成功调用的积分消耗与账户积分余额。 |
| posted_video_count | – | yes | 已发布视频数量；不可用时为 null。 |
| profile_url | string | yes | 用户的好看视频主页链接。 |
| user_id | string | yes | 好看视频用户标识，可能包含非数字字符。 |
| verification_label | – | yes | 平台展示的认证说明原文；没有或不可用时为 null。 |
No examples provided.
haokan_get_user_info_by_user_id ~98
按用户 ID 获取好看视频用户资料；ID 可从用户搜索结果获取，持有主页链接时使用 haokan_get_user_info_by_url；不返回作品列表。
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | string | yes | 好看视频用户 ID，可取用户搜索结果的 user_id，或视频详情、评论作者的 author.user_id；支持数字和字母数字标识，不要传空值。 |
| Name | Type | Req | Description |
|---|---|---|---|
| avatar_url | – | yes | 用户头像链接；不可用时为 null。 |
| bio | string | yes | 用户简介；不可用时为空字符串。 |
| follower_count | – | yes | 粉丝数量；不可用时为 null。 |
| is_verified | – | yes | 是否已认证；不可用时为 null。 |
| name | string | yes | 用户名称；不可用时为空字符串。 |
| points | object | yes | 本次成功调用的积分消耗与账户积分余额。 |
| posted_video_count | – | yes | 已发布视频数量；不可用时为 null。 |
| profile_url | string | yes | 用户的好看视频主页链接。 |
| user_id | string | yes | 好看视频用户标识，可能包含非数字字符。 |
| verification_label | – | yes | 平台展示的认证说明原文；没有或不可用时为 null。 |
No examples provided.
haokan_get_user_posted_videos_by_profile_url ~137
按用户主页链接获取好看视频用户发布视频列表，支持分页；不要传视频链接，已有用户 ID 时使用 haokan_get_user_posted_videos_by_user_id。
| Name | Type | Req | Description |
|---|---|---|---|
| page_token | string | – | 分页令牌，首次留空；续页原样传回上一页 next_page_token，且保持同一用户。 |
| profile_url | string | yes | 好看视频用户主页链接，格式为 https://haokan.baidu.com/author/用户ID，可取用户搜索结果的 profile_url，或视频详情、评论作者的 author.profile_url。 |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | 当前页用户发布视频，保持平台返回顺序。 |
| next_page_token | string | yes | 下一页分页令牌；为空表示没有下一页，续页需保持同一用户。 |
| points | object | yes | 本次成功调用的积分消耗与账户积分余额。 |
No examples provided.
haokan_get_user_posted_videos_by_user_id ~132
按用户 ID 获取好看视频用户发布视频列表，支持分页；持有用户主页链接时使用 haokan_get_user_posted_videos_by_profile_url。
| Name | Type | Req | Description |
|---|---|---|---|
| page_token | string | – | 分页令牌，首次留空；续页原样传回上一页 next_page_token，且保持同一用户。 |
| user_id | string | yes | 好看视频用户 ID，可取用户搜索结果的 user_id，或视频详情、评论作者的 author.user_id；支持数字和字母数字标识，不要传空值。 |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | 当前页用户发布视频，保持平台返回顺序。 |
| next_page_token | string | yes | 下一页分页令牌；为空表示没有下一页，续页需保持同一用户。 |
| points | object | yes | 本次成功调用的积分消耗与账户积分余额。 |
No examples provided.
haokan_get_video_comments_by_url ~116
按视频页面链接读取好看视频一级评论，支持分页；附带的回复仅为预览。另一种输入使用 haokan_get_video_comments_by_video_id。
| Name | Type | Req | Description |
|---|---|---|---|
| page_token | string | – | 分页令牌，首次留空；续页原样传回 next_page_token，保持同一视频。 |
| url | string | yes | 好看视频页面链接，格式为 https://haokan.baidu.com/v?vid=数字ID，可取视频搜索结果的 share_url。 |
| Name | Type | Req | Description |
|---|---|---|---|
| comment_count | integer | yes | 平台展示的评论总数，不等于当前页一级评论数量。 |
| items | array | yes | 当前页一级评论，保持平台顺序。 |
| next_page_token | string | yes | 下一页分页令牌；为空表示没有下一页。 |
| points | object | yes | 本次成功调用的积分消耗与账户积分余额。 |
No examples provided.
haokan_get_video_comments_by_video_id ~116
按视频 ID读取好看视频一级评论，支持分页；附带的回复仅为预览。另一种输入使用 haokan_get_video_comments_by_url。
| Name | Type | Req | Description |
|---|---|---|---|
| page_token | string | – | 分页令牌，首次留空；续页原样传回 next_page_token，保持同一视频。 |
| video_id | string | yes | 好看视频数字 ID，以字符串传入，例如 6148991337208256393；可从视频搜索结果的 video_id 获取。 |
| Name | Type | Req | Description |
|---|---|---|---|
| comment_count | integer | yes | 平台展示的评论总数，不等于当前页一级评论数量。 |
| items | array | yes | 当前页一级评论，保持平台顺序。 |
| next_page_token | string | yes | 下一页分页令牌；为空表示没有下一页。 |
| points | object | yes | 本次成功调用的积分消耗与账户积分余额。 |
No examples provided.
haokan_get_video_detail_by_url ~84
按页面链接读取好看视频详情、播放地址和作者摘要；只有视频 ID 时使用 haokan_get_video_detail_by_video_id。播放地址可能过期。
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | 好看视频页面链接，格式为 https://haokan.baidu.com/v?vid=数字ID，可取视频搜索结果的 share_url。 |
| Name | Type | Req | Description |
|---|---|---|---|
| author | object | yes | 作者用户标识、主页链接、名称、头像与粉丝数量。 |
| comment_count | – | yes | 平台返回的评论数量；缺失时为 null。 |
| cover_image_url | – | yes | 视频封面链接；不可用时为 null。 |
| duration_seconds | – | yes | 时长，单位秒；不可用时为 null。 |
| like_count | – | yes | 平台返回的点赞数量；缺失时为 null。 |
| play_url | – | yes | 优先选取平台清晰度等级最高的非空播放地址，无候选时使用默认地址；均缺失时为 null，地址可能过期。 |
| playback_variants | array | yes | 按平台清晰度等级从高到低排列的非空播放地址，包含 quality、label、url；无候选时为空数组，非空时 play_url 等于第一项 url。 |
| points | object | yes | 本次成功调用的积分消耗与账户积分余额。 |
| publish_time | – | yes | 发布时间，Unix 秒级时间戳；不可用时为 null。 |
| share_url | string | yes | 视频页面链接。 |
| title | string | yes | 视频标题。 |
| video_id | string | yes | 好看视频 ID。 |
| view_count | – | yes | 平台返回的播放次数；缺失时为 null。 |
No examples provided.
haokan_get_video_detail_by_video_id ~87
按视频 ID 读取好看视频详情、播放地址和作者摘要；持有页面链接时使用 haokan_get_video_detail_by_url。播放地址可能过期。
| Name | Type | Req | Description |
|---|---|---|---|
| video_id | string | yes | 好看视频数字 ID，以字符串传入，例如 6148991337208256393；可从视频搜索结果的 video_id 获取。 |
| Name | Type | Req | Description |
|---|---|---|---|
| author | object | yes | 作者用户标识、主页链接、名称、头像与粉丝数量。 |
| comment_count | – | yes | 平台返回的评论数量；缺失时为 null。 |
| cover_image_url | – | yes | 视频封面链接；不可用时为 null。 |
| duration_seconds | – | yes | 时长，单位秒；不可用时为 null。 |
| like_count | – | yes | 平台返回的点赞数量；缺失时为 null。 |
| play_url | – | yes | 优先选取平台清晰度等级最高的非空播放地址，无候选时使用默认地址；均缺失时为 null，地址可能过期。 |
| playback_variants | array | yes | 按平台清晰度等级从高到低排列的非空播放地址，包含 quality、label、url；无候选时为空数组，非空时 play_url 等于第一项 url。 |
| points | object | yes | 本次成功调用的积分消耗与账户积分余额。 |
| publish_time | – | yes | 发布时间，Unix 秒级时间戳；不可用时为 null。 |
| share_url | string | yes | 视频页面链接。 |
| title | string | yes | 视频标题。 |
| video_id | string | yes | 好看视频 ID。 |
| view_count | – | yes | 平台返回的播放次数；缺失时为 null。 |
No examples provided.
haokan_search_suggestions ~63
获取好看视频搜索联想词，用于补全或扩展关键词；不返回视频或用户结果，不支持分页。
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | yes | 需要补全或扩展的搜索词；不要传链接或分页令牌。 |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | 按建议顺序排列的搜索联想词。 |
| points | object | yes | 本次成功调用的积分消耗与账户积分余额。 |
No examples provided.
haokan_search_users ~121
按关键词搜索好看视频用户、账号或创作者，返回用户摘要并支持分页；不用于搜索视频。
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | yes | 用户搜索词，例如账号名、创作者名称或品牌名；不要传视频链接、用户主页链接或分页令牌。 |
| page_token | string | – | 分页令牌，首次请求留空；继续翻页时将上一页完整 next_page_token 原样传回，不得修改、截断或自行生成；只能用于相同工具和相同关键词。 |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | 当前页用户搜索结果。 |
| next_page_token | string | yes | 下一页不透明分页令牌；为空表示没有下一页。继续翻页时原样作为 page_token 传回，只能用于相同工具和相同关键词。 |
| points | object | yes | 本次成功调用的积分消耗与账户积分余额。 |
No examples provided.
haokan_search_videos ~125
按关键词搜索好看视频，返回视频摘要并支持分页；用于查找视频，不用于读取指定视频链接的详情或查找用户。
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | yes | 视频搜索词，例如科技、美食或品牌名；不要传视频链接、用户主页链接或分页令牌。 |
| page_token | string | – | 分页令牌，首次请求留空；继续翻页时将上一页完整 next_page_token 原样传回，不得修改、截断或自行生成；只能用于相同工具和相同关键词。 |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | 当前页视频搜索结果，按搜索结果顺序返回。 |
| next_page_token | string | yes | 下一页不透明分页令牌；为空表示没有下一页。继续翻页时原样作为 page_token 传回，只能用于相同工具和相同关键词。 |
| points | object | yes | 本次成功调用的积分消耗与账户积分余额。 |
No examples provided.
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.
How do I install the SocialDataX 好看视频 Haokan MCP server?
SocialDataX 好看视频 Haokan MCP is a hosted endpoint at https://mcp.socialdatax.com/haokan/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-haokan 'https://mcp.socialdatax.com/haokan/mcp'
What is the SocialDataX 好看视频 Haokan MCP server?
SocialDataX 好看视频 Haokan MCP is listed in the public MCP registry as com.socialdatax/haokan. Haokan video/user search, details, comments/replies, creators, creator videos and hot searches. This page covers its hosted endpoint (https://mcp.socialdatax.com/haokan/mcp).
Is the SocialDataX 好看视频 Haokan MCP server safe to use?
SocialDataX 好看视频 Haokan MCP scores 82 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 好看视频 Haokan MCP server expose?
SocialDataX 好看视频 Haokan MCP exposes 15 tools: haokan_get_comment_replies_by_video_id, haokan_get_comment_replies_by_url, haokan_get_video_comments_by_video_id, haokan_get_video_comments_by_url, haokan_search_videos, and 10 more. Their descriptions and schemas cost roughly 1,555 tokens of context every time the server is loaded.
Does the SocialDataX 好看视频 Haokan MCP server require authentication?
Yes. SocialDataX 好看视频 Haokan 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 好看视频 Haokan MCP server still maintained?
SocialDataX 好看视频 Haokan 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.