No user-submitted related servers found.
Scored across 27 tools
Each tool has a clearly distinct purpose with detailed descriptions. While there are many tools, they are well-separated: data retrieval (get_latest_news, get_news_by_date), search (search_news, search_rss), analysis (analyze_topic_trend, analyze_sentiment, analyze_data_insights), system management (get_system_status, trigger_crawl), and notifications (send_notification, get_channel_format_guide). No two tools appear to do the same thing.
All tool names follow a consistent snake_case verb_noun pattern (e.g., get_latest_news, analyze_sentiment, send_notification). The verbs are varied but predictable (get, search, analyze, read, send, trigger, sync, list, check, resolve, compare, find, aggregate), and the nouns clearly indicate the resource or action. There is no mixing of conventions.
With 27 tools, this exceeds the 25+ threshold that indicates a heavy set. While the server covers a broad scope (data fetching, analysis, search, system ops, article reading, notifications), many tools are peripheral system-management utilities (e.g., check_version, get_storage_status, list_available_dates) that could arguably be consolidated or exposed as a separate set. The core trend-analysis functionality is well-covered, but the overall count feels excessive for a single MCP server.
The tool surface is quite comprehensive for a trend-radar/news-analysis domain: it covers data ingestion (trigger_crawl, sync_from_remote), retrieval (get_news_by_date, get_latest_rss), search (search_news, search_rss), analysis (trend, sentiment, insights, comparison), article reading (read_article, read_articles_batch), and notifications (send_notification). Minor gaps include lack of configuration write operations (only get_current_config) and feed management (only get_rss_feeds_status), but these are not critical for typical use.