SocialDataX 知乎 Zhihu MCP
REMOTE · MCP.SOCIALDATAX.COM · SCANNED SEP 21
Zhihu/知乎 hot list, search/details, comments/replies, creators/articles, and video transcripts.
Available components
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 405, 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 Usability81
- 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 2497 tokens (~192/item across 13 items; 11 tools + 2 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 Management93
- Stability observed for 28 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 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
How do I install the SocialDataX 知乎 Zhihu MCP server?
SocialDataX 知乎 Zhihu MCP is a hosted endpoint at https://mcp.socialdatax.com/zhihu/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-52choujiang-zhihu-insights 'https://mcp.socialdatax.com/zhihu/mcp'
{
"mcpServers": {
"com-52choujiang-zhihu-insights": {
"url": "https://mcp.socialdatax.com/zhihu/mcp"
}
}
} {
"servers": {
"com-52choujiang-zhihu-insights": {
"type": "http",
"url": "https://mcp.socialdatax.com/zhihu/mcp"
}
}
} [mcp_servers.com-52choujiang-zhihu-insights] url = "https://mcp.socialdatax.com/zhihu/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-52choujiang-zhihu-insights": {
"type": "remote",
"url": "https://mcp.socialdatax.com/zhihu/mcp",
"enabled": true
}
}
} openclaw mcp add com-52choujiang-zhihu-insights --url 'https://mcp.socialdatax.com/zhihu/mcp' --transport streamable-http
mcp_servers:
com-52choujiang-zhihu-insights:
url: "https://mcp.socialdatax.com/zhihu/mcp" {
"McpServers": {
"com-52choujiang-zhihu-insights": {
"Transport": "http",
"Url": "https://mcp.socialdatax.com/zhihu/mcp"
}
}
} assistant mcp add com-52choujiang-zhihu-insights -t streamable-http -u 'https://mcp.socialdatax.com/zhihu/mcp'
{
"mcpServers": {
"com-52choujiang-zhihu-insights": {
"type": "http",
"url": "https://mcp.socialdatax.com/zhihu/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “socialdatax_get_points_balance” rewrote its description, which is the text the model reads security
- 13 Sept 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.
- 11 Sept 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.
- 9 Sept 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. Other categories moved too: Schema Quality & AI Usability rose 1.
- 7 Sept 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.
- 5 Sept 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.
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 21 Sept 2026 · Probed https://mcp.socialdatax.com/zhihu/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 | 30 Jun 2026 | 28 Sept 2026 | RSA 2048 | SHA256-RSA | 8e8caa5cf3d2f797fec12571ba1ea84b323016 |
| 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/zhihu/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.socialdatax.com/zhihu/mcp | Inconclusive | 405 |
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.
zhihu_get_comment_replies_by_url ~439
根据知乎内容页链接和一级评论 ID 读取评论回复。用户已提供完整合法的 content_url 和一级评论 comment_id 时直接使用；已有 content_url 但缺少一级评论 comment_id 时，调用 zhihu_get_content_comments_by_url，复用同一 content_url，并使用一级评论的 items[*].comment_id；缺少内容定位信息时向用户索取；支持使用 page_token 继续翻页。
| Name | Type | Req | Description |
|---|---|---|---|
| comment_id | string | yes | 一级评论 ID；用户已提供时直接使用，否则请直接复制 zhihu_get_content_comments_by_url 返回的 items[*].comment_id；不要传评论回复项自身的 comment_id。 |
| content_url | string | yes | 知乎内容页面链接；用户已提供时直接使用，否则请直接复用读取该一级评论时使用的回答页链接（包括带视频的回答）、专栏文章链接或独立视频链接；通常直接复用 zhihu_get_content_comments_by_url 使用的 content_url；不要只传 content_id 或数字 ID，不要传接口地址、短链接、移动端链接、包含链接的分享文案、问题页链接或作者主页链接；支持回答页链接 ht… |
| page_token | string | – | 知乎评论回复分页令牌。首次请求留空。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回；page_token 是不透明分页令牌；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。只能用于同一 content_url 和同一 comment_id 链路；更换链接或一级评论 comment_id 时，请清空… |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | 当前页评论回复列表；当前页可能为空数组；是否可继续翻页以 next_page_token 是否为空为准。 |
| next_page_token | string | yes | 下一页不透明分页令牌；为空表示没有更多结果。继续翻页时必须将返回的完整 next_page_token 原样作为 page_token 传回；只用于当前评论回复续页；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成。 |
| points | object | yes | 本次成功调用的积分消耗与调用完成时的账户积分余额。 |
| reply_count | – | yes | 该一级评论下的回复总数；不是当前页 items 数量；不可用时为 null。 |
No examples provided.
zhihu_get_content_comments_by_url ~362
根据知乎回答页（包括带视频的回答）、专栏文章页或独立视频页链接读取一级评论。支持使用 sort_type 选择排序，并使用 page_token 继续翻页。
| Name | Type | Req | Description |
|---|---|---|---|
| content_url | string | yes | 知乎内容页面链接；只传回答页链接（包括带视频的回答）、专栏文章链接或独立视频链接；从搜索结果中的 answer、article、video 或 videoanswer 读取评论时，直接传该结果里非空的 content_url；不要只传 content_id 或数字 ID，不要传接口地址、短链接、移动端链接、包含链接的分享文案、问题页链接或作者主页链接；支持回答页链接 https://www.zh… |
| page_token | string | – | 知乎评论分页令牌。首次请求留空。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回；page_token 是不透明分页令牌；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。只能用于同一 content_url 和同一排序链路；更换链接或排序时，请清空 page_token 后从第一页重新读取评论。 |
| sort_type | string | – | 评论排序方式：default=默认，time_descending=最新。如无明确排序需求，保持 default。 |
| Name | Type | Req | Description |
|---|---|---|---|
| comment_count | – | yes | 该评论区评论数；不是当前页 items 数量；独立视频场景下也不一定等于一级评论总数；不可用时为 null。 |
| items | array | yes | 当前页一级评论列表；当前页可能为空数组；是否可继续翻页以 next_page_token 是否为空为准。 |
| next_page_token | string | yes | 下一页不透明分页令牌；为空表示没有更多结果。继续翻页时必须将返回的完整 next_page_token 原样作为 page_token 传回；只用于当前评论续页；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成。 |
| points | object | yes | 本次成功调用的积分消耗与调用完成时的账户积分余额。 |
No examples provided.
zhihu_get_content_detail_by_url ~191
根据知乎回答页（包括带视频的回答）、专栏文章页或独立视频页链接读取详情。
| Name | Type | Req | Description |
|---|---|---|---|
| content_url | string | yes | 知乎内容页面链接；只传下面三类已支持的知乎网页链接格式，不要传接口地址、短链接、移动端链接或包含链接的分享文案；从搜索结果读取详情时，直接传搜索结果里非空的 content_url；不要只传 content_id 或数字 ID，不要自行拼接链接；不要传问题页链接或作者主页链接；支持回答页链接（包括带视频的回答） https://www.zhihu.com/question/{question_i… |
| Name | Type | Req | Description |
|---|---|---|---|
| author | object | yes | 作者信息。 |
| collect_count | – | yes | 收藏数；不可用时为 null。 |
| comment_count | – | yes | 评论数；不可用时为 null。 |
| content | string | yes | 详情正文或视频描述纯文本；视频详情不是视频转写；不可用时为空字符串。 |
| content_id | string | yes | 知乎内容 ID；用于识别内容；不要把 content_id 当作详情或评论输入。 |
| content_type | string | yes | 内容类型：answer=回答（包括带视频的回答详情），article=文章，video=独立视频；详情不会返回 videoanswer。 |
| content_url | – | yes | 可打开的知乎内容页面链接；可作为评论请求的 content_url；不可用时为 null；不要自行拼接。 |
| cover_image_url | – | yes | 封面图链接；不可用时为 null。 |
| image_urls | array | yes | 回答或文章详情正文中解析到的图片链接列表；视频详情返回空数组；无图片时为空数组。 |
| images | array | yes | 正文图片列表，包含链接及宽高；无图时为空数组。 |
| ip_location | string | yes | IP 属地；不可用时为空字符串。 |
| like_count | – | yes | 喜欢数；与赞同数 upvote_count 不同；不可用时为 null。 |
| points | object | yes | 本次成功调用的积分消耗与调用完成时的账户积分余额。 |
| publish_time | – | yes | 发布时间，秒级 Unix 时间戳；不可用时为 null。 |
| question | – | yes | 回答所属问题摘要；answer（包括带视频的回答详情）返回对象，article 和独立视频 video 为 null。 |
| share_count | – | yes | 分享数；不可用时为 null。 |
| title | string | yes | 内容标题；answer 通常为所属问题标题。 |
| topic_tags | array | yes | 知乎话题标签列表；无标签时为空数组；每项只返回 name。 |
| update_time | – | yes | 更新时间，秒级 Unix 时间戳；不可用时为 null。 |
| upvote_count | – | yes | 赞同数；不可用时为 null。 |
| video | – | yes | 视频信息；独立视频详情和带视频的回答详情可能返回对象；包含可用时的播放资源 play_url；普通回答、文章或无视频信息时为 null。 |
No examples provided.
zhihu_get_hot_list ~33
读取知乎热榜，返回当前热榜问题标题、热度、回答数和问题链接。
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | 当前知乎热榜列表；当前不支持翻页。 |
| points | object | yes | 本次成功调用的积分消耗与调用完成时的账户积分余额。 |
No examples provided.
zhihu_get_user_info_by_profile_url ~125
根据知乎用户主页链接读取公开博主资料。
| Name | Type | Req | Description |
|---|---|---|---|
| profile_url | string | yes | 知乎用户主页链接；只传 https://www.zhihu.com/people/{url_token} 这种主页链接；不要传 user_id、昵称、回答链接、专栏文章链接、问题页链接、接口地址、短链接、移动端链接或包含链接的分享文案；从搜索结果、详情、评论或评论回复里的 author.profile_url 继续获取博主资料时，直接复用该非空 profile_url。 |
| Name | Type | Req | Description |
|---|---|---|---|
| answer_count | – | yes | 知乎用户公开回答数；不可用时为 null。 |
| article_count | – | yes | 知乎用户公开文章数；不可用时为 null。 |
| avatar_url | – | yes | 用户头像链接；不可用时为 null。 |
| bio | string | yes | 知乎用户简介；不可用时为空字符串。 |
| follower_count | – | yes | 知乎用户粉丝数；不可用时为 null。 |
| gender | string | yes | 知乎用户性别：male=男，female=女，unknown=未知。 |
| ip_location | string | yes | 知乎用户 IP 属地；不可用时为空字符串。 |
| name | string | yes | 知乎用户名称；不可用时为空字符串。 |
| points | object | yes | 本次成功调用的积分消耗与调用完成时的账户积分余额。 |
| profile_url | – | yes | 知乎用户主页链接；可直接复用为 zhihu_get_user_info_by_profile_url 或 zhihu_get_user_posted_articles_by_profile_url 的 profile_url；不可用时为 null。 |
| user_id | string | yes | 知乎用户 ID；用于识别博主，不是当前知乎博主资料或作者文章列表输入；不可用时为空字符串。 |
| verification_label | string | yes | 知乎用户认证文案；不可用时为空字符串。 |
| verified | boolean | yes | 知乎用户是否为认证账号。 |
No examples provided.
zhihu_get_user_posted_articles_by_profile_url ~289
根据知乎用户主页链接读取该用户发布的文章列表。只返回文章，不返回回答、想法或视频；支持使用 page_token 继续翻页。
| Name | Type | Req | Description |
|---|---|---|---|
| page_token | string | – | 知乎用户发布文章列表分页令牌。首次请求留空。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回；page_token 是不透明分页令牌；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。只能用于同一 profile_url 的文章列表链路；更换作者时，请清空 page_token 后从第一页重新读取。 |
| profile_url | string | yes | 知乎用户主页链接；只传 https://www.zhihu.com/people/{url_token} 这种主页链接；不要传 user_id、昵称、回答链接、专栏文章链接、问题页链接、接口地址、短链接、移动端链接或包含链接的分享文案；从搜索结果、详情、评论或评论回复里的 author.profile_url 继续读取作者发布文章列表时，或从博主信息结果里的 profile_url 继续读取作者… |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | 当前页知乎用户发布文章列表；当前页可能为空，是否可继续翻页以 next_page_token 是否为空为准。 |
| next_page_token | string | yes | 下一页不透明分页令牌；为空表示没有更多结果。继续翻页时必须将返回的完整 next_page_token 原样作为 page_token 传回；只用于当前用户发布文章列表续页；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成。 |
| points | object | yes | 本次成功调用的积分消耗与调用完成时的账户积分余额。 |
No examples provided.
zhihu_get_video_speech_text_job ~125
根据用户提供的有效 job_id，或 submit 工具返回的 job_id 查询知乎视频口播转文字任务；每次最多等待 240 秒，不触发重处理，也不要重复提交任务。
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | 口播转文字任务 ID；用户已提供时直接使用，否则使用 zhihu_submit_video_speech_text_by_video_url 或 zhihu_submit_video_speech_text_by_zvideo_id 返回的 job_id；任务未完成时继续原样传入同一个 job_id，不要重复提交。 |
| Name | Type | Req | Description |
|---|---|---|---|
| content_id | string | yes | 平台内容 ID。 |
| content_meta | object | yes | 作品上下文信息，便于结合转写内容做口播分析。 |
| content_type | string | yes | 内容类型。 |
| error | – | yes | 失败或过期时的稳定错误结构；非终态或成功时为 null。 |
| is_terminal | boolean | yes | 是否已终态。 |
| job_id | string | yes | 任务 ID。 |
| message | string | yes | 面向用户/AI 的状态说明。 |
| next_action | – | yes | 非终态时建议的下一步查询动作。 |
| next_poll_after_seconds | – | yes | 建议下次查询前等待的秒数；非终态时可用。 |
| platform | string | yes | 任务所属平台。 |
| source_id | string | yes | 任务来源 ID。 |
| status | string | yes | 任务状态。 |
| transcript | – | yes | 成功时的口播转文字结果；非终态或失败时为 null。 |
No examples provided.
zhihu_search_content ~442
按搜索词搜索知乎公开内容。用户需要按搜索词查找内容时使用；已有回答页、专栏文章页或独立视频页链接且需要详情或评论时使用对应 URL 工具；已有用户主页链接时使用用户资料或文章列表工具；支持类型、排序、发布时间筛选与 page_token 翻页。
| Name | Type | Req | Description |
|---|---|---|---|
| content_type | string | – | 内容类型筛选：all=不限类型，answer=只看回答，article=只看文章，video=只看视频内容（可能返回独立视频 video 或带视频的回答 videoanswer；videoanswer 不是独立视频，也不是筛选取值）。 |
| keyword | string | yes | 知乎内容搜索词，可传关键词或短语，例如问题、话题、人物、机构或内容需求；不要传问题链接、回答链接、专栏文章链接、视频链接、用户主页链接或 page_token。 |
| page_token | string | – | 知乎搜索分页令牌。首次请求留空。继续翻页时必须将上一页返回的完整 next_page_token 原样作为 page_token 传回；page_token 是不透明分页令牌；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成，不得用省略号替换中间内容。只能用于同一关键词、同一类型筛选、同一排序和同一发布时间筛选链路。更换关键词、类型、排序或发布时间筛选时，请清空 page_toke… |
| publish_time_range | string | – | 发布时间筛选：all=不限时间，day=一天内，week=一周内，month=一月内，three_months=三月内，half_year=半年内，year=一年内。如无明确筛选需求，保持 all。 |
| sort_type | string | – | 排序方式：general=综合排序，upvote_count_descending=最多赞同，time_descending=最新发布。如无明确排序需求，保持 general。 |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | 当前页知乎内容列表；当前页可能为空，是否可继续翻页以 next_page_token 是否为空为准。 |
| next_page_token | string | yes | 下一页不透明分页令牌；为空表示没有更多结果。继续翻页时必须将返回的完整 next_page_token 原样作为 page_token 传回；只用于当前搜索续页；不得修改、截断、缩写、脱敏、掩码、省略、规范化、重组或自行生成。 |
| points | object | yes | 本次成功调用的积分消耗与调用完成时的账户积分余额。 |
No examples provided.
zhihu_submit_video_speech_text_by_video_url ~156
根据知乎独立视频页或带视频回答页链接提交口播转文字任务；提交后最多等待 240 秒，未完成时返回 job_id 和下一步查询动作。
| Name | Type | Req | Description |
|---|---|---|---|
| video_url | string | yes | 知乎视频内容页面链接；支持独立视频 https://www.zhihu.com/zvideo/{zvideo_id}，以及带视频回答 https://www.zhihu.com/question/{question_id}/answer/{answer_id}；从搜索结果继续处理 videoanswer 时直接传其非空 content_url。普通无视频回答、专栏文章页、问题页、用户主页、接口地… |
| Name | Type | Req | Description |
|---|---|---|---|
| content_id | string | yes | 平台内容 ID。 |
| content_meta | object | yes | 作品上下文信息，便于结合转写内容做口播分析。 |
| content_type | string | yes | 内容类型。 |
| error | – | yes | 失败或过期时的稳定错误结构；非终态或成功时为 null。 |
| is_terminal | boolean | yes | 是否已终态。 |
| job_id | string | yes | 任务 ID。 |
| message | string | yes | 面向用户/AI 的状态说明。 |
| next_action | – | yes | 非终态时建议的下一步查询动作。 |
| next_poll_after_seconds | – | yes | 建议下次查询前等待的秒数；非终态时可用。 |
| platform | string | yes | 任务所属平台。 |
| source_id | string | yes | 任务来源 ID。 |
| status | string | yes | 任务状态。 |
| transcript | – | yes | 成功时的口播转文字结果；非终态或失败时为 null。 |
No examples provided.
zhihu_submit_video_speech_text_by_zvideo_id ~113
根据知乎独立视频的数字 zvideo_id 提交口播转文字任务；提交后最多等待 240 秒，未完成时返回 job_id 和下一步查询动作。
| Name | Type | Req | Description |
|---|---|---|---|
| zvideo_id | string | yes | 知乎独立视频 zvideo_id；用户已提供时原样使用，否则可从独立视频详情结果的 content_id 复制；必须是数字字符串。不要传视频链接、回答 ID、文章 ID 或问题 ID。 |
| Name | Type | Req | Description |
|---|---|---|---|
| content_id | string | yes | 平台内容 ID。 |
| content_meta | object | yes | 作品上下文信息，便于结合转写内容做口播分析。 |
| content_type | string | yes | 内容类型。 |
| error | – | yes | 失败或过期时的稳定错误结构；非终态或成功时为 null。 |
| is_terminal | boolean | yes | 是否已终态。 |
| job_id | string | yes | 任务 ID。 |
| message | string | yes | 面向用户/AI 的状态说明。 |
| next_action | – | yes | 非终态时建议的下一步查询动作。 |
| next_poll_after_seconds | – | yes | 建议下次查询前等待的秒数；非终态时可用。 |
| platform | string | yes | 任务所属平台。 |
| source_id | string | yes | 任务来源 ID。 |
| status | string | yes | 任务状态。 |
| transcript | – | yes | 成功时的口播转文字结果；非终态或失败时为 null。 |
No examples provided.
What is the SocialDataX 知乎 Zhihu MCP server?
SocialDataX 知乎 Zhihu MCP is listed in the public MCP registry as com.52choujiang/zhihu-insights. Zhihu/知乎 hot list, search/details, comments/replies, creators/articles, and video transcripts. This page covers its hosted endpoint (https://mcp.socialdatax.com/zhihu/mcp).
Is the SocialDataX 知乎 Zhihu MCP server safe to use?
SocialDataX 知乎 Zhihu MCP scores 84 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 知乎 Zhihu MCP server expose?
SocialDataX 知乎 Zhihu MCP exposes 11 tools: zhihu_get_hot_list, zhihu_search_content, zhihu_get_content_detail_by_url, zhihu_get_user_info_by_profile_url, zhihu_get_user_posted_articles_by_profile_url, and 6 more. Their descriptions and schemas cost roughly 2,328 tokens of context every time the server is loaded.
Does the SocialDataX 知乎 Zhihu MCP server require authentication?
Yes. SocialDataX 知乎 Zhihu 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 知乎 Zhihu MCP server still maintained?
SocialDataX 知乎 Zhihu MCP is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.