Provides access to real-time hot discussions and trending news topics from Baidu.
Fetches real-time hot lists and trending content from the Bilibili video and social platform.
Retrieves real-time trending topics and hot lists from the Douban social community.
Accesses real-time hot lists and trending knowledge-sharing discussions from the Zhihu platform.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@HotNews MCP Server Show me what's trending on Weibo and Zhihu right now"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
A Model Context Protocol (MCP) server that provides real-time hot trending topics from major Chinese social platforms and news sites.
Real-time hot topics from 9 major Chinese platforms
MCP protocol compatible
Easy integration with AI models
Markdown formatted output with clickable links
Heat index support (where available)
Related MCP server: What Happen MCP
Zhihu Hot List (知乎热榜)
36Kr Hot List (36氪热榜)
Baidu Hot Discussion (百度热点)
Bilibili Hot List (B站热榜)
Weibo Hot Search (微博热搜)
Douyin Hot List (抖音热点)
Hupu Hot List (虎扑热榜)
Douban Hot List (豆瓣热榜)
IT News (IT新闻)
API Source, This project uses the
api.vvhan.comservice for fetching hot topics data.
get_hot_news
sources - Required arguments: Platform ID list
Example usage:
get_hot_news([3]) : Get Baidu Hot Discussion only
get_hot_news([1,3,7]) : Get hot lists from zhihuHot, Baidu, and huPu
get_hot_news([1,2,3,4]) : Get hot lists from zhihuHot, 36Kr, Baidu, and Bilibili`
{
"mcpServers": {
"mcp-server-hotnews": {
"command": "npx",
"args": [
"-y",
"@wopal/mcp-server-hotnews"
]
}
}
}（ Docker image not uploaded to Docker Hub, need to build it yourself. ）
{
"mcpServers": {
"mcp-server-hotnews": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"wopal/mcp-server-hotnews"
]
}
}
}# Install dependencies
npm install
# Watch mode
npm run watch
# Build
npm run build
# Test URLs
npm run test:urlsDocker build:
docker build -t wopal/mcp-server-hotnews:latest -f Dockerfile .This MCP server is licensed under the MIT License. This means you are free to use, modify, and distribute the software, subject to the terms and conditions of the MIT License. For more details, please see the LICENSE file in the project repository.
Get hot trending lists from various platforms
| Name | Required | Description | Default |
|---|---|---|---|
| sources | Yes | Available HotNews sources (ID: Platform): {ID: 1, Platform: "Zhihu Hot List (知乎热榜)"}, {ID: 2, Platform: "36Kr Hot List (36氪热榜)"}, {ID: 3, Platform: "Baidu Hot Discussion (百度热点)"}, {ID: 4, Platform: "Bilibili Hot List (B站热榜)"}, {ID: 5, Platform: "Weibo Hot Search (微博热搜)"}, {ID: 6, Platform: "Douyin Hot List (抖音热点)"}, {ID: 7, Platform: "Hupu Hot List (虎扑热榜)"}, {ID: 8, Platform: "Douban Hot List (豆瓣热榜)"}, {ID: 9, Platform: "IT News (IT新闻)"} Example usage: - [3]: Get Baidu Hot Discussion only - [1,3,7]: Get hot lists from zhihuHot, Baidu, and huPu - [1,2,3,4]: Get hot lists from zhihuHot, 36Kr, Baidu, and Bilibili |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the tool retrieves data ('Get'), implying a read-only operation, but fails to specify critical behaviors such as rate limits, authentication requirements, data freshness, or error handling. This leaves significant gaps in understanding how the tool behaves in practice.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that directly states the tool's function without unnecessary words. It is front-loaded with the core purpose, making it easy for an agent to quickly grasp the tool's intent, which exemplifies ideal conciseness.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of annotations and output schema, the description is insufficiently complete. It omits details about return values, error conditions, and behavioral constraints, which are crucial for a tool that fetches data from multiple platforms. The high schema coverage does not compensate for these missing contextual elements.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% description coverage, thoroughly documenting the 'sources' parameter with examples and platform details. The description adds no additional parameter information beyond what the schema provides, so it meets the baseline score of 3 for high schema coverage without compensating value.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose: 'Get hot trending lists from various platforms.' It specifies the action ('Get') and resource ('hot trending lists'), and mentions the scope ('various platforms'). However, with no sibling tools provided, it cannot demonstrate differentiation from alternatives, which prevents a perfect score of 5.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, prerequisites, or exclusions. It simply states what the tool does without context about appropriate scenarios or limitations, leaving the agent with minimal usage direction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
v0.2.0get_hot_newsScored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly distinct by default.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The name 'get_hot_news' follows a clear verb_noun pattern.
One tool is too few for a server named 'HotNews MCP Server', which suggests a broader scope for accessing trending news. A single 'get' operation lacks the expected range for news retrieval, such as filtering, searching, or managing sources.
The tool surface is severely incomplete for a news server. It only provides a generic 'get' for hot news, with no support for operations like filtering by platform, time, category, or accessing detailed articles, making it inadequate for typical news-related workflows.
MCP server aggregating hot-search boards from 8 Chinese platforms (Weibo, Zhihu, Bilibili, Douyin).
Zhihu/知乎 hot list, search/details, comments/replies, creators/articles, and video transcripts.
Weibo hot search, post search/details, comments/replies, users, posts, transcript.
Real-time news and trending topics from major sources