Un servidor de Protocolo de Contexto Modelo (MCP) que proporciona temas de actualidad en tiempo real de las principales plataformas sociales y sitios de noticias chinos.
Temas de actualidad en tiempo real de 9 importantes plataformas chinas
Compatible con el protocolo MCP
Fácil integración con modelos de IA
Salida con formato Markdown con enlaces en los que se puede hacer clic
Soporte de índice de calor (donde esté disponible)
Related MCP server: Pulse CN MCP Server
Lista de los mejores de Zhihu (知乎热榜)
Lista de los 36 mejores (36氪热榜)
Discusión candente de Baidu (百度热点)
Lista caliente de Bilibili (B站热榜)
Búsqueda activa de Weibo (微博热搜)
Lista caliente de Douyin (抖音热点)
Lista de los mejores Hupu (虎扑热榜)
Lista caliente de Douban (豆瓣热榜)
Noticias de TI (IT新闻)
Fuente API: Este proyecto utiliza el servicio
api.vvhan.compara obtener datos de temas de actualidad.
get_hot_news
sources - Argumentos obligatorios: Lista de ID de plataforma
Ejemplo de uso:
get_hot_news([3]) : Obtenga solo las discusiones más candentes de Baidu
get_hot_news([1,3,7]) : Obtenga listas populares de zhihuHot, Baidu y huPu
get_hot_news([1,2,3,4]) : Obtenga listas de las más populares de zhihuHot, 36Kr, Baidu y Bilibili.
{
"mcpServers": {
"mcp-server-hotnews": {
"command": "npx",
"args": [
"-y",
"@wopal/mcp-server-hotnews"
]
}
}
}(La imagen de Docker no está cargada en Docker Hub, debe crearla usted mismo).
{
"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:urlsCompilación de Docker:
docker build -t wopal/mcp-server-hotnews:latest -f Dockerfile .Este servidor MCP cuenta con la licencia MIT. Esto significa que puede usar, modificar y distribuir el software libremente, sujeto a los términos y condiciones de la licencia MIT. Para más detalles, consulte el archivo de LICENCIA en el repositorio del proyecto.
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. Dates show when Glama detected each change.
v1.0.0get_hot_newsWith only one tool, there is no possibility of confusion or overlap between tools. The single tool has a clear, distinct purpose focused on retrieving hot trending news from various platforms, leaving no ambiguity for an agent to misselect between tools.
The naming follows a consistent verb_noun pattern with 'get_hot_news'. Since there is only one tool, it inherently maintains perfect consistency without any deviations or mixed conventions to evaluate.
A single tool is generally too few for most server purposes, as it limits functionality and may indicate an incomplete or overly narrow scope. For a news-related server, one tool feels thin and inadequate for covering typical operations like searching, filtering, or managing news content.
The tool surface is severely incomplete for a news domain. While 'get_hot_news' provides retrieval, there are obvious gaps such as searching for specific news, filtering by categories or platforms, or accessing detailed articles, which are essential for comprehensive news handling and will likely cause agent failures in broader tasks.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
MCP server aggregating hot-search boards from 8 Chinese platforms (Weibo, Zhihu, Bilibili, Douyin).
Remote MCP server for China brand visibility, destination demand, and KOL discovery workflows.
MCP server: AI-agent access to Chinese social & trend signals — Douyin, Weibo, Xiaohongshu/RedNote,
A Model Context Protocol server for Wix AI tools
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/wopal-cn/mcp-hotnews-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
