Apify MCP Server vs Codebase Memory MCP
An independent, evidence-based trust comparison of Apify MCP Server and Codebase Memory 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.
Codebase Memory MCP leads on trust — 91.0/100 (Grade A) vs 88.6/100 (Grade A), a 2.4-point gap. Full breakdown below.
| Signal | Apify MCP Serverapify/apify-mcp-server | Codebase Memory MCPDeusData/codebase-memory-mcp |
|---|---|---|
| HVTrust score | 88.6 | 91.0 |
| Evidence grade | A | A |
| Coverage grade | B | B |
| Overall rank | #22 | #7 |
| Rank in MCP Servers | #3 | #1 |
| GitHub stars | 5.3k | 41.0k |
| Last updated | 2d ago | 1d ago |
| Build provenance | Yes | Yes |
| OSSF Scorecard | 5.5 / 10 | 7.5 / 10 |
| License | MIT | MIT |
| Downloads | 50k/wk | 5k/wk |
| Trust dimensions (points earned) | ||
| Safety / integrity / 25 | 19.4 | 18.4 |
| Identity & provenance / 18 | 18.0 | 18.0 |
| Transparency / 17 | 13.2 | 14.9 |
| Maintenance / 20 | 19.4 | 19.9 |
| Adoption / 20 | 15.2 | 15.9 |
| Runtime capability surface (full matrix) | ||
| MCP server | Implemented | Implemented |
| External providers | — | — |
| Requires API keys | Yes | No |
| Plugin surface | — | — |
| Provenance drift | Match | Match |
Open in the live compare tool →
Apify MCP Server profile
Codebase Memory 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 →