RegistryCompare › Mongodb MCP Server vs Supabase MCP Server

Mongodb MCP Server vs Supabase MCP Server

An independent, evidence-based trust comparison of Mongodb 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.9/100 (Grade A) vs 87.2/100 (Grade A), a 1.7-point gap. Full breakdown below.
Signal Mongodb MCP Servermongodb-js/mongodb-mcp-server Supabase MCP Serversupabase/mcp
HVTrust score 87.2 88.9
Evidence grade A A
Coverage grade B B
Overall rank #38 #19
Rank in MCP Servers #9 #3
GitHub stars 1.1k 2.9k
Last updated today today
Build provenance Yes Yes
OSSF Scorecard 5.5 / 10 6.5 / 10
License Apache-2.0 Apache-2.0
Downloads 79k/wk 102k/wk
Trust dimensions (points earned)
Safety / integrity / 25 19.2 19.9
Identity & provenance / 18 18.0 18.0
Transparency / 17 13.2 14.0
Maintenance / 20 19.0 17.6
Adoption / 20 13.8 15.0
Runtime capability surface (full matrix)
MCP server Implemented Implemented
External providers 1 — Supabase
Requires API keys Yes No
Plugin surface plugins
Provenance drift Match Match
Open in the live compare tool → Mongodb 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 →