RegistryCompare › Apify MCP Server vs Kubernetes MCP Server

Apify MCP Server vs Kubernetes MCP Server

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

Apify MCP Server leads on trust — 86.8/100 (Grade A) vs 84.6/100 (Grade A), a 2.2-point gap. Full breakdown below.
Signal Apify MCP Serverapify/apify-mcp-server Kubernetes MCP ServerFlux159/mcp-server-kubernetes
HVTrust score 86.8 84.6
Evidence grade A A
Coverage grade B B
Overall rank #24 #39
Rank in MCP Servers #3 #6
GitHub stars 2.5k 1.5k
Last updated today 6d ago
Build provenance Yes Yes
OSSF Scorecard 5.1 / 10 5.6 / 10
License MIT MIT
Downloads 22k/wk 15k/wk
Trust dimensions (points earned)
Safety / integrity / 25 18.9 16.4
Identity & provenance / 18 18.0 18.0
Transparency / 17 12.8 13.3
Maintenance / 20 19.7 18.3
Adoption / 20 14.0 13.2
Runtime capability surface (full matrix)
MCP server Implemented Implemented
External providers 1 — OpenAI 1 — Anthropic
Requires API keys Yes No
Plugin surface extensions extensions
Provenance drift Match Match
Open in the live compare tool → Apify MCP Server 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.2 →