Is Git MCP Server safe to use?

Git MCP Server has an HVTrust score of 56.1/100 (Grade C), ranked #752 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Git MCP Server?

Git MCP Server scores 56.1/100 on HVTracker's evidence-weighted HVTrust scale. It has 241 GitHub stars and is categorized under MCP Servers.

Git MCP Server

cyanheads/git-mcp-server

A Git MCP server for AI agents. STDIO & Streamable HTTP.

MCP Servers TypeScript Listed Apache-2.0

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

OSSF Scorecard 3.1 / 10

Provenance None

Signed commits 100%

Last push 33d ago

Compare Git MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

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

How Git MCP Server compares in MCP Servers

#417 Apollo.io 56.1 ±0
#418 Webull OpenAPI 56.1 ±0
#419 Git MCP Server 56.1 this agent
#420 Awesome Copilot MCP Server 55.8 −0.3
#421 Pgedge Postgres MCP 55.7 −0.4

Bars show each HVTrust score; the tick marks Git MCP Server’s 56.1.

Where the 56.1 comes from

HVTrust dimensions vs the MCP Servers average

56.1 / 100 · 100.0% confidence

Git MCP Server MCP Servers average (775 agents)

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

8.9 / 25

1.4 below avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

11.1 / 17

1.1 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

9.8 / 20

2.3 below avg 12.1

AdoptionLog-scaled stars · package downloads

10.5 / 20

3.3 above avg 7.2

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-24

Rank Moved

Rank dropped 132 spots (#617 → #749)

2026-09-24

HVTrust Changed

HVTrust down 4.4pts (60.4 → 56.0)

2026-09-24

Activity Score Changed

Activity score down 14pts (57 → 43)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.1/10. Tighten the weakest checks to improve public safety evidence.

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

Refresh maintenance signals The repo was last pushed 33 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for Git MCP Server View MCP Servers Report missing data

43.1

Activity sub-score · out of 100

#419

In MCP Servers

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

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

241

Forks

Last Push

2026-08-24

33 days ago

Commits (4 wk)

Downloads (7d)

3,590

npm

HN mentions (30d)

—

Open Issues

Rank Change

▲5

was #757

Analysis

Activity Inputs

43.1 / 100

StarsRepository reach

14.3 / 30

FreshnessLast push recency

20.4 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

8.2 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.1 / 10

OpenSSF Scorecard · scanned Sep 22, 2026

Signed Commits

100%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests -1

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow -1

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 10

Packaging -1

Pinned-Dependencies -1

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions -1

Vulnerabilities 4

Common questions about Git MCP Server

Git 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 Git MCP Server publish package provenance?

No published build provenance is currently detected for Git 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 Git MCP Server have an OpenSSF Scorecard?

Git MCP Server has an OpenSSF Scorecard score of 3.1/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 Git MCP Server actively maintained?

Slowing down. Last push was 33 days ago — keep an eye on whether activity resumes.

What license does Git MCP Server use?

Git MCP Server ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Git MCP Server's commits signed?

100% of the last 100 commits to Git 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

Git MCP Server appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

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 Git 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-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain Git MCP Server?

For maintainers

HVTrust scores Git 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-24

Rank Moved

Rank dropped 132 spots (#617 → #749)

2026-09-24

HVTrust Changed

HVTrust down 4.4pts (60.4 → 56.0)

2026-09-24

Activity Score Changed

Activity score down 14pts (57 → 43)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank rose 387 spots (#1004 → #617)

2026-09-23

HVTrust Changed

HVTrust up 35.5pts (24.9 → 60.4)

2026-09-22

Newly Listed

First tracked at rank #1004

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Rank Moved

Rank dropped 11 spots (#593 → #604)

2026-09-12

Rank Moved

Rank dropped 21 spots (#555 → #576)

2026-09-11

Rank Moved

Rank dropped 12 spots (#543 → #555)

2026-09-09

Rank Moved

Rank dropped 34 spots (#506 → #540)

2026-09-08

Rank Moved

Rank dropped 15 spots (#491 → #506)

2026-09-07

Rank Moved

Rank dropped 37 spots (#454 → #491)

2026-09-05

Rank Moved

Rank dropped 71 spots (#374 → #445)

2026-09-04

Scorecard Added

OSSF Scorecard: 3.6/10

2026-09-04

Grade Changed

Trust grade D → C

2026-09-04

Rank Moved

Rank rose 680 spots (#1054 → #374)

2026-09-04

HVTrust Changed

HVTrust up 24.5pts (38.9 → 63.4)

2026-09-03

Rank Moved

Rank dropped 55 spots (#999 → #1054)

2026-09-02

Rank Moved

Rank rose 204 spots (#1203 → #999)

2026-09-02

HVTrust Changed

HVTrust up 15.6pts (23.3 → 38.9)

2026-09-01

Rank Moved

Rank dropped 34 spots (#1169 → #1203)

2026-08-31

Rank Moved

Rank dropped 36 spots (#1133 → #1169)

2026-08-30

Rank Moved

Rank dropped 43 spots (#1090 → #1133)

2026-08-29

Rank Moved

Rank dropped 41 spots (#1049 → #1090)

2026-08-28

Rank Moved

Rank dropped 31 spots (#1018 → #1049)

2026-08-27

Rank Moved

Rank dropped 21 spots (#997 → #1018)

2026-08-26

Rank Moved

Rank dropped 103 spots (#894 → #997)

2026-08-24

Rank Moved

Rank rose 102 spots (#998 → #896)

2026-08-24

Activity Score Changed

Activity score up 13pts (48 → 61)

2026-08-17

Rank Moved

Rank rose 11 spots (#1006 → #995)

2026-08-16

Rank Moved

Rank dropped 30 spots (#976 → #1006)

2026-08-10

Rank Moved

Rank dropped 57 spots (#909 → #966)

2026-08-08

Newly Listed

First tracked at rank #899

GitHub → npm: @cyanheads/git-mcp-server

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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