Model Context Protocol moderate risk

Brightdata

Bright Data's Web MCP provides AI agents with seamless, unblocked access to real-time web data via a variety of tools, with varying levels of access and cost.

Connections & Capabilities

Connects To

GitHub

Capabilities

readwriteexec

Quickstart

Install

npx @brightdata/mcp

Config

{
  "mcpServers": {
    "Bright Data": {
      "command": "npx",
      "args": ["@brightdata/mcp"],
      "env": {
        "API_TOKEN": "<your-api-token-here>"
      }
    }
  }
}

Exposed MCP Tools (8)

safe

search_engine

Performs a web search and returns AI-optimized results.

Read-only operation; no data modification or system access.

safe

scrape_as_markdown

Scrapes a webpage and converts it to clean markdown format.

Read-only operation; no data modification or system access.

moderate

scraping_browser_snapshot

Captures a snapshot of a webpage using a real browser.

Can potentially trigger website security measures or expose sensitive information if not used carefully.

moderate

scraping_browser_click_ref

Simulates a click on a webpage element and returns the resulting page.

Can potentially trigger website security measures or unintended actions if not used carefully.

moderate

scraping_browser_screenshot

Takes a screenshot of a webpage using a real browser.

Can potentially capture sensitive information displayed on the page.

safe

web_data_amazon_product

Extracts product data from Amazon.

Read-only data extraction.

safe

web_data_linkedin_posts

Scrapes posts from LinkedIn.

Read-only data extraction.

safe

extract

Extracts structured data from a webpage using AI.

Read-only data extraction.

Safety Assessment

The Bright Data Web MCP is relatively safe in its default, free tier configuration. Enabling Pro mode or using custom tool configurations increases the risk, requiring careful consideration of the selected tools and their potential impact. Securely managing the API token is crucial.

Free tier limits access to basic, read-only tools.
Pro mode requires explicit enablement, preventing accidental access to advanced features.
Custom mode allows granular control over tool selection.
Rate limiting can be configured to prevent abuse.

API token is required, and its compromise could lead to unauthorized access.
Pro mode grants access to browser automation tools, which can be used maliciously if not properly controlled.
Custom mode allows enabling potentially dangerous tools if misconfigured.
Lack of detailed sandboxing for browser automation tools.