RegistryCompare › Bright Data MCP vs Kubernetes MCP Server

Bright Data MCP vs Kubernetes MCP Server

An independent, evidence-based trust comparison of Bright Data MCP and Kubernetes MCP Server, two MCP Servers projects in the HVTracker registry. Scores come from public, checkable signals — supply-chain provenance, OSSF Scorecard, maintenance, and adoption — not popularity.

Kubernetes MCP Server leads on trust — 84.4/100 (Grade A) vs 74.8/100 (Grade B), a 9.6-point gap. Full breakdown below.
Signal Bright Data MCPbrightdata/brightdata-mcp Kubernetes MCP ServerFlux159/mcp-server-kubernetes
HVTrust score 74.8 84.4
Evidence grade B A
Coverage grade B B
Overall rank #94 #55
Rank in MCP Servers #15 #6
GitHub stars 2.6k 1.5k
Last updated 2d ago 6d ago
Build provenance Yes Yes
OSSF Scorecard 3.8 / 10 5.5 / 10
License MIT MIT
Downloads 6k/wk 15k/wk
Trust dimensions (points earned)
Safety / integrity / 25 13.6 16.3
Identity & provenance / 18 18.0 18.0
Transparency / 17 11.7 13.2
Maintenance / 20 13.6 17.7
Adoption / 20 13.2 13.2
Runtime capability surface (full matrix)
MCP server Implemented Implemented
External providers 1 — Google Gemini
Requires API keys Yes No
Plugin surface
Provenance drift Match Match
Open in the live compare tool → Bright Data MCP profile Kubernetes MCP Server profile More MCP Servers →

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption, scaled by an evidence-confidence factor. Grade bands: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Signals refresh daily. Full methodology v4.3 →