Side-by-side MCP server comparison
Short answer: it is close. io.github.vmoranv/jshookmcp scores 95/100 and MCP GitLab scores 96/100 - a 1-point gap, which is inside the noise of a weekly rescore. MCP GitLab exposes 12 tools against io.github.vmoranv/jshookmcp's 2, so the choice comes down to whether you need that extra surface area or would rather keep your context window small.
Last updated
| Metric | io.github.vmoranv/jshookmcp | Mcp Gitlab |
|---|---|---|
| MCPpedia Score | 95 | 96 |
| Security Score | 30 | 30 |
| Maintenance Score | 20 | 21 |
| GitHub Stars | 2.1k | 2.1k |
| Weekly Downloads | 645 | 103.9k |
| Tools | 2 | 12 |
| Est. Token Cost | 300 | 1.8k |
| Open CVEs | 0 | 0 |
| Health | Active | Active |
| Auth Required | No | No |
| Transport | stdio, sse, http | stdio |
| License | AGPL-3.0 | MIT |
| API Pricing | freemium | freemium |
Mcp Gitlab and io.github.vmoranv/jshookmcp are closely matched at the top with scores of 96 and 95. Check each server's detail page to decide which fits your use case.
Compare up to 4 servers: mcppedia.org/compare/server-a-vs-server-b-vs-server-c