mcpbeat Sign in

TrendHub MCP Server

by zachary-1012 Your server? Claim it
not responding

TrendHub is listed as active in the registry but did not answer our last check. It exposes 21 tools.

Evidence-backed AI content studio with 21 stable trend intelligence tools.

Uptime history 54 days of history · worst day 0%
54 days agonow
0.0%
Uptime 24h
0 of 92 checks
21
Tools
read from the server
406 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 35

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 17 September 2026. No other catalogue keeps this.

23 Sep a tool changed version4 times that day
23 Sep a tool changed the parameters it asks for2 times that day get_content_brief
21 Sep 2 tools changed the parameters they ask for future_signals, xhs_hot_topics
21 Sep a tool changed version2 times that day
21 Sep a tool description was rewritten get_content_brief
20 Sep a tool changed version7 times that day
20 Sep 5 tool descriptions were rewritten6 times that day analyze_topic, get_trending, professional_intelligence and 2 more
20 Sep 2 tools changed the parameters they ask for professional_intelligence, workspace_manage
18 Sep a tool changed version2 times that day
17 Sep a tool changed version4 times that day
and 19 more, back to 17 September 2026

TrendHub does not always answer

Over the last week it answered 0.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

run in your terminal
claude mcp add trendhub --transport http https://trendhub-remote-production.up.railway.app/mcp
Settings → Connectors → Add custom connector, then paste this address
https://trendhub-remote-production.up.railway.app/mcp
~/.codex/config.toml
[mcp_servers.trendhub]
url = "https://trendhub-remote-production.up.railway.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "trendhub": {
      "url": "https://trendhub-remote-production.up.railway.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "trendhub": {
      "type": "http",
      "url": "https://trendhub-remote-production.up.railway.app/mcp"
    }
  }
}

Available tools 21

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

trend
trend_change_alerts
对比历史快照,输出各平台新晋上榜、排名飙升(≥3位)、掉榜的话题。需要先有两次以上快照(get_trending 会自动积累,或用 take_snapshot)。
trend_intelligence
轻量纵向 Trend Intelligence:基于本地真实历史计算生命周期、速度、持续性、扩散、Source Reliability 与确定性置信度;品牌实体、媒体、异常/预测、告警和报告请用 professional_intelligence。历史不足返回 insufficient_history。
analyze
analyze_topic
话题研究包:聚合当前共振、搜索曲线/动量、相关词、未来信号、节点与规则情感;需要多年度生命周期、验证预测、品牌实体或高管报告时使用 professional_intelligence。
benchmark
benchmark_trend_lead
真实场景 Lead-time Benchmark:把 TrendHub 本地历史的最早命中,与用户提供的外部事实 reference_time 对比,计算是否提前24h/72h发现。reference_time 必须来自官方公告、主流爆发点或团队约定的外部 ground truth,TrendHub 不会自己编造基准时间。
categories
list_categories
列出平台分类与内容/模板分类
content
get_content_brief
围绕主题聚合真实热点证据、相关搜索词、同平台样本与模板,并在内容工作台中调用使用者当前 AI 产出可编辑制品。
cross
cross_platform_overlap
分析某个关键词/话题当前在多少个平台同时上榜(跨平台共振),给出各平台命中条目、最佳排名与共振分。用于判断一个话题是否具备全网热度。
discover
discover_trending_topics
无需关键词,自动聚类发现当前在多个平台共振的话题(基于标题相似度,结果需大模型复核归纳)。
future
future_signals
聚合高质量科技/AI/商业/营销信源的最新文章(未来趋势信号素材),可按分类或关键词过滤。趋势判断由调用方大模型完成。
keyword
keyword_trend_curve
获取关键词在 Google Trends 上的相对热度时间序列(0-100,非绝对搜索量),支持1-5个关键词对比。
platforms
list_platforms
列出可查询的全部热点平台(调用名、中文名、分类、数据来源)
professional
professional_intelligence
Professional Intelligence v3:品牌、公司、商业体、产品、Campaign 的 Entity-first 决策入口。先主动检索主体相关公开证据,再结合生命周期、Source Reliability、Evidence Truth State、异常、6/24/48/72h验证预测、媒体/受众、机会风险与高管报告。品牌/实体研究优先用本工具;纯话题趋势研究才用 analyze_topic;只看当前榜单才用 get_trending。
related
related_queries
获取关键词在 Google Trends 的相关搜索词:top(长期热门)与 rising(近期飙升),用于选题与 SEO/搜索流量。
source
source_reliability
量化数据源稳定性:UP/DEGRADED/DOWN/AUTH_REQUIRED/RATE_LIMITED、24h/7d/30d ok/usable rate、P50/P95延迟、连续失败、schema drift 信号与历史深度。默认只读本地观测;refresh=true 时先真实刷新一次指定平台。
take
take_snapshot
立即对各平台落一次历史快照(也可由系统定时调用以持续监测)。
template
get_template
获取某个模板的完整结构(章节/目的/写作指引/填空位/checklist)。
templates
list_templates
列出内置专家内容模板(短视频分镜脚本/小红书/微博/公众号/X线程/直播脚本/营销方案/内容日历/新品发布/标题钩子)。
trending
get_trending
获取当前原始热点榜单并积累本地快照。只问“现在热什么”时使用;生命周期用 trend_intelligence,完整品牌/预测/风险机会用 professional_intelligence。
upcoming
upcoming_events
查询未来 N 天的趋势节点(科技展会/财报季/政策/电商大促/节假日),含距今天数与预热等级,用于提前布局内容。
workspace
workspace_manage
管理 TrendHub 本地工作区状态:创建/读取 workspace,维护 owner/editor/analyst/viewer 成员、watchlist、saved query、alert rule 与 audit。只写本地数据目录,不修改第三方平台、不自动上传;公网托管 Web 不暴露该变更接口。list/create 不需要 workspace_id,其余 action 必须提供 workspace_id。
xhs
xhs_hot_topics
小红书热点聚合(主打平台):一次性返回官方首页『热门推荐流』笔记(含封面/作者/点赞展示值/原文链接)、由热门标题词频派生的高频话题词(非官方热搜词榜)、当前会话模式(游客/登录)。配置环境变量 XHS_COOKIE 后额外返回官方『热搜词榜』。游客零配置即可用热门推荐流。

