github/github-mcp-server vs modelcontextprotocol/servers
github/github-mcp-server scores higher overall: 79/100 (A-tier) against 79/100 (A-tier). github/github-mcp-server leads on reliability, maintenance, safety; modelcontextprotocol/servers leads on skill leverage, evaluation readiness, composability. Scored 2026-07-07, methodology v1.0.
Dimension by dimension
| Dimension | github-mcp-server | mcp-servers |
|---|---|---|
| Reliability | 78 | 76 |
| Skill Leverage | 80 | 84 |
| Documentation | 82 | 82 |
| Maintenance | 92 | 90 |
| Safety / Governance | 76 | 70 |
| Evaluation Readiness | 60 | 62 |
| Composability | 88 | 92 |
| Adoption (capped) | 86 | 92 |
| Overall | 79 · A | 79 · A |
The entries
GitHub's official MCP server: repos, issues, PRs, actions, and code scanning exposed as agent tools with GitHub's own auth and permission…
The reference implementations of the Model Context Protocol: the official server collection that defines what a well-built agent tool looks…
Frequently asked questions
github/github-mcp-server or modelcontextprotocol/servers?
github/github-mcp-server scores higher overall (79 vs 79, methodology v1.0). But they are the same category, so the dimension table below is the real answer.
How is this comparison generated?
Both scorecards come from the same public rubric with evidence notes, scored by the same editorial process. This page presents them side by side; it adds no new judgments beyond the scores themselves.