@abhishekmcp/git

MCPcommunity
v0.2.0AbhishekMITUpdated 3mo agonpmGitHub

MCP server for local Git repositories — status, log, diff, file history, branches, and gated stage/commit — pure-JS (isomorphic-git), no git binary, from any MCP client.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
258Downloads/wk
3mo agoLast update
Package
AuthorAbhishek
LicenseMIT
Version0.2.0
Sourcenpm+mcp-registry
npm@abhishekmcp/git
GitHubAbhishekkumar2021/mcp-suite
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
ProvenanceAttested · unverified by Forge
Dependencies60 resolved · 1 with advisories
Tool surface20 tools · none privileged
Security scan✓ Cleanv0.2.0 · 1mo agoHow well does this scan work?
MODERATE@hono/node-server@1.19.17Node.js Adapter for Hono: Path traversal in `serve-static` on Windows via encoded backslash (`%5C`) · transitive
EvalsNone
IndexedJun 29, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

20 tools · none privileged
Statically extracted from the published packagev0.2.0 · 1mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

git_statusNo description published

This tool published no description. Forge does not invent one.

git_logNo description published

This tool published no description. Forge does not invent one.

git_showNo description published

This tool published no description. Forge does not invent one.

git_diffNo description published

This tool published no description. Forge does not invent one.

git_file_historyNo description published

This tool published no description. Forge does not invent one.

read_file_atNo description published

This tool published no description. Forge does not invent one.

list_branchesNo description published

This tool published no description. Forge does not invent one.

list_tagsNo description published

This tool published no description. Forge does not invent one.

current_branchNo description published

This tool published no description. Forge does not invent one.

search_logNo description published

This tool published no description. Forge does not invent one.

list_remotesNo description published

This tool published no description. Forge does not invent one.

git_stageNo description published

This tool published no description. Forge does not invent one.

git_unstageNo description published

This tool published no description. Forge does not invent one.

git_commitNo description published

This tool published no description. Forge does not invent one.

git_create_branchNo description published

This tool published no description. Forge does not invent one.

git_checkoutNo description published

This tool published no description. Forge does not invent one.

git_cloneNo description published

This tool published no description. Forge does not invent one.

git_fetchNo description published

This tool published no description. Forge does not invent one.

git_pullNo description published

This tool published no description. Forge does not invent one.

git_pushNo description published

This tool published no description. Forge does not invent one.

0 of 20 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for local Git repositories — status, log, diff, file history, branches, and gated stage/commit — pure-JS (isomorphic-git), no git binary, from any MCP client.

Keywords
mcpmodelcontextprotocolgitisomorphic-gitclaude
Alternatives
Comparing tool surfaces…

Tools exposed

20 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

No dependency coverage

This package was last scanned before Forge began storing the resolved tree. The next scan will record it.

Topics

Related in git & code hosting