Endpoints

URLTransportStateLatencyChecked
https://trendhub-remote-production.up.railway.app/mcp streamable-http answering 406 ms 5 min ago

Alternatives to TrendHub

same job, measured the same way
Agent Wholesale
by despiteryan

Pay-per-call web search, keyword trends, and evidence-backed public-page change intelligence.

3 tools answering
Arkolith
by wikatar

Evidence-backed capital-change intelligence and sourced financial data for AI agents

answering
Lore Context
by lore-context

Governed AI-agent memory, Evidence Ledger traces, evals, and portable context tools.

34 installs/wk local only
Provena Agent Memory
by admiralpunk

Self-hosted MCP memory for AI agents: persistent context with evidence-backed claims.

197 installs/wk local only
Debriefing
by debriefing

Competitive intelligence: tracked competitors, evidence-backed signals, digests and battlecards.

43 tools answering
Paper Lantern
by paperlantern

Research intelligence for AI coding agents. 2M+ CS papers with evidence and tradeoffs.

answering
OpenBtoB
by mrd-bdsmetro

OpenBtoB trade intelligence with 9 MCP tools.

answering
Revnuvo Company Intelligence
by hardeyhemy

Observed company technologies, changes and signals for AI agents, with evidence and confidence.

9 tools answering

TrendHub — questions

Answers built from our own checks of this server.

What can TrendHub do?
It exposes 21 tools, read directly from the server on our last check. Among them: analyze_topic, benchmark_trend_lead, cross_platform_overlap, discover_trending_topics, future_signals, get_content_brief and 15 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is TrendHub working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 92 checks got a reply (0.0%), average response time 406 ms. The bar chart above shows every period we have measured.
The registry lists TrendHub as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect TrendHub?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does TrendHub need an API key?
No. TrendHub completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 21 of them are readable on this page. This is what we observed, not what the docs claim.