BuzzSearch
NPM · BUZZSEARCH-MCP · 2 COMPONENTS
Search Reddit, TikTok, YouTube, and Facebook comments for exact customer quotes for ad copy.
Available components
Last scanned (22 hours ago)
Scores higher than 42% of npm servers
Category Marketing and SEO
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
- 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 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1678 tokens (~167/item across 10 items; 9 tools + 1 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 Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 59% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
- Supports UI / widget rendering.Pass
Checks we ran (17)
- 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
- Capabilities
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 →
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 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +11
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → 0.85 ▲ functional
- 17 Nov 26 −10
- Malware scan: pass → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- 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
- Schema quality: 151 → 167 ▼ functional
- Capabilities: pass → unverified ▼ functional
- Dependency health: 0.85 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Stability: unverified → 0.07 ▲ functional
- Package version: 1.1.6 → 1.1.7 functional
- 16 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 15 Nov 26 69
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 21 Nov 2026 · Analysed npm/buzzsearch-mcp@1.1.7
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 →
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 →
ask Ask a follow-up ~137
Ask a new question over a completed search's corpus and get a cited answer, without searching again. Costs less than a new search: only the answer is metered at the API rate. Good for 'what do they say about price', 'summarize the objections', 'which phrases do they use for the problem'. Works on searches started through the API or MCP.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | – |
| search_id | string | yes | The search id returned by `search` or `list_searches`. |
| wait_seconds | integer | – | Seconds to wait server-side for completion before returning (0 to 55). Call again to resume. |
No output schema declared.
No examples provided.
generate_hooks Generate ad hooks ~162
Write ad hooks grounded in a completed search's quotes, using BuzzSearch's hook writer: each hook opens with a callout lifted from real comments and carries a loop or promise. Metered at the API rate, no new search. Works on searches started through the API or MCP. Give an `angle` to steer (a product, a persona, a platform).
| Name | Type | Req | Description |
|---|---|---|---|
| angle | string | – | Optional steer, e.g. 'TikTok UGC for a $40 posture corrector'. |
| count | integer | – | – |
| search_id | string | yes | The search id returned by `search` or `list_searches`. |
| wait_seconds | integer | – | Seconds to wait server-side for completion before returning (0 to 55). Call again to resume. |
No output schema declared.
No examples provided.
get_balance Get credit balance ~31
The user's BuzzSearch credit balance, with a link to top up. Searches draw from it at the API rate.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_comments Get raw comments ~130
The raw comment bodies behind a completed search, grouped by thread or video, filtered and paged. Free. A search reads hundreds to thousands of comments, so filter by source, a substring, or a minimum score, and page with limit and offset.
| Name | Type | Req | Description |
|---|---|---|---|
| contains | string | – | Case-insensitive substring filter on the comment body. |
| limit | integer | – | – |
| min_score | integer | – | Minimum upvotes or likes. |
| offset | integer | – | – |
| search_id | string | yes | The search id returned by `search` or `list_searches`. |
| sources | array | – | – |
No output schema declared.
No examples provided.
get_quotes Get quotes ~174
Verbatim customer quotes extracted by a search, filtered and paged. Free. Each quote carries a stable id, the source url, a dimension (emotional_painpoints, recurring_painpoints, desired_outcomes, failed_solutions, objections, customer_lingo), an engagement score and an emotional intensity (1 to 5). For ad copy, pull emotional_painpoints and customer_lingo sorted by intensity.
| Name | Type | Req | Description |
|---|---|---|---|
| contains | string | – | Case-insensitive substring filter on the quote text. |
| dimensions | array | – | – |
| limit | integer | – | – |
| min_intensity | integer | – | – |
| offset | integer | – | – |
| search_id | string | yes | The search id returned by `search` or `list_searches`. |
| sort | string | – | – |
| sources | array | – | – |
No output schema declared.
No examples provided.
get_search Get a search ~131
Read a search's status, cited answer, coverage counts and top quotes. Free. Pass `turn_id` to read a specific follow-up answer, otherwise the latest turn is returned. A finished search returns at once; a running one is held open for up to 55s and returns as soon as it finishes, so call it again until status is "completed".
| Name | Type | Req | Description |
|---|---|---|---|
| search_id | string | yes | The search id returned by `search` or `list_searches`. |
| turn_id | string | – | A turn id from `search`, `ask` or `generate_hooks`. Default: the latest turn. |
No output schema declared.
No examples provided.
get_sources Get sources read ~81
The threads and videos a search read, with engagement, comment counts and how many quotes each produced. Free. Use it to cite a thread or pick which source's raw comments to pull.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
| search_id | string | yes | The search id returned by `search` or `list_searches`. |
No output schema declared.
No examples provided.
list_searches List past searches ~98
Recent searches by the signed-in user, newest first, including ones run in the BuzzSearch app. Free. Reread a past search with get_search or get_quotes instead of paying for a new one on the same topic.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | api = started via API or MCP, web = run in the app. |
| contains | string | – | Case-insensitive filter on the search query. |
| limit | integer | – | – |
No output schema declared.
No examples provided.
search Search UGC and social comments across the web ~418
Search the web for user-generated content: what real people say about a product, problem or audience in comments on Reddit, YouTube, TikTok and Facebook groups. Runs a full live search: finds threads and videos across the web, reads their comments, extracts verbatim quotes and writes a cited answer. A query that contains a TikTok video, creator profile or hashtag link, a bare creator @handle (TikTok unless the query says YouTube), a YouTube video or channel link, a Reddit thread or subreddit link, or a Facebook group post link reads that link's own comments directly (add a question after the link to also search the topic). A query that is a pasted list of comments is analyzed directly with no web search. A search usually takes one to three minutes, longer than one call can wait: it waits up to `wait_seconds` and returns the answer with the top quotes when done, otherwise the exact `get_search` call to make next; keep calling `get_search` until the status is completed. Costs credits from the BuzzSearch balance at the API rate; the exact charge is reported on completion as `credits_charged` with `balance_after`. When the balance cannot cover a search the call fails with INSUFFICIENT_CREDITS and a top-up link: tell the user and share the link. Check `list_searches` first: a prior search on the same topic can be reread for free.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | string | – | quick (about a minute), deep (about three), exhaustive (longest, most comments). |
| query | string | yes | The research question, e.g. 'what do people hate about robot vacuums'. |
| sources | array | – | Default: reddit, youtube, tiktok. Add facebook for group discussions. |
| time_range | string | – | How recent the posts and comments should be. Default: any time. |
| wait_seconds | integer | – | Seconds to wait server-side for completion before returning (0 to 55). Call again to resume. |
No output schema declared.
No examples provided.
How do I install the BuzzSearch MCP server?
BuzzSearch runs locally as an npm package, launched with npx -y buzzsearch-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 · buzzsearch-mcp
claude mcp add ai-buzzsearch-mcp -- npx -y buzzsearch-mcp
What is the BuzzSearch MCP server?
BuzzSearch is an MCP server listed in the public MCP registry as ai.buzzsearch/mcp. Search Reddit, TikTok, YouTube, and Facebook comments for exact customer quotes for ad copy. This page covers its npm package (buzzsearch-mcp).
Is the BuzzSearch MCP server safe to use?
BuzzSearch scores 71 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 BuzzSearch MCP server expose?
BuzzSearch exposes 9 tools: search, get_search, get_quotes, get_sources, get_comments, and 4 more. Their descriptions and schemas cost roughly 1,362 tokens of context every time the server is loaded.
Is the BuzzSearch MCP server still maintained?
BuzzSearch 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 BuzzSearch MCP server under?
BuzzSearch 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 BuzzSearch MCP server?
VerifyMCP ran 17 checks on BuzzSearch, covering Malware scan, Known CVEs, Install scripts, Dependency health and 13 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.