Bright Data
NPM · @PIPEWORX/MCP-BRIGHT-DATA · 2 COMPONENTS
Bright Data MCP — Bright Data Web Unlocker + SERP API (brightdata.com)
Available components
Last scanned (14 hours ago)
Scores higher than 65% of npm servers
Category Search and Retrieval
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-bright-data). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability54
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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.
- 3 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.
- 1 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 +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.
- 29 Oct 26 77
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-bright-data@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-bright-data |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-bright-data/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3606586063 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:3ad0f649ac4536cfee352c42859bf016e992c69622fd611a6a2c054015bd3798b0c28591db7dd3b0196604d4734edb53a764d635cbe89c5f71e0a2122 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
brightdata_serp ~361
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" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | 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 | yes | 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… |
No output schema declared.
No examples provided.
brightdata_unlock ~341
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" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | 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 | yes | 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. |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-bright-data
claude mcp add pipeworx-io-bright-data -- npx -y @pipeworx/mcp-bright-data
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.