SocialDataX 知乎 Zhihu MCP
com.52choujiang/zhihu-insights · 0.1.3
Zhihu/知乎 hot list, search/details, comments/replies, creators/articles, and video transcripts.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 50 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 15 of 15 | The registry entry declares a key or a token. |
| Latest connection test reached it | 20 of 20 | The latest test had its handshake answered. |
Where it answers
https://mcp.socialdatax.com/zhihu/mcpstreamable-httpAuthorizationrequired, secret: Bearer API Key from SocialDataX / 社媒数据助手
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 13 tools.
- Protocol
- 2025-06-18
- Calls itself
- zhihu_mcp 0.1.3
- Handshake time
- 960 ms
- HTTP status
- 200
The tools it lists (13, as of 4 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
zhihu_search_users按关键词搜索知乎用户；已有用户主页链接时直接调用用户资料接口。支持 page_token 翻页。
zhihu_search_suggestions根据关键词获取知乎搜索输入框联想词；不用于搜索用户或内容。
zhihu_get_hot_list读取知乎热榜，返回当前热榜问题标题、热度、回答数和问题链接。
zhihu_search_content按搜索词搜索知乎公开内容。用户需要按搜索词查找内容时使用；已有回答页、专栏文章页或独立视频页链接且需要详情或评论时使用对应 URL 工具；已有用户主页链接时使用用户资料或文章列表工具；支持类型、排序、发布时间筛选与 page_token 翻页。
zhihu_get_content_detail_by_url根据知乎回答页（包括带视频的回答）、专栏文章页或独立视频页链接读取详情。
zhihu_get_user_info_by_profile_url根据知乎用户主页链接读取公开博主资料。
zhihu_get_user_posted_articles_by_profile_url根据知乎用户主页链接读取该用户发布的文章列表。只返回文章，不返回回答、想法或视频；支持使用 page_token 继续翻页。
zhihu_get_content_comments_by_url根据知乎回答页（包括带视频的回答）、专栏文章页或独立视频页链接读取一级评论。支持使用 sort_type 选择排序，并使用 page_token 继续翻页。
zhihu_get_comment_replies_by_url根据知乎内容页链接和一级评论 ID 读取评论回复。用户已提供完整合法的 content_url 和一级评论 comment_id 时直接使用；已有 content_url 但缺少一级评论 comment_id 时，调用 zhihu_get_content_comments_by_url，复用同一 content_url，并使用一级评论的 items[*].comment_id；缺少内容定位信息时向用户索取；支持使用 page_token 继续翻页。
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.52choujiang/zhihu-insights, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 9 days ago. The registry entry