updated 2026-11-05 12:09 UTC

GitHub MCP Server

Repository by github

GitHub's official MCP Server

Protocols & Tool Integration Go Listed MIT

Is GitHub MCP Server safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 7.0 / 10
Provenance None
Signed commits 78%
Last push today
Compare GitHub MCP Server

How does it stack up against its Protocols & Tool Integration neighbours?

Pick any agent to compare →
Suggest a correction

In detail: GitHub MCP Server scores 67.9/100 (Grade B), ranked #424 of 1374 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 7.0/10; 78% of recent commits are signed; last pushed 2026-11-05. Every point is earned from checkable signals — never paid placement. How scoring works →

How GitHub MCP Server could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships GitHub MCP Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/github/github-mcp-server, MIT, last pushed 2026-11-05. 78% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Strong

    OpenSSF Scorecard rates the repository's practices 7.0/10 (scanned Oct 30, 2026). The checks that decide who can get a change released:

    • Code Review5
    • Branch Protection8
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies9
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 8
    CI-Tests 9
    CII-Best-Practices 0
    Code-Review 5
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 10
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 9
    SAST 9
    Security-Policy 10
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages None

    No registry package. GitHub MCP Server is used from its repository, so what you run is whatever you check out: pin a release tag or commit.

Changes to this chain

No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of GitHub MCP Server.

Evidence behind this score

Coverage C: 2 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads (missing)
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues GitHub MCP Server’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How GitHub MCP Server compares in Protocols & Tool Integration

  1. #21 Microsoft MCP Catalog 68.6 +0.7
  2. #22 MCP Specification 68.4 +0.5
  3. #23 GitHub MCP Server 67.9 this agent
  4. #24 MCP Go 66.8 −1.1
  5. #25 MCP Context Forge 66.4 −1.5

Bars show each HVTrust score; the tick marks GitHub MCP Server’s 67.9.

Where the 67.9 comes from

HVTrust dimensions vs the Protocols & Tool Integration average

67.9 / 100 · 100.0% confidence

GitHub MCP Server Protocols & Tool Integration average (63 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
12.7 / 25
1.6 above avg 11.1
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
1.3 below avg 12.1
Transparency50% declared license · 50% OSSF Scorecard
14.4 / 17
1.4 above avg 13.0
Maintenance60% last-push freshness · 40% commit activity
18.4 / 20
3.9 above avg 14.5
AdoptionLog-scaled stars · package downloads
10.9 / 20
in line with avg 11.1

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-01
Rank Moved
Rank dropped 10 spots (#429 → #439)
2026-10-21
Rank Moved
Rank rose 10 spots (#433 → #423)
2026-10-20
Rank Moved
Rank dropped 10 spots (#423 → #433)
Maintainer Checklist
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Compare with another agent
View Protocols & Tool Integration Report missing data
89.3
Activity sub-score · out of 100
#23
In Protocols & Tool Integration

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-05 12:09 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-11-05

Activity & Reach

Stars
34.2k
Forks
5.3k
Last Push
2026-11-05
today
Commits (4 wk)
38
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
206
Rank Change
▲4
was #428

Analysis

Activity Inputs

89.3 / 100
StarsRepository reach
27.2 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
19.8 / 25
CommunityFork signal
17.3 / 20

Common questions about GitHub MCP Server

GitHub MCP Server has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does GitHub MCP Server publish package provenance?
No published build provenance is currently detected for GitHub MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does GitHub MCP Server have an OpenSSF Scorecard?
GitHub MCP Server has an OpenSSF Scorecard score of 7.0/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is GitHub MCP Server actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does GitHub MCP Server use?
GitHub MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are GitHub MCP Server's commits signed?
78% of the last 100 commits to GitHub MCP Server are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
GitHub MCP Server appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
1 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to GitHub MCP Server's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-04
Tool Surface Changed
Detected tool/plugin surface changed: none → declared

Maintain GitHub MCP Server?

For maintainers

HVTrust scores GitHub MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 31Surface 1
2026-11-01
Rank Moved
Rank dropped 10 spots (#429 → #439)
2026-10-21
Rank Moved
Rank rose 10 spots (#433 → #423)
2026-10-20
Rank Moved
Rank dropped 10 spots (#423 → #433)
2026-10-17
Rank Moved
Rank dropped 30 spots (#394 → #424)
2026-10-09
Rank Moved
Rank dropped 10 spots (#391 → #401)
2026-10-08
Rank Moved
Rank rose 20 spots (#411 → #391)
2026-10-07
Rank Moved
Rank rose 36 spots (#447 → #411)
2026-10-04
Rank Moved
Rank rose 10 spots (#461 → #451)
2026-10-03
Rank Moved
Rank rose 19 spots (#480 → #461)
2026-10-01
Rank Moved
Rank dropped 12 spots (#464 → #476)
2026-09-24
Rank Moved
Rank dropped 40 spots (#422 → #462)
2026-09-23
Rank Moved
Rank dropped 259 spots (#163 → #422)
2026-09-21
Rank Moved
Rank rose 259 spots (#422 → #163)
2026-09-19
Rank Moved
Rank dropped 14 spots (#414 → #428)
2026-09-18
Rank Moved
Rank dropped 34 spots (#380 → #414)
2026-09-13
Rank Moved
Rank dropped 10 spots (#376 → #386)
2026-09-11
Rank Moved
Rank dropped 18 spots (#356 → #374)
2026-09-07
Rank Moved
Rank dropped 21 spots (#331 → #352)
2026-09-05
Rank Moved
Rank dropped 61 spots (#261 → #322)
2026-09-04
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-09-04
Rank Moved
Rank dropped 12 spots (#249 → #261)
2026-09-03
Rank Moved
Rank dropped 14 spots (#235 → #249)
2026-09-02
Rank Moved
Rank dropped 22 spots (#213 → #235)
2026-08-31
Rank Moved
Rank dropped 22 spots (#185 → #207)
2026-08-29
Rank Moved
Rank dropped 11 spots (#178 → #189)
2026-08-22
Rank Moved
Rank rose 10 spots (#176 → #166)
2026-08-20
Rank Moved
Rank rose 23 spots (#193 → #170)
2026-08-18
Rank Moved
Rank rose 10 spots (#199 → #189)
2026-08-17
Rank Moved
Rank rose 11 spots (#210 → #199)
2026-08-13
Rank Moved
Rank dropped 17 spots (#177 → #194)
2026-08-12
Rank Moved
Rank rose 21 spots (#198 → #177)
2026-08-08
Rank Moved
Rank dropped 29 spots (#158 → #187)
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 67.9 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/github-mcp-server.svg)](https://hvtracker.net/agents/github-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/github-mcp-server"><img src="https://hvtracker.net/badge/github-mcp-server.svg" alt="HVTrust"></a>

Other agents in Protocols & Tool Integration

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON