Skip to main content

Social Trends Intelligence MCP

by io.github.FoundryNet

Server Details

Trending topics, cross-platform sentiment, viral content, community pulse & brand mentions.

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Unhealthy
Last Tested: 2026-09-06 07:42
Transport: Streamable HTTP
URL
Repository: FoundryNet/social-intel-mcp
GitHub Stars: 0
Server Listing: social-intel-mcp

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

7 tool updatesJul 16, 2026

Changedbrand_mentions1 field changed

changedInput schema / properties / payment_tx / description

Previous value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction reference, when re-calling after a 402."

Changedbrief_summary1 field changed

changedInput schema / properties / payment_tx / description

Previous value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction reference, when re-calling after a 402."

Changedcommunity_pulse1 field changed

changedInput schema / properties / payment_tx / description

Previous value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction reference, when re-calling after a 402."

Changeddaily_brief1 field changed

changedInput schema / properties / payment_tx / description

Previous value: -"Solana tx signature, when re-calling after a 402 (x402 rail)."New value: +"payment transaction reference, when re-calling after a 402."

Changedtopic_sentiment1 field changed

changedInput schema / properties / payment_tx / description

Previous value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction reference, when re-calling after a 402."

Changedtrending_topics1 field changed

changedInput schema / properties / payment_tx / description

Previous value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction reference, when re-calling after a 402."

Changedviral_content1 field changed

changedInput schema / properties / payment_tx / description

Previous value: -"Solana tx signature, when re-calling after a 402."New value: +"payment transaction reference, when re-calling after a 402."

1 tool updateJun 22, 2026
- Addedbrief_summary

1 tool updateJun 21, 2026

Changeddaily_brief2 fields changed

changedInput schema / properties / payment_tx / description

Previous value: -"Solana tx signature, when re-calling after a 402."New value: +"Solana tx signature, when re-calling after a 402 (x402 rail)."

addedInput schema / properties / stripe_token

Added 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 updatesJun 19, 2026
- First observedbrand_mentions
- First observedcommunity_pulse
- First observeddaily_brief
- First observedmint_info
- First observedtopic_sentiment
- First observedtrending_topics
- First observedviral_content

Frequently Asked Questions

Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.

Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
- GitHub identity — fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
- HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
- DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.

The HTTP ownership file has this structure:

{
  "$schema": "https://glama.ai/mcp/schemas/connector.json",
  "claim": "glama_claim_..."
}

Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.

If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.

For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.

Discussions

No comments yet. Be the first to start the discussion!

Login with GitHub to comment

Related MCP Connectors

PitchGhostOAuth
io.github.PitchGhost
AI-powered social listening across Twitter, LinkedIn, Reddit, Facebook, and more.
Social Media Marketing Research & Data
2
affogataOAuth
com.affogata.app
Social listening analytics — query topics, filters, trending keywords, and conversation clusters.
Social Media Marketing
2
Social Media Intelligence MCP
ai.trendsmcp
Cross-platform social media intelligence. Trend volume and growth signals. Free key at trendsmcp.ai
Social Media Research & Data
237
ParahumanOAuth
co.parahuman
Search brand mentions, track sentiment, and manage monitored keywords across 11 platforms.
1

Related MCP Servers

Trends MCP
Search Research & Data
trendsmcp-ai
A
license
A
quality
A
maintenance
Live trend data for your AI. 25+ platforms. One connection.
Updated 8 days ago (2026-08-29 16:28 UTC)
8
3
37
MIT
TrendRadar MCP
AI & Machine Learning Marketing Communication
AY08siliang
A
license
A
quality
C
maintenance
Provides 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.
Updated 10 days ago (2026-08-27 03:50 UTC)
27
GPL 3.0
TrendRadar
15642875149
A
license
A
quality
C
maintenance
Enables AI-driven public opinion monitoring and trend analysis with multi-platform aggregation, smart alerts, and natural language interaction via MCP.
Updated 16 days ago (2026-08-21 12:07 UTC)
27
GPL 3.0
LLM Pulse MCP Serverofficial
Marketing Search
LLM-Pulse
A
license
A
quality
B
maintenance
Monitors brand mentions, citations, sentiment, competitor share of voice, and GEO performance across AI search engines.
Updated 6 days ago (2026-08-31 12:10 UTC)
1
MIT

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.1/5.0

Disambiguation4/5

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.

Naming Consistency3/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Resources