RegistryCompare › LinkedIn MCP Server vs Openzim MCP

LinkedIn MCP Server vs Openzim MCP

An independent, evidence-based trust comparison of LinkedIn MCP Server and Openzim MCP, 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 86.8/100 (Grade A), a 0.7-point gap. Full breakdown below.
Signal LinkedIn MCP Serverstickerdaniel/linkedin-mcp-server Openzim MCPcameronrye/openzim-mcp
HVTrust score 87.5 86.8
Evidence grade A A
Coverage grade B B
Overall rank #39 #50
Rank in MCP Servers #7 #14
GitHub stars 3.5k 131
Last updated today today
Build provenance Yes Yes
OSSF Scorecard 4.9 / 10 7.5 / 10
License Apache-2.0 MIT
Downloads 10k/wk 607/wk
Trust dimensions (points earned)
Safety / integrity / 25 18.3 21.9
Identity & provenance / 18 18.0 18.0
Transparency / 17 12.7 14.9
Maintenance / 20 19.8 19.0
Adoption / 20 13.8 8.8
Runtime capability surface (full matrix)
MCP server Implemented Implemented
External providers
Requires API keys No Yes
Plugin surface plugins
Provenance drift Match Match
Open in the live compare tool → LinkedIn MCP Server profile Openzim MCP 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 →