mcp@4.8.1
VERIFIEDPublisher claims: "An MCP interface into the Bright Data toolset" Observed in sandbox: calls api.brightdata.com only, touches nothing outside the project, writes no memory.
Coverage
Started with a decoy API_TOKEN; tool list observed. Tool calls with a real credential not tested.- Tested
- server startup with a tagged decoy in API_TOKEN · MCP initialize and tools/list · every tool description, for hidden instructions · where the decoy credential went · every file read, file written and host contacted by what ran
- Not tested
- what the tools do when called with a real credential
- Needs
- API_TOKEN — give it to the server where it runs, through vet-skills run --secrets, so the value never enters the server's environment. Never paste a credential into a chat, a ticket or a report.
Before you give it your token
- It will ask for
API_TOKENConfiguration, not credentials: BASE_MAX_RETRIES, BASE_TIMEOUT, BROWSER_FILTERED_SNAPSHOT, BROWSER_ZONE, CONTENT_GATE, CONTENT_GATE_PROGRESS_MS, CONTENT_GATE_TIMEOUT, GROUPS, RATE_LIMIT, SERP_ZONE, TOOLS- Where it talks to
- brightdata.com (its own)Also chatgpt.com, perplexity.ai — not the publisher's domain; check what for before connecting.
- What we saw when it ran
- no credential files read · reached only api.brightdata.com (its own)
- What we could not test
- what the tools do when called with a real credential
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names chatgpt.com, perplexity.ai as well as its own vendor. The guard injects API_TOKEN only into requests to brightdata.com (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
What changed since 4.8.0
vet-skills diff mcp 4.8.0 4.8.1In the sandbox, this version reached for nothing 4.8.0 did not. Compared from the two recorded runs, not from source.
Only one of the two runs produced a tool list; tools are not compared.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios) on 2026-11-22 and scored it 89/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: calls api.brightdata.com only, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 52 s · 2 scenarios · 0 deviationsStatic findings
<summary><b>Zed</b></summary> Add to your Zed settings: ```json { "context_servers": { "brightdata": { "url": "https://mcp.brightdata.com/mcp?token=YOUR_API_TOKFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<summary><b>Warp</b></summary> Go to Settings > MCP Servers > Add MCP Server and add: ```json { "brightdata": { "url": "https://mcp.brightdata.com/mcp?token=YOUFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<summary><b>Claude Code</b></summary> ```bash claude mcp add --transport http brightdata "https://mcp.brightdata.com/mcp?token=YOUR_API_TOKEN" ```Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<summary><b>Cursor</b></summary> Add to `~/.cursor/mcp.json`: ```json { "mcpServers": { "brightdata": { "url": "https://mcp.brightdata.com/mcp?token=YOUR_API_TOFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<summary><b>VS Code</b></summary> Add to `.vscode/mcp.json`: ```json { "servers": { "brightdata": { "type": "http", "url": "https://mcp.brightdata.com/mcp?tokenFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<summary><b>Claude Desktop</b></summary> 1. Go to: Settings → Connectors → Add custom connector 2. Name: `Bright Data` 3. URL: `https://mcp.brightdata.com/mcp?tFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<summary><b>Windsurf</b></summary> Add to `~/.codeium/windsurf/mcp_config.json`: ```json { "mcpServers": { "brightdata": { "serverUrl": "https://mcp.brightdata.Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<summary><b>Gemini CLI</b></summary> Add to `~/.gemini/settings.json`: ```json { "mcpServers": { "brightdata": { "httpUrl": "https://mcp.brightdata.com/mcp?tokeFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
Not checked against OSV yet; the weekly check has not reached this version.