RegistryCompare › LinkedIn MCP Server vs Supabase MCP Server

LinkedIn MCP Server vs Supabase MCP Server

An independent, evidence-based trust comparison of LinkedIn 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.8/100 (Grade A) vs 87.4/100 (Grade A), a 1.4-point gap. Full breakdown below.
Signal LinkedIn MCP Serverstickerdaniel/linkedin-mcp-server Supabase MCP Serversupabase/mcp
HVTrust score 87.4 88.8
Evidence grade A A
Coverage grade B B
Overall rank #32 #19
Rank in MCP Servers #6 #3
GitHub stars 3.3k 2.9k
Last updated today today
Build provenance Yes Yes
OSSF Scorecard 4.9 / 10 6.5 / 10
License Apache-2.0 Apache-2.0
Downloads 13k/wk 102k/wk
Trust dimensions (points earned)
Safety / integrity / 25 18.2 19.9
Identity & provenance / 18 18.0 18.0
Transparency / 17 12.7 14.0
Maintenance / 20 19.2 17.5
Adoption / 20 13.9 15.0
Runtime capability surface (full matrix)
MCP server Implemented Implemented
External providers 1 — Supabase
Requires API keys No No
Plugin surface plugins
Provenance drift Match Match
Open in the live compare tool → LinkedIn 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 →