# Social Signal (npm · @pipeworx/mcp-social-signal)

Social Signal — post-VOLUME TIME SERIES across the open social networks that can be read without…

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-social-signal/social-signal-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-social-signal/social-signal-mcp)
- npm · `@pipeworx/mcp-social-signal`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-social-signal/pipeworx-mcp-social-signal.md), [page](https://verifymcp.io/servers/pipeworx-io-social-signal/pipeworx-mcp-social-signal)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-social-signal`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-social-signal).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add pipeworx-io-social-signal -- npx -y @pipeworx/mcp-social-signal
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-social-signal": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-social-signal"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-social-signal": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-social-signal"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-social-signal -- npx -y @pipeworx/mcp-social-signal
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-social-signal": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-social-signal"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-social-signal --command npx --arg -y --arg @pipeworx/mcp-social-signal
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-social-signal:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-social-signal"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-social-signal": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-social-signal"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-social-signal -t stdio -c npx -a -y @pipeworx/mcp-social-signal
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-social-signal": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-social-signal"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 81, +3)

- [security regression] 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.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.23
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 78, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 78)

First indexed and scored.

## MCP tools (2)

### `social_topic_volume` (~410 tokens)

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.

Input parameters:

- `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, required): The search term to count posts for. Examples: "bitcoin", "openai", "federal reserve". Mastodon matches this as a single hashtag.

### `social_account_activity` (~303 tokens)

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.

Input parameters:

- `days` (number): How many days of cadence to report. Default 30, maximum 90.
- `handle` (string, required): 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.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-social-signal/pipeworx-mcp-social-signal#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 78
- 2026-11-03: 78
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 78

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-social-signal
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-social-signal
- Repository: https://github.com/pipeworx-io/mcp-social-signal
- Website: https://pipeworx.io/packs/social-signal
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-social-signal/pipeworx-mcp-social-signal.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-social-signal/pipeworx-mcp-social-signal.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-social-signal/pipeworx-mcp-social-signal