fanqie-radar
Related Servers
Alternatives to fanqie-radar
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to query Google Trends data, including search interest over time, regional breakdowns, trending searches, and keyword ideas.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to query TikTok Shop analytics through the Kalodata Open API, including category, product, creator, and video rankings and details.1-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to access Google Trends data for comparing keywords, discovering trending searches, and analyzing regional interest through natural language.2MIT
- AlicenseAqualityBmaintenanceProvides TikTok trend data to AI assistants, including hashtag volume, growth rates, and top trending topics for early trend detection.31MIT
- AlicenseBqualityDmaintenanceEnables searching and reading novels from FanQie Novel platform through MCP, supporting book details, chapters, comments, and multi-type content retrieval.1436 npm48MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to query GitHub trending projects, analyze language and technology trends, and generate visual trend reports.MIT
TDQS
Scored across 7 tools
Each tool targets a distinct analytical concern: raw rankings, lookup, trend diff, genre aggregation, imitation scoring, keyword frequency, and data stats. Even the two heat-related tools are clearly separated by dimension: genre read volume vs. title-word frequency.
All tool names share the fanqie_ prefix, use lowercase snake_case, and combine the server domain with a descriptive noun or verb. The naming pattern is predictable and makes the set feel uniform.
Seven tools is a well-scoped size for a domain-specific ranking-analysis server. Each tool has a clear purpose and none feel redundant or ornamental.
The core analysis workflow—read rankings, search books, compare trends, assess genre heat, and score imitation candidates—is fully covered. The main gap is the absence of an explicit snapshot-capture or refresh tool to ensure trend data is available, though this may be handled externally or by the fetch path.