Apify MCP Server vs Supabase MCP Server
An independent, evidence-based trust comparison of Apify 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.8/100 (Grade A) vs 88.6/100 (Grade A), a 0.2-point gap. Full breakdown below.
| Signal | Apify MCP Serverapify/apify-mcp-server | Supabase MCP Serversupabase/mcp |
|---|---|---|
| HVTrust score | 88.6 | 88.8 |
| Evidence grade | A | A |
| Coverage grade | B | B |
| Overall rank | #20 | #19 |
| Rank in MCP Servers | #4 | #3 |
| GitHub stars | 5.8k | 2.9k |
| Last updated | today | today |
| Build provenance | Yes | Yes |
| OSSF Scorecard | 5.5 / 10 | 6.5 / 10 |
| License | MIT | Apache-2.0 |
| Downloads | 38k/wk | 102k/wk |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 19.4 | 19.9 |
| Identity & provenance / 18 | 18.0 | 18.0 |
| Transparency / 17 | 13.2 | 14.0 |
| Maintenance / 20 | 19.5 | 17.5 |
| Adoption / 20 | 15.1 | 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 →
Apify 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 →