chore(deps): update dependency @brightdata/mcp to v2.9.5

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@brightdata/mcp	2.9.0 → 2.9.5

---

Release Notes

brightdata/brightdata-mcp (@​brightdata/mcp)

v2.9.5

Compare Source

v2.9.4

Compare Source

v2.9.3

Compare Source

v2.9.3

• New code tool group - your coding agent's companion
  • web_data_npm_package - look up any npm package by name and get back
    structured metadata: latest version, README, dependencies, and more
    (e.g. @brightdata/sdk, express, fastify)
  • web_data_pypi_package - look up any PyPI package by name and get back
    structured metadata: latest version, README, dependencies, and more
    (e.g. langchain-brightdata, requests, numpy)
  • Enable with GROUPS="code" - works with Claude Code, Cursor, Windsurf,
    and any MCP-powered coding agent
• Added code group row to the tool groups table in README
• Added coding agent configuration example in README

Why this matters

Coding agents constantly need to answer questions like "what's the latest
version of X?" or "what does this package do?". Until now that meant
scraping registry pages or relying on stale training data. The code group
gives agents a single, reliable tool to query npm and PyPI directly —
structured data, no scraping, no blocking, always up to date.

v2.9.2

Compare Source

v2.9.1

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

[github-actions]

🔒 MCP Security Scan Results

⚠️ brightdata-mcp

• Status: Warning
• Message: No JSON output found in scan results (insecure_ignore is enabled)

---

Summary: Scanned 1 MCP server(s), all passed security checks. ✅

[rdimitrov]

@renovatebot rebase

[JAORMX]

Triage: build-containers blocked by genuine upstream CVEs

Local Grype scan (DB 2026-04-27) of the 2.9.5 image surfaces these HIGH findings (severity-cutoff: high, only-fixed: true):

Package	Installed	GHSA	Severity	Fixed in
@modelcontextprotocol/sdk	1.21.2	GHSA-w48q-cv73-mx4w	High	1.24.0
@modelcontextprotocol/sdk	1.21.2	GHSA-8r9q-7v3j-jr4g	High	1.25.2
@modelcontextprotocol/sdk	1.21.2	GHSA-345p-7cg4-v4c7	High	1.26.0
picomatch	4.0.3	GHSA-c2c7-rcm5-vvqj	High	4.0.4

These are genuine upstream CVEs, not false positives. The fix requires @brightdata/mcp to bump its @modelcontextprotocol/sdk dep to ≥1.26.0 (and pull in updated transitive deps for picomatch).

Recommendation: Hold this bump until upstream brightdata-com/brightdata-mcp updates the MCP SDK pin.