Skip to main content
Glama
sligter

mcp-newsnow

by sligter
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

MCP NewNow Server

MCP Compatible

一个基于 Model Context Protocol (MCP) 的新闻聚合服务器，通过 Newsnow API 提供多平台热点新闻和趋势话题。

功能特点

  • 多平台热点聚合：一站式获取来自酷安、知乎、微博、B站、抖音、GitHub等14+平台的热点内容

  • 中英文源名识别：支持中英文新闻源名称，并提供模糊匹配功能

  • 自定义API端点：通过环境变量或命令行参数配置NewNow API端点

Related MCP server: Realtime-News

安装方法

方法一：从 PyPI 安装

# 使用 pip 安装
pip install mcp-newsnow

# 或使用 uv 安装
uv pip install mcp-newsnow

方法二：配置 Claude Desktop

在 Claude Desktop 配置文件中添加服务器配置：

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

添加以下配置：

{
  "mcpServers": {
    "get_news": {
      "command": "uvx",
      "args": [
        "mcp-newsnow"
      ]
    }
  }
}

使用方法

使用 Claude Desktop

  1. 安装并配置 Claude Desktop

  2. 在配置文件中添加上述 MCP 服务器配置

  3. 重启 Claude Desktop

  4. 在对话中使用新闻相关工具

使用 MCP CLI 进行开发

# 通过环境变量设置API端点
NEWS_API_URL=https://newsnow.example.com

# 运行测试
mcp test server.py

可用工具

1. 获取单一源新闻 (get_newsnow)

async def get_newsnow(source: str) -> dict[str, Any] | None

从指定源获取最新新闻。

参数:

  • source: 新闻源名称 (支持中英文，例如"知乎"、"zhihu"、"B站"等)

返回: 包含新闻数据的字典

2. 获取多源新闻 (get_multi_news)

async def get_multi_news(sources: list[str] = None) -> dict[str, Any]

从多个源获取最新新闻 (最多5个)。

参数:

  • sources: 新闻源名称列表

返回: 包含多个新闻源数据的字典

3. 获取所有源新闻 (get_all_news)

async def get_all_news() -> dict[str, Any]

获取所有配置的新闻源数据。

返回: 包含所有新闻源数据和元数据的字典

4. 列出可用新闻源 (list_sources)

async def list_sources() -> dict[str, str]

列出所有可用的新闻源及其中文名称。

返回: 新闻源ID到中文名称的映射字典

环境变量

支持的新闻源

  • 酷安 (coolapk)

  • B站热搜 (bilibili-hot-search)

  • 知乎 (zhihu)

  • 微博 (weibo)

  • 今日头条 (toutiao)

  • 抖音 (douyin)

  • GitHub趋势 (github-trending-today)

  • Linux热榜 (linuxdo-hot)

  • 贴吧 (tieba)

  • 华尔街见闻 (wallstreetcn)

  • 澎湃新闻 (thepaper)

  • 财联社 (cls-hot)

  • 雪球 (xueqiu)

  • 快手 (kuaishou)

贡献指南

欢迎提交问题和拉取请求！以下是一些潜在的改进方向：

  • 添加更多新闻源支持

  • 增强内容提取和处理能力

  • 添加缓存层减少API调用

  • 改进错误处理和重试机制

  • 添加结果过滤和分类功能

许可证

本项目采用 MIT 许可证。

Available Tools

4 tools
get_all_newsB

获取所有配置的新闻源的数据

Returns:
    包含所有新闻源数据的字典
ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

B3.3/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided and the description does not disclose any behavioral traits (e.g., idempotency, auth needs, rate limits), leaving the agent with minimal insight.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Extremely concise with one functional line; could include more context but remains efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no parameters, no output schema, and no annotations, the description is minimal but covers the basic purpose; could mention output format details or limits.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With zero parameters, the description adds no extra meaning but is adequate for a parameterless tool; baseline 4 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it gets data for all configured news sources, which distinguishes it from siblings that may fetch a subset or specific source.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool vs alternatives; only implies it is for all sources without further context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_multi_newsC

从多个源获取最新新闻

ParametersJSON Schema
NameRequiredDescriptionDefault
sourcesNo

TDQS

C2/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, so the description must carry the full burden. It only states the tool gets news; no disclosure of read-only nature, authentication needs, rate limits, or any side effects. Very insufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very concise (one sentence), but it lacks structure and substance. It is not bloated, but conciseness should not compromise completeness. There is no front-loading of key info.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple tool with one optional parameter and no output schema, the description should at least explain the parameter and possible values. It does not, leaving the agent with minimal context. Sibling tools exist but no guidance to navigate between them.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description does not mention the 'sources' parameter. Schema description coverage is 0%, and the parameter has no description in the schema either. The description adds zero meaning beyond the parameter name.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it gets the latest news from multiple sources, which is clear. However, it does not differentiate from sibling tools like get_all_news, making it ambiguous whether it is a filtered version or similar.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives (get_all_news, get_newsnow, list_sources). No context on prerequisites or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_newsnowC

