Trending topics from Weibo, Baidu, Zhihu & Google Trends for content and market research.
Model Context Protocol (MCP) Server: com.goaimoat/hot-topics
This MCP server, com.goaimoat/hot-topics, provides trending topics aggregated from Weibo, Baidu, Zhihu, and Google Trends. The intent is content and market research, using the server’s topic feed as a basis for identifying what is currently gaining attention.
🛠️ Key Features
Trending topics sourced from Weibo, Baidu, Zhihu, and Google Trends
Focus on content and market research use of trend data
🚀 Use Cases
Content research to identify current topics
Market research based on trending themes across multiple platforms
⚡ Developer Benefits
Provides a single trending-topics data source across the listed platforms
Server description clarifies its research-oriented purpose
Real-time trending topics from Weibo/Baidu/Zhihu (China) and Google Trends (US), scored against content tracks with sensitive-topic filtering. Tracks: 亲子教育, AI工具, EN_kids, EN_ai, all, raw.
Trending topics for AI agents — Weibo / Baidu / Zhihu (China) + Google Trends (US), plus HackerNews & StackExchange community intel. 2 tools. Zero dependencies, pure Python stdlib.
Hosted (no install):https://hot.mcp.goaimoat.com/mcp
Registry name:com.goaimoat/hot-topics
Free: 10 calls per day per IP. Then $0.03/call.
Built for content-creation and marketing agents that need to know what people are actually talking about right now before they write. Battle-tested in production driving a daily automated content pipeline.
Tools
Tool
What it gives the agent
get_trending
Live hot topics from 4 sources, scored against content tracks (亲子教育, AI工具, EN_kids, EN_ai, all, raw), with a built-in sensitive-topic blacklist (death/disaster/crime/politics) so agents never draft around toxic trends
get_reddit_intel
High-engagement community threads (HackerNews + StackExchange: Parenting/Workplace/Expatriates) for GEO (Generative Engine Optimization) research — the pain points real users are asking about this week
Why this exists
Trending data is scattered across platforms that expose no API, and each source covers a different audience. An agent that reads only one is working from a partial picture.
This server collects them into one structured response, so the agent sees the whole picture in a single call.
Multi-source with graceful degradation: any one source failing does not break the pipeline. A source that cannot be read is reported as unavailable rather than filled in with guesses.
Hosted API (no install, works behind any firewall)
Don't want to run it yourself, or your network can't reach these sources? A hosted version runs 24/7 on our Singapore server — one HTTP GET, JSON back:
code
GET http://43.160.199.215/hotapi/v1/hot?track=EN_ai&key=YOUR_KEY
GET http://43.160.199.215/hotapi/v1/reddit?track=poa&key=YOUR_KEY
GET http://43.160.199.215/hotapi/v1/health