RegistryCompare › Apify MCP Server vs LinkedIn MCP Server

Apify MCP Server vs LinkedIn MCP Server

An independent, evidence-based trust comparison of Apify MCP Server 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 — 86.9/100 (Grade A) vs 57.8/100 (Grade C), a 29.1-point gap. Full breakdown below.
Signal Apify MCP Serverapify/apify-mcp-server LinkedIn MCP Serverstickerdaniel/linkedin-mcp-server
HVTrust score 57.8 86.9
Evidence grade C A
Coverage grade C B
Overall rank #383 #31
Rank in MCP Servers #130 #5
GitHub stars 5.0k 3.2k
Last updated today today
Build provenance Yes Yes
OSSF Scorecard 5.5 / 10 4.9 / 10
License MIT Apache-2.0
Downloads 13k/wk
Trust dimensions (points earned)
Safety / integrity / 25 19.4 18.0
Identity & provenance / 18 18.0 18.0
Transparency / 17 13.2 12.7
Maintenance / 20 19.7 19.5
Adoption / 20 8.9 13.9
Runtime capability surface (full matrix)
MCP server Implemented Implemented
External providers 1 — Anthropic
Requires API keys Yes No
Plugin surface extensions
Provenance drift Match Match
Open in the live compare tool → Apify MCP Server 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 →