Registry › Compare › Gitlab MCP vs Windows MCP

Gitlab MCP vs Windows MCP

Both are Grade A and 0.1 points apart, so choose on what you weigh most. Gitlab MCP leads on transparency; Windows MCP leads on supply-chain integrity and adoption.

A Gitlab MCP 90.9

MCP server for GitLab: 277 tools for projects, MRs, issues, pipelines, wikis and more via the GitLab REST/GraphQL API

zereight/gitlab-mcp · #18 overall · #4 MCP Servers · coverage B (3/5)

Choose Gitlab MCP if transparency matters most.

+1.4Transparency: OSSF Scorecard 8.3 against 6.7

A Windows MCP 90.8

MCP Server for Computer Use in Windows

CursorTouch/Windows-MCP · #21 overall · #5 MCP Servers · coverage B (3/5)

Choose Windows MCP if supply-chain integrity and adoption matter most.

+0.9Safety / Integrity: 99% of recent commits signed, against 41%
+0.5Adoption: 11.5k GitHub stars against 2.1k

Where they differ

19.9

Safety / IntegrityWindows MCP +0.9

20.8

15.6

TransparencyGitlab MCP +1.4

14.2

19.9

MaintenanceGitlab MCP +0.1

19.8

15.0

AdoptionWindows MCP +0.5

15.5

1 dimension identical: Identity 18.0 · Full evidence table

An independent, evidence-based trust comparison of Gitlab 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.

Full evidence

Signal	Gitlab MCPzereight/gitlab-mcp	Windows MCPCursorTouch/Windows-MCP
HVTrust score	90.9	90.8
Evidence grade	A	A
Coverage grade	B	B
Overall rank	#18	#21
Rank in MCP Servers	#4	#5
GitHub stars	2.1k	11.5k
Last updated	1d ago	1d ago
Build provenance	Yes	Yes
OSSF Scorecard	8.3 / 10	6.7 / 10
License	MIT	MIT
Downloads	172k/wk	21k/wk
Trust dimensions (points earned)
Safety / integrity / 25	19.9	20.8
Identity & provenance / 18	18.0	18.0
Transparency / 17	15.6	14.2
Maintenance / 20	19.9	19.8
Adoption / 20	15.0	15.5
Runtime capability surface (full matrix)
MCP server	Implemented	Implemented
External providers	—	—
Requires API keys	Yes	Yes
Plugin surface	—	—
Provenance drift	Match	Match

Open in the live compare tool → Gitlab 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.4 →