Is GitHub MCP Server safe to use?

GitHub MCP Server has an HVTrust score of 66.3/100 (Grade B), ranked #424 of 1328 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for GitHub MCP Server?

GitHub MCP Server scores 66.3/100 on HVTracker's evidence-weighted HVTrust scale. It has 33.1k GitHub stars and is categorized under Protocols & Tool Integration.

GitHub MCP Server

github/github-mcp-server

GitHub's official MCP Server

Protocols & Tool Integration Go Grade B Listed MIT

66.3/100

Rank #424 of 1328

Compare GitHub MCP Server

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

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade C · 2/5 signals

Last push

2026-09-16 · 4d ago

Recent change

Rank +2

Is GitHub MCP Server safe? GitHub MCP Server scores 66.3/100 (Grade B), ranked #424 of 1328 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.3/10; 29% of recent commits are signed; last pushed 2026-09-16. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in Protocols & Tool Integration

#16 NitroStack — 67.8 (B) → #17 MCP Registry — 67.6 (B) → #19 MCP Specification — 66.3 (B) → #20 Graft — 66.2 (B) →

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

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)

Maintainer Checklist

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.

Compare with another agent Get email alerts for GitHub MCP Server View Protocols & Tool Integration Report missing data

90.4

Activity sub-score · out of 100

#18

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 →

Rank Trend

2026-08-11 2026-09-20

Activity & Reach

Stars

33.1k

Forks

5.0k

Last Push

2026-09-16

4 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

163

Rank Change

▲4

was #428

Analysis

HVTrust Dimensions vs Protocols & Tool Integration

66.3 / 100 · 100.0% confidence

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

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

10.6 / 25

in line with avg 10.5

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

0.8 below avg 11.6

Transparency50% declared license · 50% OSSF Scorecard

14.7 / 17

1.9 above avg 12.8

Maintenance60% last-push freshness · 40% commit activity

18.7 / 20

4.7 above avg 14.0

AdoptionLog-scaled stars · package downloads

10.8 / 20

in line with avg 10.6

Activity Inputs

90.4 / 100

StarsRepository reach

27.1 / 30

FreshnessLast push recency

24.4 / 25

ActivityRecent commits

21.7 / 25

CommunityFork signal

17.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

7.3 / 10

OpenSSF Scorecard · scanned Sep 15, 2026

Signed Commits

29%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 8

CI-Tests 10

CII-Best-Practices 0

Code-Review 6

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 10

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 5

SAST 10

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 5

Is GitHub MCP Server safe?

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.3/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 4 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?

28% 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.

Google Gemini

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

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)

2026-07-13

Rank Moved

Rank dropped 16 spots (#109 → #125)

2026-07-06

Grade Changed

Trust grade C → B

2026-07-03

Grade Changed

Trust grade C → B

2026-07-02

Grade Changed

Trust grade B → C

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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.3 · Raw JSON