Social Signal
NPM · @PIPEWORX/MCP-SOCIAL-SIGNAL · 2 COMPONENTS
Social Signal — post-VOLUME TIME SERIES across the open social networks that can be read without…
Available components
Last scanned (7 hours ago)
Scores higher than 68% of npm servers
Category News and Social
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-social-signal). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 767 tokens (~383/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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 +3
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.23 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 78
First indexed and scored.
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 · Analysed npm/@pipeworx/mcp-social-signal@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-social-signal |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-social-signal/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3692354067 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:86789f182d4dce4f48883ef7449fcf01d2920c7d17e673a8f9c0f6741c8774e9cdc2e897b96aee679515bdee7ddc8e965ffff564777d831463f2a8383 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
social_account_activity ~303
POSTING CADENCE for one social media account as a TIME SERIES: posts per day over a window, plus average engagement per post and the timestamp of the most recent post. Answers "how often does this account post", "has this account gone quiet", "what is their POST VOLUME TREND", "how active is @someone on social media". The network is inferred from the handle shape (a dotted handle is Bluesky, "@user@instance.tld" is Mastodon, "u/name" is Reddit); when the shape is ambiguous the response lists every network tried in networks_tried. Days with a null count were outside the reach of the feed and stay distinguishable from days with a measured zero. Coverage is Bluesky, Mastodon, Reddit and Hacker News; X/Twitter is excluded (paid API), so results are a directional proxy over a partial slice of social media rather than total social volume. Examples: handle "bsky.app", days 30 for a month of posting cadence; handle "@Mastodon@mastodon.social", days 90 for a long-run activity check.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | How many days of cadence to report. Default 30, maximum 90. |
| handle | string | yes | The account handle. Bluesky: "user.bsky.social" or a did:. Mastodon: "@user@mastodon.social". Reddit: "u/name". A bare name is tried against each in turn. |
No output schema declared.
No examples provided.
social_topic_volume ~410
SOCIAL MEDIA VOLUME as a TIME SERIES: how many posts mention a topic, bucketed by day or hour, so you can see the POST VOLUME TREND and whether SOCIAL CHATTER ABOUT A TOPIC is rising or fading. Answers "how much is X being discussed", "BUZZ OVER TIME for X", "is attention on X growing this week". Returns a per-bucket count broken out by network, running totals, engagement sums where the source exposes them, and an explicit window_actually_covered block. A bucket is a number only where that network was truly measured; where reach ran out it is null, so a measured zero is always distinguishable from an unobserved gap. Coverage is Bluesky, Mastodon, Reddit and Hacker News; X/Twitter is excluded (paid API), so results are a directional proxy over a partial slice of social media rather than total social volume. Examples: topic "bitcoin", days 7, bucket "day" for a week-long attention curve; topic "openai", days 2, bucket "hour", networks ["bluesky","hackernews"] for an intraday spike check.
| Name | Type | Req | Description |
|---|---|---|---|
| bucket | string | – | Bucket width for the series. Default "day". Use "hour" for intraday spikes (window capped at 3 days). |
| days | number | – | How many days back to measure. Default 7, maximum 30. With bucket="hour" this is capped at 3 days. |
| mastodon_instance | string | – | Mastodon instance whose public hashtag timeline is read. Default mastodon.social. Examples: "mastodon.world", "fosstodon.org". |
| networks | array | – | Subset of networks to measure. Default is all four: bluesky, mastodon, reddit, hackernews. |
| topic | string | yes | The search term to count posts for. Examples: "bitcoin", "openai", "federal reserve". Mastodon matches this as a single hashtag. |
No output schema declared.
No examples provided.
How do I install the Social Signal MCP server?
Social Signal runs locally as an npm package, launched with npx -y @pipeworx/mcp-social-signal. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-social-signal
claude mcp add pipeworx-io-social-signal -- npx -y @pipeworx/mcp-social-signal
What is the Social Signal MCP server?
Social Signal is an MCP server listed in the public MCP registry as io.github.pipeworx-io/social-signal. Social Signal, post-VOLUME TIME SERIES across the open social networks that can be read without… This page covers its npm package (@pipeworx/mcp-social-signal).
Is the Social Signal MCP server safe to use?
Social Signal scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Social Signal MCP server expose?
Social Signal exposes 2 tools: social_topic_volume, social_account_activity. Their descriptions and schemas cost roughly 713 tokens of context every time the server is loaded.
Is the Social Signal MCP server still maintained?
Social Signal is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Social Signal MCP server under?
Social Signal declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.