TrendRadar MCP Server

Content

TrendRadar MCP Server exposes the TrendRadar news and RSS monitoring workspace to Claude through the Model Context Protocol. It lets Claude query local TrendRadar data, search RSS and hotlist records, compare periods, analyze topics, read article bodies, inspect storage status, sync remote storage, and send notification messages through configured channels.

The server is implemented with FastMCP and supports stdio and HTTP transports. The repository documents local MCP client configuration for Cursor, Cline, Continue, Cherry Studio, and other MCP-compatible clients, plus a Docker image path for running the loopback HTTP MCP service on port 3333.

Source Review

• https://github.com/sansan0/TrendRadar
• https://github.com/sansan0/TrendRadar/blob/master/README-EN.md
• https://github.com/sansan0/TrendRadar/blob/master/README-MCP-FAQ-EN.md
• https://github.com/sansan0/TrendRadar/blob/master/pyproject.toml
• https://github.com/sansan0/TrendRadar/blob/master/mcp_server/server.py
• https://github.com/sansan0/TrendRadar/blob/master/mcp_server/tools/data_query.py
• https://github.com/sansan0/TrendRadar/blob/master/mcp_server/tools/notification.py
• https://github.com/sansan0/TrendRadar/blob/master/mcp_server/tools/storage_sync.py
• https://github.com/sansan0/TrendRadar/blob/master/docker/Dockerfile.mcp
• https://github.com/sansan0/TrendRadar/blob/master/version_mcp
• https://github.com/sansan0/TrendRadar/blob/master/LICENSE

These sources were reviewed on 2026-06-06. Prefer the live repository, English README, MCP FAQ, package metadata, server implementation, tool modules, Dockerfile, MCP version file, and license for current setup commands, tool names, supported transports, configuration behavior, and runtime risks.

Features

• FastMCP-based server with stdio and HTTP transport support.
• Local-source setup using uv --directory /path/to/TrendRadar run python -m mcp_server.server.
• Docker HTTP service path for trendradar-mcp, listening on port 3333 by default.
• News and RSS query tools for latest data, date ranges, platform filters, and available dates.
• Search tools for keyword, fuzzy, entity, RSS-inclusive, and related-news workflows.
• Trend analysis tools for topic hotness, lifecycle, viral signals, sentiment, period comparison, aggregation, and summary reports.
• System tools for configuration inspection, version checks, status checks, and manual crawl triggering.
• Storage tools for remote sync, local/remote date listing, and storage status.
• Article reader tools that convert URLs into Markdown through Jina Reader.
• Notification tools for channel status, channel-specific formatting guidance, and message sending.

Installation

Clone TrendRadar, install dependencies with uv, and run the MCP server from the project checkout. For stdio clients, the repository documents a local command shaped like:

{
  "mcpServers": {
    "trendradar": {
      "command": "uv",
      "args": [
        "--directory",
        "/path/to/TrendRadar",
        "run",
        "python",
        "-m",
        "mcp_server.server"
      ]
    }
  }
}

The Docker MCP image starts the HTTP server with:

python -m mcp_server.server --transport http --host 0.0.0.0 --port ${MCP_PORT}

Keep the exposed HTTP endpoint local unless you add your own reverse proxy, authentication, and network controls.

Use Cases

• Ask Claude to search today's TrendRadar output for a company, policy, product, or AI topic.
• Compare how a topic appears across platforms, RSS feeds, and time periods.
• Generate a daily or weekly briefing from locally accumulated hotlist and RSS data.
• Read article bodies after search results identify source URLs worth deeper analysis.
• Pull recent data from remote storage into a local MCP analysis workspace.
• Check configured notification channels before sending a reviewed summary to team chat.
• Inspect current TrendRadar configuration before changing crawl, RSS, storage, or notification workflows.

Safety and Privacy

TrendRadar MCP is useful for news intelligence, but it is not read-only in every workflow. Claude can trigger crawls, sync remote storage, and send notifications to real channels if credentials are configured. Use review prompts or client approval settings before allowing notification sends, remote syncs, or broad crawl operations.

Treat stored news data and configuration as sensitive operational context. Watch keywords, RSS feeds, webhook destinations, cloud bucket names, article URLs, and AI-analysis prompts can reveal business interests or monitoring strategy. Keep notification secrets, S3-compatible credentials, and AI provider keys in approved secret stores, and avoid exposing the HTTP MCP endpoint beyond trusted local environments.

Duplicate Check

No sansan0/TrendRadar, trendradar-mcp, TrendRadar MCP, news trend analysis MCP, public-opinion monitoring MCP, or TrendRadar notification MCP entry was found in content/mcp, content/tools, content/guides, content/agents, or content/skills.