future_signals — TrendHub MCP Tool
future_signals
(future signals) is one of 21 tools on the
TrendHub
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call future_signals from your client
- Claude Code TrendHub future_signals run in your project directory
- Claude Desktop TrendHub future_signals ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TrendHub future_signals ~/.cursor/mcp.json
- VS Code TrendHub future_signals .vscode/mcp.json
- Zed TrendHub future_signals ~/.config/zed/settings.json
- Windsurf TrendHub future_signals ~/.codeium/windsurf/mcp_config.json
- Cline TrendHub future_signals ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TrendHub future_signals ~/.gemini/settings.json
- Grok TrendHub future_signals .mcp.json (in your project root)
- ChatGPT TrendHub future_signals Settings → Connectors → Advanced → Developer mode
- Claude.ai TrendHub future_signals Settings → Connectors → Add custom connector
- LangChain TrendHub future_signals pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http trendhub https://trendhub-remote-production.up.railway.app/mcpOther tools on this server
- list_platforms
- list_categories
- get_trending
- xhs_hot_topics
- cross_platform_overlap
- discover_trending_topics
- trend_change_alerts
- take_snapshot
- source_reliability
- keyword_trend_curve
- related_queries
- upcoming_events
- analyze_topic
- trend_intelligence
- benchmark_trend_lead
- list_templates
- get_template
- get_content_brief
- professional_intelligence
- workspace_manage
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.