Skip to main content
Glama
manoloxhb

TrendRadar MCP Server

by manoloxhb

Related Servers

Alternatives to TrendRadar MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      An AI-powered news aggregator MCP server that fetches live news from multiple sources, provides AI summaries via Claude, and performs sentiment analysis and trending topic detection.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for trend-pulse, an agentic trend intelligence platform that fetches and analyzes trending topics from 37 sources, provides search, historical data, and lifecycle prediction via 29 tools.
      137 PyPI
      62
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An aggregator for real-time hot topics and news from major social and financial platforms like Zhihu, Bilibili, and Wall Street News. It features an MCP server that allows AI models to fetch and analyze trending information for automated insights.
      17
      GPL 3.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that aggregates AI news, academic papers from ArXiv, and trending GitHub repositories from multiple sources, enabling users to fetch, search, and filter recent AI content via natural language.
      1
      MIT

    TDQS

    A3.9/5.0

    Scored across 27 tools

    Disambiguation3/5

    Most tools are clearly scoped by resource type (news, RSS, storage, notifications), but the analysis cluster is crowded: analyze_topic_trend, analyze_data_insights, analyze_sentiment, compare_periods, and aggregate_news all accept topic/date_range and return overlapping-looking results. Detailed descriptions reduce but do not eliminate the risk of an agent picking the wrong analysis tool.

    Naming Consistency5/5

    All 27 tools follow a consistent snake_case verb_noun pattern: get_*, search_*, analyze_*, read_*, send_*, etc. Even multi-word tools like get_rss_feeds_status and generate_summary_report stay predictable. No mixed conventions or vague generic verbs.

    Tool Count2/5

    27 tools exceeds the 25+ threshold for 'too many', and the count feels inflated by several status/utility tools (get_system_status, get_storage_status, get_rss_feeds_status, get_current_config, check_version) and near-duplicate batch variants (read_article/read_articles_batch). The broad domain justifies some size, but the set would be tighter and less overwhelming at ~18-20 tools.

    Completeness4/5

    The tool surface covers the full news workflow: crawl, retrieve, search, analyze, summarize, compare, read articles, and send notifications, plus storage sync and system health. Minor gaps exist—such as no notification channel creation/editing and no persisted report storage—but agents can complete core tasks without dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues