Search arXiv papers, download full text, semantic search, citation graphs, and alerts via MCP.
TrendHub is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Evidence-first trend intelligence across 38 public sources with 19 MCP tools and lead benchmarks.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http trendhub-mcp https://trendhub-remote-production.up.railway.app/mcp
# 2 — ask your agent for something these tools do
# list_platforms, list_categories, get_trending and 18 more
TrendHub costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http trendhub-mcp https://trendhub-remote-production.up.railway.app/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
21 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
列出可查询的全部热点平台(调用名、中文名、分类、数据来源)
No parameter schema on file.
列出平台分类与内容/模板分类
No parameter schema on file.
获取当前原始热点榜单并积累本地快照。只问“现在热什么”时使用;生命周期用 trend_intelligence,完整品牌/预测/风险机会用 professional_intelligence。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| platform | string | no | 平台调用名,多个用逗号分隔,如 weibo,zhihu,bilibili,hackernews |
| category | string | no | 分类:social/video/news/tech/dev/ai/global |
| limit | number | no | 每个平台返回条数,默认20 |
小红书热点聚合(主打平台):一次性返回官方首页『热门推荐流』笔记(含封面/作者/点赞展示值/原文链接)、由热门标题词频派生的高频话题词(非官方热搜词榜)、当前会话模式(游客/登录)。配置环境变量 XHS_COOKIE 后额外返回官方『热搜词榜』。游客零配置即可用热门推荐流。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | number | no | 热门笔记条数,默认30,最多40 |
| topic_limit | number | no | 派生话题词数量,默认20 |
| with_hotlist | boolean | no | 登录态下是否同时取官方热搜词榜,默认 true |
| focus | string | no | 品牌、Campaign、行业或话题;游客模式会据此收窄推荐流并补充行业公开证据 |
| industry_only | boolean | no | 是否只保留品牌营销、商业运营、广告、媒体相关内容,默认 true |
分析某个关键词/话题当前在多少个平台同时上榜(跨平台共振),给出各平台命中条目、最佳排名与共振分。用于判断一个话题是否具备全网热度。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keyword | string | yes | 关键词或话题,如 'AI眼镜'、'英伟达' |
| platforms | string | no | 可选,限定平台调用名,逗号分隔 |
无需关键词,自动聚类发现当前在多个平台共振的话题(基于标题相似度,结果需大模型复核归纳)。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| min_platforms | number | no | 至少在几个平台出现,默认2 |
| platforms | string | no | 可选,限定平台,逗号分隔 |
| topic | string | no | 可选,按话题/关键词筛选聚类结果;支持品牌、campaign、行业议题或平台标签 |
对比历史快照,输出各平台新晋上榜、排名飙升(≥3位)、掉榜的话题。需要先有两次以上快照(get_trending 会自动积累,或用 take_snapshot)。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| platforms | string | no | 可选,限定平台,逗号分隔;默认核心平台 |
立即对各平台落一次历史快照(也可由系统定时调用以持续监测)。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| platforms | string | no | 可选,限定平台,逗号分隔 |
量化数据源稳定性:UP/DEGRADED/DOWN/AUTH_REQUIRED/RATE_LIMITED、24h/7d/30d ok/usable rate、P50/P95延迟、连续失败、schema drift 信号与历史深度。默认只读本地观测;refresh=true 时先真实刷新一次指定平台。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| platforms | string | no | 平台调用名,逗号分隔;默认核心平台 |
| refresh | boolean | no | 是否先联网刷新一次,默认 false |
获取关键词在 Google Trends 上的相对热度时间序列(0-100,非绝对搜索量),支持1-5个关键词对比。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keywords | string | yes | 关键词,多个用逗号分隔,如 'AI眼镜,VR头显' |
| geo | string | no | 地区代码,US/CN/TW/HK,留空=全球 |
| timeframe | string | no | 如 today 1-m / today 3-m / today 12-m / now 7-d,默认 today 12-m |
获取关键词在 Google Trends 的相关搜索词:top(长期热门)与 rising(近期飙升),用于选题与 SEO/搜索流量。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keyword | string | yes | — |
| geo | string | no | — |
聚合高质量科技/AI/商业/营销信源的最新文章(未来趋势信号素材),可按分类或关键词过滤。趋势判断由调用方大模型完成。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | 信源分类;industry=品牌/商业/广告/媒体组合,可用 list_categories 查看;all=全部 |
| keyword | string | no | 按关键词过滤标题/摘要 |
| limit | number | no | — |
查询未来 N 天的趋势节点(科技展会/财报季/政策/电商大促/节假日),含距今天数与预热等级,用于提前布局内容。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| days_ahead | number | no | 未来天数窗口,默认90 |
| category | string | no | 节点分类,如 tech-event/earnings/ecommerce/holiday-cn/policy |
话题研究包:聚合当前共振、搜索曲线/动量、相关词、未来信号、节点与规则情感;需要多年度生命周期、验证预测、品牌实体或高管报告时使用 professional_intelligence。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keyword | string | yes | 要分析的话题 |
| geo | string | no | Google Trends 地区,留空全球 |
| timeframe | string | no | 趋势时间窗,默认 today 3-m |
轻量纵向 Trend Intelligence:基于本地真实历史计算生命周期、速度、持续性、扩散、Source Reliability 与确定性置信度;品牌实体、媒体、异常/预测、告警和报告请用 professional_intelligence。历史不足返回 insufficient_history。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keyword | string | yes | 要评估生命周期的关键词/话题 |
| platforms | string | no | 可选平台,逗号分隔;默认核心平台 |
| refresh | boolean | no | 是否先刷新当前数据,默认 true |
真实场景 Lead-time Benchmark:把 TrendHub 本地历史的最早命中,与用户提供的外部事实 reference_time 对比,计算是否提前24h/72h发现。reference_time 必须来自官方公告、主流爆发点或团队约定的外部 ground truth,TrendHub 不会自己编造基准时间。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keyword | string | yes | Benchmark 话题/关键词 |
| reference_time | string | yes | 外部 ground-truth ISO-8601 时间,例如 2026-09-20T09:00:00+08:00 |
| platforms | string | no | 可选平台;默认核心平台 |
列出内置专家内容模板(短视频分镜脚本/小红书/微博/公众号/X线程/直播脚本/营销方案/内容日历/新品发布/标题钩子)。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | no | script=脚本 copy=文案 plan=方案 |
| platform | string | no | 平台,如 douyin/xiaohongshu/weibo/wechat/twitter |
获取某个模板的完整结构(章节/目的/写作指引/填空位/checklist)。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | 模板 id,如 short-video-script / xiaohongshu-note / marketing-plan |
围绕主题聚合真实热点证据、相关搜索词、同平台样本与模板,并在内容工作台中调用使用者当前 AI 产出可编辑制品。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | yes | 创作主题/要蹭的热点 |
| template_id | string | no | 模板 id;不传则按 platform 自动匹配 |
| platform | string | no | 目标平台,如 douyin/xiaohongshu/weibo/wechat/twitter/douyin-live;all=通用 |
| goal | string | no | 目标,如 涨粉/带货转化/品牌曝光/线索收集 |
| audience | string | no | 目标人群画像 |
| geo | string | no | 搜索趋势地区 |
| open_model_review_public_titles | boolean | no | 仅在使用者要求开源模型复核时设为 true;TrendHub 自托管开放权重模型,无需使用者密钥。只处理主题和本次简报中的公开标题。 |
Professional Intelligence v3:品牌、公司、商业体、产品、Campaign 的 Entity-first 决策入口。先主动检索主体相关公开证据,再结合生命周期、Source Reliability、Evidence Truth State、异常、6/24/48/72h验证预测、媒体/受众、机会风险与高管报告。品牌/实体研究优先用本工具;纯话题趋势研究才用 analyze_topic;只看当前榜单才用 get_trending。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| keyword | string | yes | 要研究的品牌、公司、商业体、产品、Campaign 或商业主体,例如 广州太古汇 / LV / 小米 / Tesla |
| platforms | string | no | 可选平台调用名,逗号分隔;留空时由专业 Source Planner 自动选择零配置核心源 |
| verticals | string | no | 可选行业/场景,逗号分隔:fashion-luxury,beauty,business-corporate,technology,automotive,finance-markets,marketing-advertising,retail-commerce,culture-entertainment |
| refresh | boolean | no | 是否先刷新当前公开数据,默认 true |
| geo | string | no | Entity-first 搜索趋势地区,默认 CN;如 CN/HK/US |
| timeframe | string | no | Entity-first 搜索趋势时间窗,默认 today 3-m |
| days_ahead | number | no | 未来节点窗口,默认60天 |
| report | string | no | 附带高管报告格式,默认 json |
管理 TrendHub 本地工作区状态:创建/读取 workspace,维护 owner/editor/analyst/viewer 成员、watchlist、saved query、alert rule 与 audit。只写本地数据目录,不修改第三方平台、不自动上传;公网托管 Web 不暴露该变更接口。list/create 不需要 workspace_id,其余 action 必须提供 workspace_id。
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | string | yes | 操作:list/create/get/member_set/watchlist_set/query_save/rule_save/audit |
| principal | string | yes | 本地身份映射,例如 local-owner 或公司 SSO 映射后的非敏感 principal |
| workspace_id | string | no | 工作区 ID;除 list/create 外均必填 |
| name | string | no | create 的工作区名,或 saved query / alert rule 的显示名 |
| member_principal | string | no | member_set 要新增/更新的非敏感 principal |
| role | string | no | member_set 的目标角色 |
| keywords | string | no | watchlist 关键词,逗号分隔 |
| query | string | no | query_save 时的关键词 |
| platforms | string | no | query_save 的平台调用名,逗号分隔 |
| geo | string | no | query_save 的地区/geo 过滤 |
| rule_json | string | no | rule_save 的 JSON 规则对象 |
| enabled | boolean | no | rule_save 是否启用,默认 true |
| limit | number | no | audit 返回条数,默认 200,最大 1000 |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install TrendHub or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 2.0.4.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish TrendHub can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.