TrendRadar MCP

A self-hosted trend and news monitor with an MCP server: hot-topic aggregation, RSS and smart alerts

  • 63,615 ★ on the repository
  • Last commit
  • GPL-3.0
MCP serverOfficial

Extended access

Why this level

  • The service reaches the network and collects data from external platforms
  • It sends alerts to external channels per your configuration
All reasons and checks

sansan0/trendradar

Install

Services

Manual install

docker compose up -d trendradar-mcp

Starts the MCP service within docker compose; the main trendradar service is started separately.

Access and checks

How we review

Extended accessThe tool runs code or makes network calls and only reads external data.

  • The service reaches the network and collects data from external platforms
  • It sends alerts to external channels per your configuration

This is third-party code. Review the repository files before installing.

What it does

TrendRadar collects hot topics from many platforms and RSS feeds, filters them by keywords and pushes digests to messengers and email. A separate MCP server exposes this data to an agent: you can chat about trends, analyze sentiment and reason about momentum in natural language. It installs through uv or Docker and keeps data locally or in the cloud as you choose. The MCP server listens on a local port and connects to clients such as Claude Desktop or Cline.

Who it is for. For marketers, SMM and analysts who need news monitoring with agent-driven analysis.

Good fit when

  • You need to track hot topics by keyword and get digests
  • You want to discuss trends and sentiment with an agent over MCP
  • You need alerts about spikes of interest in messengers

Not a fit when

  • You want a turnkey cloud service with no self-hosting
  • You only care about platforms outside the supported sources

Example request

Show today's hot topics for my keywords and assess their sentiment

MCP

Transport
http
Authentication
not required

Limitations

You self-host the service through uv or Docker. The MCP server listens only on 127.0.0.1 by default; remote access needs a reverse proxy and authentication you set up. The main hot-topic sources are oriented toward Chinese platforms.

How to disable. Stop the trendradar-mcp container (docker compose stop trendradar-mcp) and remove the trendradar entry from your client's MCP config.

FAQ

Is MCP required?

No, TrendRadar also works as a plain monitor with alerts. MCP adds agent-driven trend analysis.

Where do alerts go?

To WeChat, Feishu, DingTalk, Telegram, Slack, email and via ntfy or bark, per your configuration.

Discussion

No questions or reviews yet.

Telegram API MCP

telegram-api-mcp

Russian stack

MCP server for the Telegram Bot API: messages, channels, forums, payments and long posts from a bot, with Telegram rate limits built in

MCP serverBroad access34Repository stars
Russian stack

An MCP server for Mail.ru email in Claude.ai, plus a separate Telegram bot that checks the inbox every 15 minutes and alerts on important messages

MCP serverBroad access

TG Telegram Parser refreshes a saved channel export, adding new posts and revisiting a configured number of earlier discussions.

CLIExtended access241Repository stars

TGStat MCP

tgstat-mcp

Russian stack

TGStat MCP server: Telegram channel and post search, subscriber and reach trends, ERR and mentions

MCP serverExtended access4Repository stars

MCP Telegram for reading: the agent gets your account's dialog list and unread messages over MTProto and has no way to write on your behalf

MCP serverBroad access190Repository stars

README in short

The README describes TrendRadar as an aggregator of hot topics across several platforms and RSS, with keyword filtering and smart alerts to popular channels. It highlights an MCP server that gives an agent conversational access to the data for sentiment and trend analysis. Installation is available through uv, Docker and docker compose, including a separate trendradar-mcp image. GPL-3.0 licensed.

README badge

Report a problem