MCP Rank
View Leaderboard

Developer tools

GitHub MCP Server

Repository, issue, pull request, and code search workflows for agentic coding.

Deep ReviewMCP Rank ReviewedHigh confidencelow riskclaudecursorcodexVS Code

Score breakdown

Install + docs94
Maintenance96
Auth handling90
Client compatibility94
Real usefulness97
Safety signals88

Evidence history

Review snapshots show why the current score, confidence, and risk labels changed over time.

seed review
DateChangeScoreConfidenceRisk
May 14, 2026
Initial MCP Rank review captured from the curated seed dataset.

First-party GitHub ownership materially improves provenance and maintenance confidence.

seed snapshot · reviewed

94highlow

Evidence notes

First-party GitHub ownership materially improves provenance and maintenance confidence.
Install paths cover containerized use and common MCP client setup patterns.
Tool value is concrete: repository search, issue triage, pull-request review, and workflow investigation.
Permission risk is understandable because teams can review token scopes before connecting.
Evidence confidence is high because source ownership, docs, and package distribution are all directly linkable.

Best-fit use cases

Best fit for coding-agent workflows where repository context is the primary MCP need.

Useful for support engineers who need issue and pull-request context without manually switching tools.

Strong default candidate for teams building an MCP baseline because value is broad and review evidence is strong.

Risk analysis

Primary risk is overbroad repository or organization token scope.

Mutation tools should be gated by human approval and separated from read-only inspection.

Private code exposure risk depends on the connected client and model provider, not only the MCP server.

Use-case examples

Summarize open pull requests before standup.
Find recent issues related to a failing CI workflow.
Draft a safe investigation plan for a repository incident.