RegistryCompare › Kubernetes MCP Server vs Supabase MCP Server

Kubernetes MCP Server vs Supabase MCP Server

An independent, evidence-based trust comparison of Kubernetes MCP Server and Supabase 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.

Supabase MCP Server leads on trust — 88.9/100 (Grade A) vs 80.6/100 (Grade A), a 8.3-point gap. Full breakdown below.
Signal Kubernetes MCP ServerFlux159/mcp-server-kubernetes Supabase MCP Serversupabase/mcp
HVTrust score 80.6 88.9
Evidence grade A A
Coverage grade B B
Overall rank #68 #24
Rank in MCP Servers #6 #2
GitHub stars 1.6k 2.9k
Last updated 8d ago today
Build provenance Yes Yes
OSSF Scorecard 5.5 / 10 6.5 / 10
License MIT Apache-2.0
Downloads 9k/wk 89k/wk
Trust dimensions (points earned)
Safety / integrity / 25 16.9 20.0
Identity & provenance / 18 18.0 18.0
Transparency / 17 13.2 14.0
Maintenance / 20 13.5 17.6
Adoption / 20 13.0 14.9
Runtime capability surface (full matrix)
MCP server Implemented Implemented
External providers 1 — Google Gemini 1 — Supabase
Requires API keys No No
Plugin surface plugins
Provenance drift Match Match
Open in the live compare tool → Kubernetes MCP Server profile Supabase 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 →