TrendHub
REMOTE · TRENDHUB-REMOTE-PRODUCTION.UP.RAILWAY.APP · SCANNED SEP 21
Entity-first trend intelligence: 21 MCP tools, fast decision views and evidence.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 5945 tokens (~26/item across 227 items; 21 tools + 206 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 95% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the TrendHub MCP server?
TrendHub is a hosted endpoint at https://trendhub-remote-production.up.railway.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · trendhub-remote-production.up.railway.app
claude mcp add --transport http zachary-1012-trendhub 'https://trendhub-remote-production.up.railway.app/mcp'
{
"mcpServers": {
"zachary-1012-trendhub": {
"url": "https://trendhub-remote-production.up.railway.app/mcp"
}
}
} {
"servers": {
"zachary-1012-trendhub": {
"type": "http",
"url": "https://trendhub-remote-production.up.railway.app/mcp"
}
}
} [mcp_servers.zachary-1012-trendhub] url = "https://trendhub-remote-production.up.railway.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"zachary-1012-trendhub": {
"type": "remote",
"url": "https://trendhub-remote-production.up.railway.app/mcp",
"enabled": true
}
}
} openclaw mcp add zachary-1012-trendhub --url 'https://trendhub-remote-production.up.railway.app/mcp' --transport streamable-http
mcp_servers:
zachary-1012-trendhub:
url: "https://trendhub-remote-production.up.railway.app/mcp" {
"McpServers": {
"zachary-1012-trendhub": {
"Transport": "http",
"Url": "https://trendhub-remote-production.up.railway.app/mcp"
}
}
} assistant mcp add zachary-1012-trendhub -t streamable-http -u 'https://trendhub-remote-production.up.railway.app/mcp'
{
"mcpServers": {
"zachary-1012-trendhub": {
"type": "http",
"url": "https://trendhub-remote-production.up.railway.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 0
- Server version: 1.7.3 → 1.7.4 functional
- Server version: 1.7.1 → 1.7.3 functional
- 20 Sept 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “analyze_topic” rewrote its description, which is the text the model reads security
- Tool “get_trending” rewrote its description, which is the text the model reads security
- Tool “professional_intelligence” rewrote its description, which is the text the model reads security
- Tool “trend_intelligence” rewrote its description, which is the text the model reads security
- Tool “workspace_manage” rewrote its description, which is the text the model reads security
- Schema quality: 45 → 26 ▲ functional
- Schema quality: 45 → 25 ▲ functional
- Tool coverage: 80% → 95% ▲ functional
- New resource “36氪” functional
- New resource “Ad Age” functional
- New resource “Adweek” functional
- New resource “Allure” functional
- New resource “Amazon” functional
- New resource “Apple Podcasts” functional
- New resource “Associated Press / AP” functional
- New resource “BBC” functional
- New resource “Bing News/Search” functional
- New resource “Bloomberg” functional
- New resource “Bluesky” functional
- New resource “Brand / company owned domains” functional
- New resource “Business Insider” functional
- New resource “CNBC” functional
- New resource “Campaign” functional
- New resource “Common Crawl” functional
- New resource “Discord public/authorized communities” functional
- New resource “ELLE” functional
- New resource “ELLE China” functional
- New resource “Facebook” functional
- New resource “FashionNetwork.com” functional
- New resource “Financial Times” functional
- New resource “Forbes” functional
- New resource “Fortune” functional
- New resource “GDELT” functional
- New resource “GQ” functional
- New resource “GQ China / 智族GQ” functional
- New resource “GitHub Trending” functional
- New resource “Glossy” functional
- New resource “Google News” functional
- New resource “Google Trending Now” functional
- New resource “Google Trends” functional
- New resource “Hacker News” functional
- New resource “Harper's BAZAAR” functional
- New resource “Highsnobiety” functional
- New resource “Hypebeast” functional
- New resource “Hypebeast 中文” functional
- New resource “IT之家” functional
- New resource “Instagram” functional
- New resource “Jing Daily” functional
- New resource “Kakao ecosystem” functional
- New resource “LADYMAX” functional
- New resource “LINE” functional
- New resource “Lemon8” functional
- New resource “LinkedIn” functional
- New resource “Luxe.CO / 华丽志” functional
- New resource “Marketing-Interactive” functional
- New resource “Morketing” functional
- New resource “NAVER Search/DataLab” functional
- New resource “Pinterest” functional
- New resource “Podcast Index” functional
- New resource “Product Hunt” functional
- New resource “Public RSS / Atom” functional
- New resource “QQ” functional
- New resource “QQ空间 / Qzone” functional
- New resource “QQ音乐播客” functional
- New resource “Reddit” functional
- New resource “Reuters” functional
- New resource “Snapchat” functional
- New resource “SocialBeta” functional
- New resource “Spotify Podcasts” functional
- New resource “TechCrunch” functional
- New resource “Telegram public channels” functional
- New resource “The Business of Fashion” functional
- New resource “The Guardian” functional
- New resource “The New York Times” functional
- New resource “The Verge” functional
- New resource “The Wall Street Journal” functional
- New resource “Threads” functional
- New resource “TikTok” functional
- New resource “Twitch” functional
- New resource “VOGUE China” functional
- New resource “Vogue” functional
- New resource “Vogue Business” functional
- New resource “WARC” functional
- New resource “WIRED” functional
- New resource “WWD” functional
- New resource “WhatsApp Channels” functional
- New resource “X” functional
- New resource “YouTube” functional
- New resource “YouTube Podcasts” functional
- New resource “evidence-contract” functional
- New resource “namespace” functional
- New resource “skill-contract” functional
- New resource “trendhub.apps.evidence_explorer” functional
- New resource “trendhub.apps.source_health” functional
- New resource “trendhub.apps.trend_radar” functional
- New resource “trendhub.content.build_brief” functional
- New resource “trendhub.discovery.platforms” functional
- New resource “trendhub.discovery.trending” functional
- New resource “trendhub.history.topic” functional
- New resource “trendhub.intelligence.cross_signal” functional
- New resource “trendhub.intelligence.lifecycle” functional
- New resource “trendhub.intelligence.professional” functional
- New resource “trendhub.intelligence.topic_research” functional
- New resource “trendhub.reliability.source_health” functional
- New resource “trendhub.research.deep_topic” functional
- New resource “trendhub.resources.evidence_contract” functional
- New resource “trendhub.resources.namespace” functional
- New resource “trendhub.resources.skill” functional
- New resource “trendhub.resources.source_contract” functional
- New resource “trendhub.tasks.async_intelligence” functional
- New resource “trendhub.workspace.local” functional
- New resource “上海证券报” functional
- New resource “中国新闻网 / China News Service” functional
- New resource “京东” functional
- New resource “人民日报 / People's Daily” functional
- New resource “今日头条” functional
- New resource “企业微信 / WeCom” functional
- New resource “哔哩哔哩” functional
- New resource “喜马拉雅” functional
- New resource “嘉人 Marie Claire China” functional
- New resource “大众点评” functional
- New resource “天猫” functional
- New resource “央视新闻 / CCTV News” functional
- New resource “小宇宙播客” functional
- New resource “小红书” functional
- New resource “广告门” functional
- New resource “微信公众号” functional
- New resource “微信小程序” functional
- New resource “微信指数” functional
- New resource “微信视频号” functional
- New resource “微博” functional
- New resource “快手” functional
- New resource “抖音” functional
- New resource “搜狗搜索” functional
- New resource “数英 Digitaling” functional
- New resource “新华社 / Xinhua” functional
- New resource “新浪新闻” functional
- New resource “时尚芭莎 / Harper's BAZAAR China” functional
- New resource “晚点 LatePost” functional
- New resource “澎湃新闻” functional
- New resource “界面新闻” functional
- New resource “百度指数” functional
- New resource “百度热搜” functional
- New resource “百度贴吧” functional
- New resource “百度资讯/新闻” functional
- New resource “知乎” functional
- New resource “第一财经” functional
- New resource “网易云音乐播客” functional
- New resource “网易新闻” functional
- New resource “美团” functional
- New resource “腾讯新闻” functional
- New resource “荔枝” functional
- New resource “虎嗅” functional
- New resource “虎扑” functional
- New resource “证券时报” functional
- New resource “豆瓣” functional
- New resource “财新” functional
- New resource “酷安” functional
- New resource “钛媒体” functional
- Server version: 1.6.1 → 1.7.1 functional
- Server version: 1.5.3 → 1.6.1 functional
- Server version: 1.5.2 → 1.5.3 functional
- “professional_intelligence” added an optional parameter “days_ahead” cosmetic
- “professional_intelligence” added an optional parameter “geo” cosmetic
- “professional_intelligence” added an optional parameter “timeframe” cosmetic
- “professional_intelligence” reworded the description of “keyword” cosmetic
- “workspace_manage” reworded the description of “action” cosmetic
- “workspace_manage” reworded the description of “enabled” cosmetic
- “workspace_manage” reworded the description of “geo” cosmetic
- “workspace_manage” reworded the description of “limit” cosmetic
- “workspace_manage” reworded the description of “member_principal” cosmetic
- “workspace_manage” reworded the description of “name” cosmetic
- “workspace_manage” reworded the description of “platforms” cosmetic
- “workspace_manage” reworded the description of “role” cosmetic
- “workspace_manage” reworded the description of “workspace_id” cosmetic
- 19 Sept 26 0
- Schema quality: 51 → 45 ▲ functional
- New resource “Apple Podcasts public catalog history” functional
- New resource “Ars Technica history” functional
- New resource “Bluesky public search history” functional
- New resource “GDELT global news history” functional
- New resource “Search Engine Land history” functional
- New resource “Social Media Today history” functional
- New resource “Solidot history” functional
- New resource “Stratechery history” functional
- New resource “TechCrunch history” functional
- New resource “The Verge history” functional
- New resource “WIRED history” functional
- New resource “cnBeta history” functional
- New resource “极客公园 history” functional
- 18 Sept 26 +3
We did not load change detail this far back for this component, so this day may have recorded more than is shown.
- Schema quality: fail → pass ▲ functional
- First check of Schema quality: 100 functional
- New resource “36氪 history” functional
- New resource “51CTO history” functional
- New resource “B站热门 history” functional
- New resource “CSDN history” functional
- “discover_trending_topics” added an optional parameter “topic” cosmetic
- 17 Sept 26 −1
We did not load change detail this far back for this component, so this day may have recorded more than is shown.
- 16 Sept 26 72
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://trendhub-remote-production.up.railway.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6da79bb561da3efeb0e751ca21abd3999fe |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of trendhub-remote-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://trendhub-remote-production.up.railway.app/mcp | Verified | 200 | |
| http (plaintext) | http://trendhub-remote-production.up.railway.app/mcp | HTTPS enforced | 301 | https://trendhub-remote-production.up.railway.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
analyze_topic ~104
话题研究包：聚合当前共振、搜索曲线/动量、相关词、未来信号、节点与规则情感；需要多年度生命周期、验证预测、品牌实体或高管报告时使用 professional_intelligence。
| Name | Type | Req | Description |
|---|---|---|---|
| geo | string | – | Google Trends 地区，留空全球 |
| keyword | string | yes | 要分析的话题 |
| timeframe | string | – | 趋势时间窗，默认 today 3-m |
No output schema declared.
No examples provided.
benchmark_trend_lead ~149
真实场景 Lead-time Benchmark：把 TrendHub 本地历史的最早命中，与用户提供的外部事实 reference_time 对比，计算是否提前24h/72h发现。reference_time 必须来自官方公告、主流爆发点或团队约定的外部 ground truth，TrendHub 不会自己编造基准时间。
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | yes | Benchmark 话题/关键词 |
| platforms | string | – | 可选平台；默认核心平台 |
| reference_time | string | yes | 外部 ground-truth ISO-8601 时间，例如 2026-09-20T09:00:00+08:00 |
No output schema declared.
No examples provided.
cross_platform_overlap ~102
分析某个关键词/话题当前在多少个平台同时上榜（跨平台共振），给出各平台命中条目、最佳排名与共振分。用于判断一个话题是否具备全网热度。
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | yes | 关键词或话题，如 'AI眼镜'、'英伟达' |
| platforms | string | – | 可选，限定平台调用名，逗号分隔 |
No output schema declared.
No examples provided.
discover_trending_topics ~111
无需关键词，自动聚类发现当前在多个平台共振的话题（基于标题相似度，结果需大模型复核归纳）。
| Name | Type | Req | Description |
|---|---|---|---|
| min_platforms | number | – | 至少在几个平台出现，默认2 |
| platforms | string | – | 可选，限定平台，逗号分隔 |
| topic | string | – | 可选，按话题/关键词筛选聚类结果；支持品牌、campaign、行业议题或平台标签 |
No output schema declared.
No examples provided.
future_signals ~88
聚合高质量科技/AI/商业/营销信源的最新文章（未来趋势信号素材），可按分类或关键词过滤。趋势判断由调用方大模型完成。
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | 信源分类，可用 list_categories 查看；all=全部 |
| keyword | string | – | 按关键词过滤标题/摘要 |
| limit | number | – | – |
No output schema declared.
No examples provided.
get_content_brief ~200
专家创作简报：围绕主题聚合真实热点证据、相关搜索词、情感信号、同平台真实爆款样本，并匹配模板，输出逐格填充指引与可直接交给大模型的 productionPrompt。脚本/文案/方案的成稿由调用方大模型完成。
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | 目标人群画像 |
| geo | string | – | 搜索趋势地区 |
| goal | string | – | 目标，如 涨粉/带货转化/品牌曝光/线索收集 |
| platform | string | – | 目标平台，如 douyin/xiaohongshu/weibo/wechat/twitter/douyin-live；all=通用 |
| template_id | string | – | 模板 id；不传则按 platform 自动匹配 |
| topic | string | yes | 创作主题/要蹭的热点 |
No output schema declared.
No examples provided.
get_template ~55
获取某个模板的完整结构（章节/目的/写作指引/填空位/checklist）。
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 模板 id，如 short-video-script / xiaohongshu-note / marketing-plan |
No output schema declared.
No examples provided.
get_trending ~116
获取当前原始热点榜单并积累本地快照。只问“现在热什么”时使用；生命周期用 trend_intelligence，完整品牌/预测/风险机会用 professional_intelligence。
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | 分类：social/video/news/tech/dev/ai/global |
| limit | number | – | 每个平台返回条数，默认20 |
| platform | string | – | 平台调用名，多个用逗号分隔，如 weibo,zhihu,bilibili,hackernews |
No output schema declared.
No examples provided.
keyword_trend_curve ~126
获取关键词在 Google Trends 上的相对热度时间序列（0-100，非绝对搜索量），支持1-5个关键词对比。
| Name | Type | Req | Description |
|---|---|---|---|
| geo | string | – | 地区代码，US/CN/TW/HK，留空=全球 |
| keywords | string | yes | 关键词，多个用逗号分隔，如 'AI眼镜,VR头显' |
| timeframe | string | – | 如 today 1-m / today 3-m / today 12-m / now 7-d，默认 today 12-m |
No output schema declared.
No examples provided.
list_categories ~19
列出平台分类与内容/模板分类
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_platforms ~30
列出可查询的全部热点平台（调用名、中文名、分类、数据来源）
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_templates ~93
列出内置专家内容模板（短视频分镜脚本/小红书/微博/公众号/X线程/直播脚本/营销方案/内容日历/新品发布/标题钩子）。
| Name | Type | Req | Description |
|---|---|---|---|
| platform | string | – | 平台，如 douyin/xiaohongshu/weibo/wechat/twitter |
| type | string | – | script=脚本 copy=文案 plan=方案 |
No output schema declared.
No examples provided.
professional_intelligence ~324
Professional Intelligence v3：品牌、公司、商业体、产品、Campaign 的 Entity-first 决策入口。先主动检索主体相关公开证据，再结合生命周期、Source Reliability、Evidence Truth State、异常、6/24/48/72h验证预测、媒体/受众、机会风险与高管报告。品牌/实体研究优先用本工具；纯话题趋势研究才用 analyze_topic；只看当前榜单才用 get_trending。
| Name | Type | Req | Description |
|---|---|---|---|
| days_ahead | number | – | 未来节点窗口，默认60天 |
| geo | string | – | Entity-first 搜索趋势地区，默认 CN；如 CN/HK/US |
| keyword | string | yes | 要研究的品牌、公司、商业体、产品、Campaign 或商业主体，例如 广州太古汇 / LV / 小米 / Tesla |
| platforms | string | – | 可选平台调用名，逗号分隔；留空时由专业 Source Planner 自动选择零配置核心源 |
| refresh | boolean | – | 是否先刷新当前公开数据，默认 true |
| report | string | – | 附带高管报告格式，默认 json |
| timeframe | string | – | Entity-first 搜索趋势时间窗，默认 today 3-m |
| verticals | string | – | 可选行业/场景，逗号分隔：fashion-luxury,beauty,business-corporate,technology,automotive,finance-markets,marketing-advertising,retail-commerce,culture-entertainment |
No output schema declared.
No examples provided.
related_queries ~55
获取关键词在 Google Trends 的相关搜索词：top（长期热门）与 rising（近期飙升），用于选题与 SEO/搜索流量。
| Name | Type | Req | Description |
|---|---|---|---|
| geo | string | – | – |
| keyword | string | yes | – |
No output schema declared.
No examples provided.
source_reliability ~120
量化数据源稳定性：UP/DEGRADED/DOWN/AUTH_REQUIRED/RATE_LIMITED、24h/7d/30d ok/usable rate、P50/P95延迟、连续失败、schema drift 信号与历史深度。默认只读本地观测；refresh=true 时先真实刷新一次指定平台。
| Name | Type | Req | Description |
|---|---|---|---|
| platforms | string | – | 平台调用名，逗号分隔；默认核心平台 |
| refresh | boolean | – | 是否先联网刷新一次，默认 false |
No output schema declared.
No examples provided.
take_snapshot ~49
立即对各平台落一次历史快照（也可由系统定时调用以持续监测）。
| Name | Type | Req | Description |
|---|---|---|---|
| platforms | string | – | 可选，限定平台，逗号分隔 |
No output schema declared.
No examples provided.
trend_change_alerts ~82
对比历史快照，输出各平台新晋上榜、排名飙升(≥3位)、掉榜的话题。需要先有两次以上快照（get_trending 会自动积累，或用 take_snapshot）。
| Name | Type | Req | Description |
|---|---|---|---|
| platforms | string | – | 可选，限定平台，逗号分隔；默认核心平台 |
No output schema declared.
No examples provided.
trend_intelligence ~119
轻量纵向 Trend Intelligence：基于本地真实历史计算生命周期、速度、持续性、扩散、Source Reliability 与确定性置信度；品牌实体、媒体、异常/预测、告警和报告请用 professional_intelligence。历史不足返回 insufficient_history。
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | yes | 要评估生命周期的关键词/话题 |
| platforms | string | – | 可选平台，逗号分隔；默认核心平台 |
| refresh | boolean | – | 是否先刷新当前数据，默认 true |
No output schema declared.
No examples provided.
upcoming_events ~90
查询未来 N 天的趋势节点（科技展会/财报季/政策/电商大促/节假日），含距今天数与预热等级，用于提前布局内容。
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | 节点分类，如 tech-event/earnings/ecommerce/holiday-cn/policy |
| days_ahead | number | – | 未来天数窗口，默认90 |
No output schema declared.
No examples provided.
workspace_manage ~325
管理 TrendHub 本地工作区状态：创建/读取 workspace，维护 owner/editor/analyst/viewer 成员、watchlist、saved query、alert rule 与 audit。只写本地数据目录，不修改第三方平台、不自动上传；公网托管 Web 不暴露该变更接口。list/create 不需要 workspace_id，其余 action 必须提供 workspace_id。
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | 操作：list/create/get/member_set/watchlist_set/query_save/rule_save/audit |
| enabled | boolean | – | rule_save 是否启用，默认 true |
| geo | string | – | query_save 的地区/geo 过滤 |
| keywords | string | – | watchlist 关键词，逗号分隔 |
| limit | number | – | audit 返回条数，默认 200，最大 1000 |
| member_principal | string | – | member_set 要新增/更新的非敏感 principal |
| name | string | – | create 的工作区名，或 saved query / alert rule 的显示名 |
| platforms | string | – | query_save 的平台调用名，逗号分隔 |
| principal | string | yes | 本地身份映射，例如 local-owner 或公司 SSO 映射后的非敏感 principal |
| query | string | – | query_save 时的关键词 |
| role | string | – | member_set 的目标角色 |
| rule_json | string | – | rule_save 的 JSON 规则对象 |
| workspace_id | string | – | 工作区 ID；除 list/create 外均必填 |
No output schema declared.
No examples provided.
xhs_hot_topics ~165
小红书热点聚合（主打平台）：一次性返回官方首页『热门推荐流』笔记（含封面/作者/点赞展示值/原文链接）、由热门标题词频派生的高频话题词（非官方热搜词榜）、当前会话模式（游客/登录）。配置环境变量 XHS_COOKIE 后额外返回官方『热搜词榜』。游客零配置即可用热门推荐流。
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | 热门笔记条数，默认30，最多40 |
| topic_limit | number | – | 派生话题词数量，默认20 |
| with_hotlist | boolean | – | 登录态下是否同时取官方热搜词榜，默认 true |
No output schema declared.
No examples provided.
What is the TrendHub MCP server?
TrendHub is an MCP server listed in the public MCP registry as io.github.Zachary-1012/trendhub. Entity-first trend intelligence: 21 MCP tools, fast decision views and evidence. This page covers its hosted endpoint (https://trendhub-remote-production.up.railway.app/mcp).
Is the TrendHub MCP server safe to use?
TrendHub scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the TrendHub MCP server expose?
TrendHub exposes 21 tools: list_platforms, list_categories, get_trending, xhs_hot_topics, cross_platform_overlap, and 16 more. Their descriptions and schemas cost roughly 2,522 tokens of context every time the server is loaded.
Does the TrendHub MCP server require authentication?
No. We connected to TrendHub without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the TrendHub MCP server still maintained?
TrendHub is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.