RegistryCompare › LinkedIn MCP Server vs Mongodb MCP Server

LinkedIn MCP Server vs Mongodb MCP Server

An independent, evidence-based trust comparison of LinkedIn MCP Server and Mongodb 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.3/100 (Grade A) vs 87.2/100 (Grade A), a 0.1-point gap. Full breakdown below.
Signal LinkedIn MCP Serverstickerdaniel/linkedin-mcp-server Mongodb MCP Servermongodb-js/mongodb-mcp-server
HVTrust score 87.3 87.2
Evidence grade A A
Coverage grade B B
Overall rank #35 #38
Rank in MCP Servers #7 #9
GitHub stars 3.3k 1.1k
Last updated 1d ago today
Build provenance Yes Yes
OSSF Scorecard 4.9 / 10 5.5 / 10
License Apache-2.0 Apache-2.0
Downloads 13k/wk 79k/wk
Trust dimensions (points earned)
Safety / integrity / 25 18.2 19.2
Identity & provenance / 18 18.0 18.0
Transparency / 17 12.7 13.2
Maintenance / 20 19.0 19.0
Adoption / 20 13.9 13.8
Runtime capability surface (full matrix)
MCP server Implemented Implemented
External providers
Requires API keys No Yes
Plugin surface
Provenance drift Match Match
Open in the live compare tool → LinkedIn MCP Server profile Mongodb 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 →