Social Trends Intelligence MCP
Server Details
Trending topics, cross-platform sentiment, viral content, community pulse & brand mentions.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- FoundryNet/social-intel-mcp
- GitHub Stars
- 0
- Server Listing
- social-intel-mcp
TDQS
Scored across 8 tools
Most tools have clearly distinct purposes: brand_mentions targets brand tracking, community_pulse checks community pulse, topic_sentiment analyzes sentiment, trending_topics tracks trends, viral_content finds viral posts. However, trending_topics and viral_content overlap slightly in tracking what's gaining attention, though the former focuses on topics and the latter on specific content. brief_summary and daily_brief are related but priced differently. Overall, agents can distinguish them with careful description reading.
All names use snake_case, but the pattern varies: some are noun_verb (brand_mentions, topic_sentiment), some are adjective_noun (brief_summary, viral_content), and some are noun_noun (community_pulse, daily_brief, trending_topics, mint_info). No consistent verb_noun pattern. The names are still readable but lack a unified convention.
8 tools cover the core functionalities of a social trends intelligence server: brand tracking, community check, sentiment analysis, trending topics, viral content, daily brief, and a summary preview. The count is well-scoped; each tool serves a distinct need without being excessive. The inclusion of mint_info for server metadata is a nice touch.
The tool set covers most common social listening use cases: trend discovery, sentiment, viral tracking, branded mentions, and community analysis. Minor gaps include lack of historical data retrieval, export functionality, or scheduled alerts. However, for a query-only intelligence server, the surface is reasonably complete.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
7 tool updates
- Changed
brand_mentions1 field changed- changed
Input schema / properties / payment_tx / descriptionPrevious value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction reference, when re-calling after a 402."
- Changed
brief_summary1 field changed- changed
Input schema / properties / payment_tx / descriptionPrevious value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction reference, when re-calling after a 402."
- Changed
community_pulse1 field changed- changed
Input schema / properties / payment_tx / descriptionPrevious value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction reference, when re-calling after a 402."
- Changed
daily_brief1 field changed- changed
Input schema / properties / payment_tx / descriptionPrevious value: -"Solana tx signature, when re-calling after a 402 (x402 rail)."New value: +"payment transaction reference, when re-calling after a 402."
- Changed
topic_sentiment1 field changed- changed
Input schema / properties / payment_tx / descriptionPrevious value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction reference, when re-calling after a 402."
- Changed
trending_topics1 field changed- changed
Input schema / properties / payment_tx / descriptionPrevious value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction reference, when re-calling after a 402."
- Changed
viral_content1 field changed- changed
Input schema / properties / payment_tx / descriptionPrevious value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction reference, when re-calling after a 402."
1 tool update
- Added
brief_summary
1 tool update
- Changed
daily_brief2 fields changed- changed
Input schema / properties / payment_tx / descriptionPrevious value: -"Solana tx signature, when re-calling after a 402."New value: +"Solana tx signature, when re-calling after a 402 (x402 rail)." - added
Input schema / properties / stripe_tokenAdded value: +{ + "anyOf": [ + { + "type": "string" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Stripe Checkout Session id (cs_…), when re-calling after\npaying the Stripe payment link (alternative to x402). Can also be\nsupplied via the X-Stripe-Token header." +}
7 tool updates
- First observed
brand_mentions - First observed
community_pulse - First observed
daily_brief - First observed
mint_info - First observed
topic_sentiment - First observed
trending_topics - First observed
viral_content
Related MCP Connectors
AI-powered social listening across Twitter, LinkedIn, Reddit, Facebook, and more.
Social listening analytics — query topics, filters, trending keywords, and conversation clusters.
Cross-platform social media intelligence. Trend volume and growth signals. Free key at trendsmcp.ai
Search brand mentions, track sentiment, and manage monitored keywords across 11 platforms.
Related MCP Servers
- AlicenseAqualityAmaintenanceLive trend data for your AI. 25+ platforms. One connection.8337MIT
- AlicenseAqualityCmaintenanceProvides AI-powered public opinion and trend monitoring with multi-platform aggregation, RSS subscriptions, keyword filtering, translation, sentiment analysis, and trend prediction, all accessible via natural language conversations and able to push alerts to various messaging channels.27GPL 3.0
- AlicenseAqualityCmaintenanceEnables AI-driven public opinion monitoring and trend analysis with multi-platform aggregation, smart alerts, and natural language interaction via MCP.27GPL 3.0

LLM Pulse MCP Serverofficial
AlicenseAqualityBmaintenanceMonitors brand mentions, citations, sentiment, competitor share of voice, and GEO performance across AI search engines.1MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.