# Bright Data (npm · @pipeworx/mcp-bright-data)

Bright Data MCP — Bright Data Web Unlocker + SERP API (brightdata.com)

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 84/100, [markdown](https://verifymcp.io/servers/pipeworx-io-bright-data/bright-data-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-bright-data/bright-data-mcp)
- npm · `@pipeworx/mcp-bright-data`: 80/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-bright-data/pipeworx-mcp-bright-data.md), [page](https://verifymcp.io/servers/pipeworx-io-bright-data/pipeworx-mcp-bright-data)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-bright-data`
- Version: `0.2.1`
- 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-05.

- **Supply Chain Security**: 100/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.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-bright-data).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 54/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 755 tokens (~377/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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 Bright Data MCP server?

Bright Data runs locally as an npm package, launched with npx -y @pipeworx/mcp-bright-data. 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 pipeworx-io-bright-data -- npx -y @pipeworx/mcp-bright-data
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-bright-data": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-bright-data"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-bright-data": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-bright-data"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-bright-data -- npx -y @pipeworx/mcp-bright-data
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-bright-data --command npx --arg -y --arg @pipeworx/mcp-bright-data
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-bright-data:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-bright-data"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-bright-data": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-bright-data"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-bright-data -t stdio -c npx -a -y @pipeworx/mcp-bright-data
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-bright-data": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-bright-data"
      ]
    }
  }
}
```

## 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-03 (score 80, +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-01 (score 79, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-31 (score 63, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 78, +1)

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

### 2026-10-29 (score 77)

First indexed and scored.

## MCP tools (2)

### `brightdata_unlock` (~341 tokens)

Fetch any URL through Bright Data Web Unlocker — rotating residential proxies with automatic anti-bot bypass and CAPTCHA solving, built for the hardest-to-scrape sites (Cloudflare, PerimeterX, Akamai fronted). Returns the page content with status and length; large pages are truncated. Calls proxy the fetch synchronously and can take 10-30 seconds. BYOK: Bright Data API token via _apiKey + a Web Unlocker zone configured in your dashboard (first zone is auto-named "web_unlocker1"); pay-per-request pricing on the Bright Data side. Example: brightdata_unlock({ url: "https://example.com", _apiKey: "your-brightdata-token" })

Input parameters:

- `_apiKey` (string, required): Your Bright Data API token (account settings or zone Overview tab). Requires a Bright Data account with a Web Unlocker zone; sign up at https://brightdata.com
- `country` (string): Two-letter ISO country code for the proxy exit location, e.g. "us", "gb", "de". Default: Bright Data auto-selects per your zone configuration.
- `format` (string): Response shape: "raw" (default — the target page body as a string) or "json" (a JSON envelope with status/headers/body metadata from Bright Data).
- `url` (string, required): The absolute URL to fetch, including scheme, e.g. "https://example.com/page"
- `zone` (string): Your Web Unlocker zone name from the Bright Data control panel. Default "web_unlocker1" — the auto-generated name of the first Web Unlocker zone.

### `brightdata_serp` (~361 tokens)

Run a Google search through the Bright Data SERP API and return parsed organic results (rank, title, link, description) with geo-targeting. Uses the same Bright Data request API with a SERP-type zone — create a SERP API zone in your Bright Data dashboard and pass its name as `zone` (Web Unlocker zones return raw HTML for Google). BYOK: Bright Data API token via _apiKey; pay-per-request pricing on the Bright Data side. Example: brightdata_serp({ query: "best espresso machine", zone: "serp_api1", country: "us", _apiKey: "your-brightdata-token" })

Input parameters:

- `_apiKey` (string, required): Your Bright Data API token (account settings or zone Overview tab). Requires a Bright Data account with a SERP API zone; sign up at https://brightdata.com
- `country` (string): Two-letter country code for localized results (sent as Google's `gl` parameter), e.g. "us", "gb", "jp". Optional.
- `num` (number): Maximum organic results to return (client-side cap; Google serves ~10 per page — use `start` for deeper pages). Default 10.
- `query` (string, required): The Google search query, e.g. "best espresso machine 2026"
- `start` (number): Pagination offset: 0 = first page (default), 10 = second page, 20 = third.
- `zone` (string): Your SERP API zone name from the Bright Data control panel (a SERP-type zone is required for parsed Google results). Default "serp_api1" — the typical auto-generated name; check your dashboard for th…

## Diagnostics

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

## Score history

- 2026-11-05: 80
- 2026-11-04: 80
- 2026-11-03: 80
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 63
- 2026-10-30: 78
- 2026-10-29: 77

## Common questions

### What is the Bright Data MCP server?

Bright Data is an MCP server listed in the public MCP registry as io.github.pipeworx-io/bright-data. Bright Data MCP, Bright Data Web Unlocker + SERP API (brightdata.com). This page covers its npm package (@pipeworx/mcp-bright-data).

### Is the Bright Data MCP server safe to use?

Bright Data 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. Its build provenance is signed and verified. 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 Bright Data MCP server expose?

Bright Data exposes 2 tools: brightdata_unlock, brightdata_serp. Their descriptions and schemas cost roughly 702 tokens of context every time the server is loaded.

### Is the Bright Data MCP server still maintained?

Bright Data 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 Bright Data MCP server under?

Bright Data 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 Bright Data MCP server?

VerifyMCP ran 16 checks on Bright Data, 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/@pipeworx/mcp-bright-data
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-bright-data
- Repository: https://github.com/pipeworx-io/mcp-bright-data
- Website: https://pipeworx.io/packs/bright-data
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-bright-data/pipeworx-mcp-bright-data.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-bright-data/pipeworx-mcp-bright-data/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-bright-data/pipeworx-mcp-bright-data.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-bright-data/pipeworx-mcp-bright-data