Quick Verdict
TrendRadar is a durable trend-discovery and RSS monitoring platform, not merely a script that takes one snapshot of trending lists. It combines multi-platform rankings, RSS/Atom, keyword and AI-interest filtering, scheduled reports, historical SQLite data, notifications, and MCP queries in one self-hosted workflow. The repository identifies the current main application as version 6.10.0 and uses GPL-3.0. Its GitHub Releases API has no formal release entries, so version history is maintained mainly in the README and project files.
It suits individuals and teams willing to manage configuration, sources, storage, and messaging secrets. It can support brand monitoring, industry briefs, competitor tracking, and RSS digests, but it does not grant republication rights or make third-party sources reliable. Some ranking data comes from the NewsNow API, with an option to configure a self-hosted endpoint. Data availability, source terms, content rights, AI providers, and notification services remain separate decisions.
Best For
- Research and content teams combining public rankings with selected RSS feeds
- Brand and marketing teams tracking keyword appearance, rank changes, and cross-platform momentum
- Technical self-hosters comfortable with YAML, secrets, schedulers, Docker, and backups
- Internal intelligence workflows that need scheduled delivery and MCP access to collected history
- Not ideal for buyers requiring licensed official datasets, a hosted SLA, unreviewed automated conclusions, or zero secret-management responsibility
Key Features
- Ranking and RSS aggregation: collects platform lists and RSS/Atom feeds into a common reporting flow
- Historical trend storage: SQLite preserves new items, ranking trajectories, dates, and prior topics rather than only the latest snapshot
- Layered filtering: keywords, required terms, exclusions, regular expressions, groups, AI interest descriptions, and per-group limits
- AI pipeline: optional filtering, translation, summaries, trend analysis, and sentiment through LiteLLM-compatible providers
- Notification channels: WeCom, Feishu, DingTalk, Telegram, email, ntfy, Bark, Slack, and generic webhooks
- Deployment and query surfaces: GitHub Actions, Docker, local Python, HTML/Markdown reports, and a separate MCP service over saved data
Use Cases
- Industry briefings that merge rankings and selected feeds into morning or evening reports
- Brand and competitor monitoring using history to separate brief spikes from sustained momentum
- Focused research feeds built from RSS, source groups, regular expressions, and AI-assisted first-pass filtering
- Historical conversational queries through MCP against the local SQLite collection, not the open web at large
- Automation handoff to n8n or an internal review and archive process while preserving source URLs
Pricing
TrendRadar itself is free and licensed under GPL-3.0. Running and modifying it is different from distributing a modified program; organizations shipping copies or derivative code should review the corresponding source and notice obligations. The software license does not cover the rights in fetched articles, RSS content, trademarks, AI output, or third-party services.
Operational costs can include GitHub Actions quotas, a Docker host, object storage, model calls, email, and messaging services. Although the README marks version 6.10.0, there is no formal GitHub release object to pin. Production operators should lock an audited commit or image digest, keep migration notes, and test rollback instead of automatically following the latest master branch.
Pros
- Complete loop from collection and history to filtering, AI analysis, reports, and delivery
- Multiple deployment paths plus configurable data and storage endpoints
- Strong Chinese documentation and support for common regional messaging channels
- Historical SQLite data and MCP make prior observations searchable
- Clear GPL-3.0 licensing and a detailed, actively maintained change history
Cons
- No formal GitHub Releases, so version pinning and rollback need an operator-owned process
- Ranking collection depends on NewsNow and third-party pages whose fields and availability can change
- Technical access to RSS or rankings does not grant content reuse rights
- AI analysis introduces cost, disclosure, and hallucination risk
- Numerous notification integrations create a large set of high-impact secrets
- Self-hosting transfers authentication, backup, monitoring, patching, and availability duties to the user
Alternatives
| Tool | Best for | Main advantage | Boundary versus TrendRadar |
|---|---|---|---|
| Perplexity | Ad hoc sourced research | Immediate answers and citations | No continuous collector or owned history |
| Tavily | Agent search APIs | Developer-oriented retrieval output | Monitoring, storage, and alerts are DIY |
| Exa | Semantic web discovery | Strong semantic retrieval and content access | Not a Chinese ranking-monitoring platform |
| n8n | General automation | Broad connectors and flow control | Trend collection and ranking logic must be built |
| Dify | Delivering AI applications | Rich model and application workflows | No equivalent continuous news pipeline by default |
Perplexity is simpler for one-time questions. Tavily and Exa are better retrieval primitives for agents. n8n and Dify offer more general workflow freedom. TrendRadar is differentiated by packaging continuous collection, history, filtering, and delivery into a ready-to-run system.
FAQ
What is the current TrendRadar version?
As of July 21, 2026, the repository README identifies the main application as 6.10.0. There are no formal GitHub Releases, so pin a commit or image digest and record the source of every production upgrade.
Can TrendRadar be used commercially for free?
The GPL-3.0 software can be run and modified without a subscription, but distribution of modified or derivative code can trigger source and license obligations. Content, AI, branding, and notification-service rights remain separate.
Does NewsNow or RSS access permit republication?
No. Being able to fetch a title or feed does not automatically permit copying full articles, public redistribution, or commercial reuse. Preserve attribution and links, limit excerpts, and review each source’s terms and applicable law.
Does AI analysis send data outside the host?
It does when an external model provider is enabled. Titles, summaries, or other prompt context then cross the local boundary. Minimize fields and avoid sending unauthorized full text, personal data, or internal intelligence.
Should I use GitHub Actions or Docker?
Actions is convenient for low-frequency personal reports but has quota and secret-management constraints. Docker or a local host is better for continuous collection, private endpoints, or durable history, provided you operate backups, updates, and monitoring.
Where should notification credentials be stored?
Use GitHub Secrets, container secrets, or controlled environment variables. Never commit webhooks, SMTP passwords, or model keys to public configuration, logs, screenshots, or fork history. Rotate any exposed secret immediately.
Bottom Line
TrendRadar 6.10.0 is valuable because it creates a persistent information pipeline: rankings and RSS enter a historical store, rules or AI filter them, channels distribute reports, and MCP queries prior data. Before adoption, pin the code, review NewsNow and RSS rights, minimize AI disclosures, protect notification and storage secrets, and back up SQLite. For teams willing to own those self-hosting duties, it is a mature trend platform. For occasional research, a lighter search product is easier.