# io.github.CloudCorpRecords/buzzmeter (npm · @reneturcios/buzzmeter)

Reddit and Hacker News sensing: trending topics, mention velocity, sentiment, new terms.

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `@reneturcios/buzzmeter`: 72/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-buzzmeter/reneturcios-buzzmeter.md), [page](https://verifymcp.io/servers/cloudcorprecords-buzzmeter/reneturcios-buzzmeter)
- oci · `ghcr.io/cloudcorprecords/buzzmeter`: 43/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-buzzmeter/ghcr-io-cloudcorprecords-buzzmeter.md), [page](https://verifymcp.io/servers/cloudcorprecords-buzzmeter/ghcr-io-cloudcorprecords-buzzmeter)

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/buzzmeter`
- Version: `0.1.0`
- 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-21.

- **Supply Chain Security**: 98/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.
  - 31 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 542 tokens (~135/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 io.github.CloudCorpRecords/buzzmeter MCP server?

io.github.CloudCorpRecords/buzzmeter runs locally as an npm package, launched with npx -y @reneturcios/buzzmeter mcp. 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 cloudcorprecords-buzzmeter -- npx -y @reneturcios/buzzmeter mcp
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-buzzmeter": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/buzzmeter",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-buzzmeter": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/buzzmeter",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-buzzmeter -- npx -y @reneturcios/buzzmeter mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-buzzmeter": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@reneturcios/buzzmeter",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cloudcorprecords-buzzmeter --command npx --arg -y --arg @reneturcios/buzzmeter --arg mcp
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-buzzmeter:
    command: "npx"
    args: ["-y", "@reneturcios/buzzmeter", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-buzzmeter": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@reneturcios/buzzmeter",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cloudcorprecords-buzzmeter -t stdio -c npx -a -y @reneturcios/buzzmeter mcp
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-buzzmeter": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/buzzmeter",
        "mcp"
      ]
    }
  }
}
```

## 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-20 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 71, +1)

- [functional improvement] Stability: unverified → 0.07

### 2026-11-18 (score 70, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-17 (score 55)

First indexed and scored.

## MCP tools (4)

### `trending_topics` (~140 tokens)

What is SURGING on Reddit + Hacker News right now. Returns a ranked list of terms/topics by real-time momentum (recency-weighted engagement across newest posts), scoped to a subreddit or overall. Use to answer 'what's trending on r/<x>' / 'what is the internet talking about today'. Live data from Arctic Shift (Reddit) + HN Algolia — no stale snapshot.

Input parameters:

- `limit` (number): Max trending terms (default 15).
- `subreddit` (string): Limit to one subreddit, e.g. 'wallstreetbets' or 'r/SaaS'. Omit for overall (Reddit + HN).

### `mention_pulse` (~156 tokens)

Mention COUNT + VELOCITY + SENTIMENT for a term, ticker ($AAPL), brand, or product across Reddit + Hacker News over a time window. Returns total mentions, day-by-day buckets, a velocity (rising/falling) signal, lexical sentiment breakdown, and the top posts. Use for brand-watch, ticker-buzz, product-launch tracking, or trend-confirmation. Live data.

Input parameters:

- `days` (number): Look-back window in days (default 7, max ~30).
- `subreddit` (string): Optional: restrict the Reddit side to one subreddit.
- `term` (string, required): The term/ticker/brand/product to track, e.g. 'Claude', '$NVDA', 'Notion'.

### `whats_being_said` (~139 tokens)

Top recent posts and the dominant discussion THEMES for a query across Reddit + Hacker News. Use to quickly understand 'what are people saying about X' — the actual posts plus the co-occurring themes/angles. Each post carries score, comments, sentiment and a link. Live data.

Input parameters:

- `days` (number): Look-back window in days (default 14).
- `limit` (number): Max posts (default 12).
- `query` (string, required): What to look up, e.g. 'vision pro returns' or 'rust vs go'.
- `subreddit` (string): Optional: restrict the Reddit side to one subreddit.

### `emerging_terms` (~107 tokens)

Newly FIRST-APPEARING terms from our rolling novelty ledger (Reddit/HN newest posts + the 24/7 idea_intel loop). Surfaces words/phrases/tickers we just started seeing — early-signal detection for new products, memes, projects, or narratives. Each row carries a first_seen date + sample.

Input parameters:

- `days` (number): Only terms first seen within N days (default 14).
- `limit` (number): Max terms (default 25).

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-buzzmeter/reneturcios-buzzmeter#diagnostics

## Score history

- 2026-11-21: 72
- 2026-11-20: 72
- 2026-11-19: 71
- 2026-11-18: 70
- 2026-11-17: 55

## Common questions

### What is the io.github.CloudCorpRecords/buzzmeter MCP server?

io.github.CloudCorpRecords/buzzmeter is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/buzzmeter. Reddit and Hacker News sensing: trending topics, mention velocity, sentiment, new terms. This page covers its npm package (@reneturcios/buzzmeter).

### Is the io.github.CloudCorpRecords/buzzmeter MCP server safe to use?

io.github.CloudCorpRecords/buzzmeter scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 io.github.CloudCorpRecords/buzzmeter MCP server expose?

io.github.CloudCorpRecords/buzzmeter exposes 4 tools: trending_topics, mention_pulse, whats_being_said, emerging_terms. Their descriptions and schemas cost roughly 542 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/buzzmeter MCP server still maintained?

io.github.CloudCorpRecords/buzzmeter is still listed as active in the MCP registry. We last reached this channel on 21 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 io.github.CloudCorpRecords/buzzmeter MCP server under?

io.github.CloudCorpRecords/buzzmeter declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the io.github.CloudCorpRecords/buzzmeter MCP server?

VerifyMCP ran 16 checks on io.github.CloudCorpRecords/buzzmeter, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@reneturcios/buzzmeter
- Socket report: https://socket.dev/npm/package/@reneturcios/buzzmeter
- Repository: https://github.com/CloudCorpRecords/buzzmeter
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-buzzmeter/reneturcios-buzzmeter.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-buzzmeter/reneturcios-buzzmeter/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cloudcorprecords-buzzmeter/reneturcios-buzzmeter.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-buzzmeter/reneturcios-buzzmeter
