Bright Data MCP

A powerful Model Context Protocol (MCP) server that provides an all-in-one solution for public web access.

MCP Servers JavaScript Grade B Listed MIT
75.3/100
Rank #89 of 1283
Compare Bright Data MCP

Strong public trust posture, backed by multiple independent signals.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-07-27 · 15d ago
Recent change
No recent signal change

Is Bright Data MCP safe? Bright Data MCP scores 75.3/100 (Grade B), ranked #89 of 1283 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 3.8/10; 26% of recent commits are signed; last pushed 2026-07-27. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-07-27
Rank Moved
Rank rose 22 spots (#99 → #77)
2026-07-27
HVTrust Changed
HVTrust up 3.9pts (70.9 → 74.8)
2026-07-27
Activity Score Changed
Activity score up 15pts (52 → 67)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.8/10. Tighten the weakest checks to improve public safety evidence.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
64.8
Activity sub-score · out of 100
#13

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-11 21:02 UTC · Repo last pushed 15 days ago

Activity & Reach

Stars
2.6k
Forks
322
Last Push
2026-07-27
15 days ago
Commits (4 wk)
5
Downloads (7d)
5,941
npm
HN mentions (30d)
Open Issues
9
Rank Change
▼1
was #88

Analysis

HVTrust Dimensions vs MCP Servers

75.3 / 100 · 100.0% confidence

Bright Data MCP MCP Servers average (761 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
13.6 / 25
8.6 above avg 5.0
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.7 above avg 13.3
Transparency50% declared license · 50% OSSF Scorecard
11.7 / 17
2.9 above avg 8.8
Maintenance60% last-push freshness · 40% commit activity
14.1 / 20
1.6 above avg 12.5
AdoptionLog-scaled stars · package downloads
13.2 / 20
7.4 above avg 5.8

Activity Inputs

64.8 / 100
StarsRepository reach
20.5 / 30
FreshnessLast push recency
22.9 / 25
ActivityRecent commits
9.7 / 25
CommunityFork signal
11.7 / 20

Supply Chain Trust

Package Provenance
Verified
npm attestation
OSSF Scorecard
3.8 / 10
OpenSSF Scorecard · scanned Aug 10, 2026
Signed Commits
26%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 10
CII-Best-Practices 0
Code-Review 0
Contributors 6
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 1
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions 0
Vulnerabilities 0

Is Bright Data MCP safe?

Public supply-chain signals for Bright Data MCP are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Bright Data MCP carries less obvious unverified-evidence risk than projects with thin signals.
Does Bright Data MCP publish package provenance?
Yes. Bright Data MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Bright Data MCP have an OpenSSF Scorecard?
Bright Data MCP has an OpenSSF Scorecard score of 3.8/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Bright Data MCP actively maintained?
Maintained. Last push was 15 days ago.
What license does Bright Data MCP use?
Bright Data MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Bright Data MCP's commits signed?
26% of the last 100 commits to Bright Data MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Bright Data MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Marketplace
Marketplace plugin/integration surface detected.
  • browser
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain Bright Data MCP?

For maintainers

HVTrust scores Bright Data MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Reputation Timeline

Signal history
HVTrust 2Rank 2Listed 1Grade 1Scorecard 1Score 1
2026-07-27
Rank Moved
Rank rose 22 spots (#99 → #77)
2026-07-27
HVTrust Changed
HVTrust up 3.9pts (70.9 → 74.8)
2026-07-27
Activity Score Changed
Activity score up 15pts (52 → 67)
2026-07-15
Scorecard Added
OSSF Scorecard: 3.8/10
2026-07-15
Grade Changed
Trust grade C → B
2026-07-15
Rank Moved
Rank rose 68 spots (#165 → #97)
2026-07-15
HVTrust Changed
HVTrust up 7.9pts (63.4 → 71.3)
2026-07-14
Newly Listed
First tracked at rank #165

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 75.3 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/bright-data-mcp.svg)](https://hvtracker.net/agents/bright-data-mcp)
HTML:
<a href="https://hvtracker.net/agents/bright-data-mcp"><img src="https://hvtracker.net/badge/bright-data-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON