# BuzzSearch (npm · buzzsearch-mcp)

Search Reddit, TikTok, YouTube, and Facebook comments for exact customer quotes for ad copy.

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

## Components

- remote · `buzzsearch.ai`: 31/100, [markdown](https://verifymcp.io/servers/ai-buzzsearch-mcp/api-mcp.md), [page](https://verifymcp.io/servers/ai-buzzsearch-mcp/api-mcp)
- npm · `buzzsearch-mcp`: 71/100 (this document), [markdown](https://verifymcp.io/servers/ai-buzzsearch-mcp/buzzsearch-mcp.md), [page](https://verifymcp.io/servers/ai-buzzsearch-mcp/buzzsearch-mcp)

## Channel facts

- Registry: `npm`
- Package: `buzzsearch-mcp`
- Version: `1.1.7`
- 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**: 74/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 59% 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 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.
  - Supports UI / widget rendering.

## Install

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

### Claude

```bash
claude mcp add ai-buzzsearch-mcp -- npx -y buzzsearch-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "ai-buzzsearch-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "buzzsearch-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-buzzsearch-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "buzzsearch-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add ai-buzzsearch-mcp -- npx -y buzzsearch-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add ai-buzzsearch-mcp --command npx --arg -y --arg buzzsearch-mcp
```

### Hermes

```yaml
mcp_servers:
  ai-buzzsearch-mcp:
    command: "npx"
    args: ["-y", "buzzsearch-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "ai-buzzsearch-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "buzzsearch-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-buzzsearch-mcp -t stdio -c npx -a -y buzzsearch-mcp
```

### Other

```json
{
  "mcpServers": {
    "ai-buzzsearch-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "buzzsearch-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 71, +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.

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

- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 0.85

### 2026-11-17 (score 59, −10)

- [security regression] Malware scan: pass → unverified
- [security regression] Known CVEs: pass → unverified
- [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] Schema quality: 151 → 167
- [functional regression] Capabilities: pass → unverified
- [functional regression] Dependency health: 0.85 → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional improvement] Stability: unverified → 0.07
- [functional] Package version: 1.1.6 → 1.1.7

### 2026-11-16 (score 69, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-15 (score 69)

First indexed and scored.

## MCP tools (9)

### `search` (~418 tokens)

Search UGC and social comments across the web

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.

Input parameters:

- `depth` (string): quick (about a minute), deep (about three), exhaustive (longest, most comments).
- `query` (string, required): 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.

### `get_search` (~131 tokens)

Get a search

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

Input parameters:

- `search_id` (string, required): 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.

### `get_quotes` (~174 tokens)

Get quotes

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.

Input parameters:

- `contains` (string): Case-insensitive substring filter on the quote text.
- `dimensions` (array)
- `limit` (integer)
- `min_intensity` (integer)
- `offset` (integer)
- `search_id` (string, required): The search id returned by `search` or `list_searches`.
- `sort` (string)
- `sources` (array)

### `get_sources` (~81 tokens)

Get sources read

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.

Input parameters:

- `limit` (integer)
- `offset` (integer)
- `search_id` (string, required): The search id returned by `search` or `list_searches`.

### `get_comments` (~130 tokens)

Get raw comments

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.

Input parameters:

- `contains` (string): Case-insensitive substring filter on the comment body.
- `limit` (integer)
- `min_score` (integer): Minimum upvotes or likes.
- `offset` (integer)
- `search_id` (string, required): The search id returned by `search` or `list_searches`.
- `sources` (array)

### `ask` (~137 tokens)

Ask a follow-up

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.

Input parameters:

- `question` (string, required)
- `search_id` (string, required): 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.

### `generate_hooks` (~162 tokens)

Generate ad hooks

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

Input parameters:

- `angle` (string): Optional steer, e.g. 'TikTok UGC for a $40 posture corrector'.
- `count` (integer)
- `search_id` (string, required): 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.

### `list_searches` (~98 tokens)

List past searches

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.

Input parameters:

- `channel` (string): api = started via API or MCP, web = run in the app.
- `contains` (string): Case-insensitive filter on the search query.
- `limit` (integer)

### `get_balance` (~31 tokens)

Get credit balance

The user's BuzzSearch credit balance, with a link to top up. Searches draw from it at the API rate.

## Diagnostics

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

## Score history

- 2026-11-21: 71
- 2026-11-20: 71
- 2026-11-19: 70
- 2026-11-18: 70
- 2026-11-17: 59
- 2026-11-16: 69
- 2026-11-15: 69

## Common questions

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

## Links

- npm package: https://www.npmjs.com/package/buzzsearch-mcp
- Socket report: https://socket.dev/npm/package/buzzsearch-mcp
- Repository: https://github.com/buzzsearch/buzzsearch-mcp-server
- Website: https://buzzsearch.ai/mcp
- Changelog RSS feed: https://verifymcp.io/servers/ai-buzzsearch-mcp/buzzsearch-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-buzzsearch-mcp/buzzsearch-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ai-buzzsearch-mcp/buzzsearch-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ai-buzzsearch-mcp/buzzsearch-mcp
