Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.CloudCorpRecords/buzzmeter

NPM · @RENETURCIOS/BUZZMETER · 2 COMPONENTS

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

72 Trust /100

Last scanned (21 hours ago)

Scores higher than 44% of npm servers

Trust breakdown (7 categories)

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 Security98
  • 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
  • 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
  • Stability observed for 4 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +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.

  • 19 Nov 26 +1
    • Stability: unverified → 0.07 ▲ functional
  • 18 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 17 Nov 26 55

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Analysed npm/@reneturcios/buzzmeter@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~542 tokens

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 →

Tool Tokens
emerging_terms ~107

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.

NameTypeReqDescription
daysnumber–Only terms first seen within N days (default 14).
limitnumber–Max terms (default 25).

No output schema declared.

No examples provided.

mention_pulse ~156

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.

NameTypeReqDescription
daysnumber–Look-back window in days (default 7, max ~30).
subredditstring–Optional: restrict the Reddit side to one subreddit.
termstringyesThe term/ticker/brand/product to track, e.g. 'Claude', '$NVDA', 'Notion'.

No output schema declared.

No examples provided.

trending_topics ~140

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.

NameTypeReqDescription
limitnumber–Max trending terms (default 15).
subredditstring–Limit to one subreddit, e.g. 'wallstreetbets' or 'r/SaaS'. Omit for overall (Reddit + HN).

No output schema declared.

No examples provided.

whats_being_said ~139

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.

NameTypeReqDescription
daysnumber–Look-back window in days (default 14).
limitnumber–Max posts (default 12).
querystringyesWhat to look up, e.g. 'vision pro returns' or 'rust vs go'.
subredditstring–Optional: restrict the Reddit side to one subreddit.

No output schema declared.

No examples provided.

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.

npm · @reneturcios/buzzmeter

# add to Claude Code
claude mcp add cloudcorprecords-buzzmeter -- npx -y @reneturcios/buzzmeter mcp
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.