RegistryCompare › Codebase Memory MCP vs Windows MCP

Codebase Memory MCP vs Windows MCP

An independent, evidence-based trust comparison of Codebase Memory MCP and Windows 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 — 92.1/100 (Grade A) vs 85.1/100 (Grade A), a 7.0-point gap. Full breakdown below.
Signal Codebase Memory MCPDeusData/codebase-memory-mcp Windows MCPCursorTouch/Windows-MCP
HVTrust score 92.1 85.1
Evidence grade A A
Coverage grade B B
Overall rank #5 #50
Rank in MCP Servers #1 #4
GitHub stars 44.1k 7.1k
Last updated today 1d ago
Build provenance Yes Yes
OSSF Scorecard 7.5 / 10 6.2 / 10
License MIT MIT
Downloads 16k/wk 4k/wk
Trust dimensions (points earned)
Safety / integrity / 25 19.0 17.8
Identity & provenance / 18 18.0 18.0
Transparency / 17 14.9 13.8
Maintenance / 20 20.0 16.4
Adoption / 20 16.8 14.1
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 → Codebase Memory MCP profile Windows 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 →