Comment Scraper
NPM · COMMENT-SCRAPER-MCP
Read your Comment Scraper exports of Reddit and Hacker News threads. Local and read-only.
Available components
Last scanned (13 hours ago)
Scores higher than 65% 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 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
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 353 tokens (~88/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 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
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 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 0
- Stability: 0.40 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- Package version: 0.1.1 → 0.1.3 functional
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
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/comment-scraper-mcp@0.1.3
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 | 30 |
| 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 →
get_comment Get a comment in context ~73
Returns one comment by its [cN] number with the comments it replies to (up to the top) and its direct replies.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | yes | Comment number, e.g. "c12" or "12" |
| thread | string | yes | Thread id from list_threads, or words from its title |
No output schema declared.
No examples provided.
list_threads List exported threads ~53
Lists the Reddit and Hacker News threads the user exported with Comment Scraper, newest first, with comment counts. Call this first to get a thread id.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Only threads whose title contains this text |
No output schema declared.
No examples provided.
read_thread Read a thread ~133
Returns a thread's post and comments as numbered Markdown ([c12] reply to [c3] (score 41, 3d ago)). Long threads come in pages: call again with the offset given at the end. Cite comments by their [cN] number.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Comments per page, default 200 |
| min_score | integer | – | Only comments with at least this score (hidden scores are left out) |
| offset | integer | – | Skip this many comments (for the next page) |
| thread | string | yes | Thread id from list_threads, or words from its title |
No output schema declared.
No examples provided.
search_comments Search comments ~94
Finds comments containing all of the given words across every exported thread (or one thread). Returns each match with its thread, [cN] number and score.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum matches, default 30 |
| query | string | yes | Words to look for; a comment must contain all of them (case-insensitive) |
| thread | string | – | Limit to one thread: id or words from its title |
No output schema declared.
No examples provided.
How do I install the Comment Scraper MCP server?
Comment Scraper runs locally as an npm package, launched with npx -y comment-scraper-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 · comment-scraper-mcp
claude mcp add supertj-comment-scraper-mcp -- npx -y comment-scraper-mcp
What is the Comment Scraper MCP server?
Comment Scraper is an MCP server listed in the public MCP registry as io.github.supertj/comment-scraper-mcp. Read your Comment Scraper exports of Reddit and Hacker News threads. Local and read-only. This page covers its npm package (comment-scraper-mcp).
Is the Comment Scraper MCP server safe to use?
Comment Scraper scores 80 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. 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 Comment Scraper MCP server expose?
Comment Scraper exposes 4 tools: list_threads, read_thread, search_comments, get_comment. Their descriptions and schemas cost roughly 353 tokens of context every time the server is loaded.
Is the Comment Scraper MCP server still maintained?
Comment Scraper 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 Comment Scraper MCP server under?
Comment Scraper declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.