RegistryCompare › Canvas MCP vs LinkedIn MCP Server

Canvas MCP vs LinkedIn MCP Server

An independent, evidence-based trust comparison of Canvas MCP and LinkedIn 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.

LinkedIn MCP Server leads on trust — 87.5/100 (Grade A) vs 87.2/100 (Grade A), a 0.3-point gap. Full breakdown below.
Signal Canvas MCPvishalsachdev/canvas-mcp LinkedIn MCP Serverstickerdaniel/linkedin-mcp-server
HVTrust score 87.2 87.5
Evidence grade A A
Coverage grade B B
Overall rank #44 #39
Rank in MCP Servers #11 #7
GitHub stars 243 3.5k
Last updated today today
Build provenance Yes Yes
OSSF Scorecard 7.7 / 10 4.9 / 10
License MIT Apache-2.0
Downloads 163/wk 10k/wk
Trust dimensions (points earned)
Safety / integrity / 25 21.5 18.3
Identity & provenance / 18 18.0 18.0
Transparency / 17 15.0 12.7
Maintenance / 20 20.0 19.8
Adoption / 20 8.7 13.8
Runtime capability surface (full matrix)
MCP server Implemented Implemented
External providers
Requires API keys Yes No
Plugin surface plugins
Provenance drift Match Match
Open in the live compare tool → Canvas MCP profile LinkedIn 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 →