TrendHub
REMOTE · TRENDHUB-REMOTE-PRODUCTION.UP.RAILWAY.APP
Evidence-backed AI content studio with 21 stable trend intelligence tools.
Available components
Last scanned (15 hours ago)
Scores higher than 8% of remote servers
Unreachable for 1 day in a row. Last reached 4 Nov 2026.
Category Marketing and SEO
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (3)
- HTTPS
- DNSSEC
- Transport
Checks we could not complete (8)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- TLS certificate in Endpoint SecurityTLS not yet verified: we couldn't open a connection to check the certificate.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 5 Nov 26 0
- Endpoint reachability: not serving MCP → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it. security
- 18 Oct 26 −64
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 16 Oct 26 0
- Stability: 0.97 → pass security
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +3
No change was recorded against any check on this day. Stability & Change Management went from 60 to 80. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Probed https://trendhub-remote-production.up.railway.app/mcp
TLS unreached
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. | DS published | 23684 | 8 | Verified |
| railway.app. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
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 | Unreachable | ||
| http (plaintext) | http://trendhub-remote-production.up.railway.app/mcp | HTTPS enforced |
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 ~99
聚合高质量科技/AI/商业/营销信源的最新文章（未来趋势信号素材），可按分类或关键词过滤。趋势判断由调用方大模型完成。
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | 信源分类；industry=品牌/商业/广告/媒体组合，可用 list_categories 查看；all=全部 |
| keyword | string | – | 按关键词过滤标题/摘要 |
| limit | number | – | – |
No output schema declared.
No examples provided.
get_content_brief 在 TrendHub 内容工作台创作 ~221
围绕主题聚合真实热点证据、相关搜索词、同平台样本与模板，并在内容工作台中调用使用者当前 AI 产出可编辑制品。
| Name | Type | Req | Description |
|---|---|---|---|
| audience | string | – | 目标人群画像 |
| geo | string | – | 搜索趋势地区 |
| goal | string | – | 目标，如 涨粉/带货转化/品牌曝光/线索收集 |
| open_model_review_public_titles | boolean | – | 仅在使用者要求开源模型复核时设为 true；TrendHub 自托管开放权重模型，无需使用者密钥。只处理主题和本次简报中的公开标题。 |
| 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 ~225
小红书热点聚合（主打平台）：一次性返回官方首页『热门推荐流』笔记（含封面/作者/点赞展示值/原文链接）、由热门标题词频派生的高频话题词（非官方热搜词榜）、当前会话模式（游客/登录）。配置环境变量 XHS_COOKIE 后额外返回官方『热搜词榜』。游客零配置即可用热门推荐流。
| Name | Type | Req | Description |
|---|---|---|---|
| focus | string | – | 品牌、Campaign、行业或话题；游客模式会据此收窄推荐流并补充行业公开证据 |
| industry_only | boolean | – | 是否只保留品牌营销、商业运营、广告、媒体相关内容，默认 true |
| limit | number | – | 热门笔记条数，默认30，最多40 |
| topic_limit | number | – | 派生话题词数量，默认20 |
| with_hotlist | boolean | – | 登录态下是否同时取官方热搜词榜，默认 true |
No output schema declared.
No examples provided.
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'
What is the TrendHub MCP server?
TrendHub is an MCP server listed in the public MCP registry as io.github.Zachary-1012/trendhub. Evidence-backed AI content studio with 21 stable trend intelligence tools. This page covers its hosted endpoint (https://trendhub-remote-production.up.railway.app/mcp).
Is the TrendHub MCP server safe to use?
TrendHub scores 23 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,614 tokens of context every time the server is loaded.
Does the TrendHub MCP server require authentication?
Its publisher declares no required credentials for TrendHub. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the TrendHub MCP server still maintained?
TrendHub is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the TrendHub MCP server?
VerifyMCP ran 3 checks on TrendHub, covering HTTPS, DNSSEC and Transport. 8 items could not be completed, a gap on our side rather than a finding about TrendHub: TLS certificate, Authorization, HSTS header, Schema quality and 4 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.