{
  "markdown": "# @pipeworx/social-signal\n\nHow much a topic is being discussed across social networks, and how active an account is. Keyless.\n\nPart of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1476+ live data sources.\n\n## Tools\n\n- `social_topic_volume(...)` — post counts for a topic over time, bucketed, across Bluesky, Mastodon, Reddit and Hacker News.\n- `social_account_activity(...)` — posting cadence and engagement for one account on Bluesky or Mastodon.\n\n## Auth\n\nNone.\n\n## Coverage — a directional proxy, not total social volume\n\nCovers **Bluesky, Mastodon, Reddit and Hacker News**. **X/Twitter is excluded** — its API is paid — so results measure a partial slice of social media. Every tool description says this, because \"social volume\" that silently omits the largest network invites a wrong conclusion about a trend.\n\nA network that cannot be reached returns `null` for its buckets rather than `0`. That distinction matters: a measured zero and an unobserved gap are different facts, and Mastodon in particular is often unreachable from Cloudflare egress.\n\n### Per-network quirks handled in-pack\n\n- **Reddit** — `search.rss` prepends subreddit entries (`t5_` ids dated 2010) which faked a 16-year coverage floor; only `t3_`/`t1_` ids are counted.\n- **Hacker News** — Algolia caps pagination at 1,000 and returns `nbHits: 0` past it, so the pack keeps the maximum `nbHits` seen rather than the last.\n- **Bluesky** — burst-throttles at roughly 10 requests refilling ~1/s, so buckets are swept newest-first under a 12-request budget and any gap lands at the far edge of the window.\n\n## Data sources\n\n- Bluesky: `https://public.api.bsky.app`\n- Mastodon: `https://mastodon.social/api/v2/search`\n- Reddit: `https://www.reddit.com/search.rss`\n- Hacker News: `https://hn.algolia.com/api/v1/search`\n\n## Quick Start\n\nAdd to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):\n\n```json\n{\n  \"mcpServers\": {\n    \"social-signal\": {\n      \"url\": \"https://gateway.pipeworx.io/social-signal/mcp\"\n    }\n  }\n}\n```\n\n### What this endpoint actually serves\n\n`tools/list` at `https://gateway.pipeworx.io/social-signal/mcp` returns the tools in the table\nabove **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,\n`discover_tools`, `search_within`, `remember`/`recall` and the rest of the\ngateway-wide set. So the tool count you see is larger than this table: a\nsingle-pack endpoint currently lists roughly 30 shared tools alongside the\npack's own. The connection's `initialize` response states its exact scope, and\nis the authoritative answer for a given day.\n\nThis is deliberate, not multiplexing by accident. The meta-tools are what let a\nscoped connection answer a question this pack does not cover — via\n`ask_pipeworx`, which routes across the whole catalog — without you adding a\nsecond MCP server. There is currently no way to mount a pack endpoint without\nthem; if the extra schemas cost you more context than the routing is worth,\nconnect to the full gateway once rather than to several pack endpoints.\n\nOr connect to the full Pipeworx gateway to get every pack's tools listed\ndirectly, instead of just this one's:\n\n```json\n{\n  \"mcpServers\": {\n    \"pipeworx\": {\n      \"url\": \"https://gateway.pipeworx.io/mcp\"\n    }\n  }\n}\n```\n\nBoth URLs reach the same gateway and the same 1476+ data sources. The\nonly difference is which pack's tools are listed **directly**; `ask_pipeworx`\nreaches all of them from either one.\n\n## Using with ask_pipeworx\n\nInstead of calling tools directly, you can ask questions in plain English —\nthis works on the pack endpoint above as well as on the full gateway:\n\n```\nask_pipeworx({ question: \"your question about Social Signal data\" })\n```\n\nThe gateway picks the right tool and fills the arguments automatically.\n\n## More\n\n- [Docs and guides](https://pipeworx.io/docs)\n- [pipeworx.io](https://pipeworx.io)\n\n## License\n\nMIT\n",
  "bytes": 3871,
  "sha": "901aa9aaec48803af57a49aa7bfd2ebbab0f38384bb7c9807d09e3d7616d3386",
  "repo_slug": "pipeworx-io/mcp-social-signal",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_github_pipeworx_io_social_signal_77161560/readme"
}