从指定源获取最新新闻

ParametersJSON Schema
NameRequiredDescriptionDefault
sourceYes

TDQS

C2.4/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It implies a read-only operation but does not disclose any behavioral traits such as authentication requirements, rate limits, or data recency. A more detailed description is needed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (one sentence) and front-loaded, but it is too minimal. While concise, it sacrifices necessary detail. It earns a 3 because it states the purpose without extra words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of output schema and parameter descriptions, the description is severely incomplete. It does not explain what 'source' means, what the output looks like, or any other relevant context for a tool with one required parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The single parameter 'source' has no schema description and 0% coverage. The description does not clarify what values are valid (e.g., source names, IDs, URLs). The tool definition fails to provide essential semantic guidance.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description '从指定源获取最新新闻' clearly states the action (get latest news) and resource (from specified source). However, it does not differentiate from sibling tools like get_all_news and get_multi_news, which might perform similar functions.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus its alternatives (get_all_news, get_multi_news, list_sources). The description only states what it does, not the context for its use.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

list_sourcesA

列出所有可用的新闻来源和对应的中文名称

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations provided, but the description accurately describes the read-only listing behavior. No hidden traits or side effects need disclosure for this simple tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence, front-loaded with the verb '列出', no unnecessary words. Highly concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no parameters and no output schema, the description fully specifies what it returns. Complete for its simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters exist (schema coverage 100%). The description adds value by specifying what the list contains (sources and Chinese names), beyond the empty schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action (list) and the resource (all available news sources with Chinese names). It distinguishes from sibling tools like get_all_news which likely retrieve articles.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use this tool vs alternatives. Usage is implied but not explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 4 tool updatesv0.1.4
    • First observedget_all_news
    • First observedget_multi_news
    • First observedget_newsnow
    • First observedlist_sources
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3/5.0

Scored across 4 tools

Disambiguation4/5

Tools are largely distinct: get_all_news retrieves all sources, get_multi_news from multiple specific sources, get_newsnow from a single specified source, and list_sources lists sources. The slight overlap between get_all and get_multi could cause misselection if descriptions are not read carefully.

Naming Consistency3/5

The naming pattern is mostly 'get_<qualifier>_news' for three tools, but 'get_newsnow' breaks this pattern by combining words and omitting an underscore. 'list_sources' follows verb_noun consistently.

Tool Count5/5

With exactly 4 tools, the set is well-scoped for a news aggregator that needs to list sources and fetch news in all, multiple, or single source modes. No excess or deficiency.

Completeness4/5

The set covers essential news retrieval operations (list sources, get all/multiple/single news). It lacks source management, but that is likely out of scope. Minor gap: no search or filter functionality.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • MCP Hot News Server

    wudalu
    A
    license
    Not graded
    quality
    D
    maintenance
    A modern multi-platform hot news aggregation server based on FastMCP that supports real-time hot topics data collection from 13+ major platforms including Zhihu, Weibo, Baidu, and Bilibili.
    3
    MIT

  • Realtime-News

    xiaobenyang-com
    A
    license
    B
    quality
    D
    maintenance
    Obtain real-time news trending lists: Weibo Hot Search, Baidu Hot List, Zhihu Hot List, Jinri Toutiao Hot List, 36Kr Hot List, Tencent News Hot List, Bilibili Hot List, The Paper Hot List, Hupu Walking Street Hot List, TikTok Hot List, IT News Hot List, Huoxiu Hot List, Baidu Tieba Hot List, Juejin
    17
    2
    Apache 2.0

  • What Happen MCP

    kawayiYokami
    F
    license
    Not graded
    quality
    Not graded
    maintenance
    Aggregates news from 70+ platforms across categories like tech, finance, social, entertainment, and sports. Provides access to trending topics from popular Chinese platforms including Weibo, GitHub, Zhihu, Baidu, and Bilibili.
    12 npm
    2
    -

  • HotNews MCP Server

    hanweiit007
    A
    license
    B
    quality
    D
    maintenance
    Provides real-time hot trending topics and heat indices from nine major Chinese social media and news platforms including Weibo, Zhihu, and Bilibili. It enables users to fetch markdown-formatted news summaries and clickable links via the get_hot_news tool.
    1
    1,019 npm
    3
    MIT