← Index

io.github.selfagency/git-mcp

io.github.selfagency/git-mcpv0.4.2Developer Tools

A Git MCP server that doesn't suck

The current version, v0.4.2, was published to the official MCP registry on 2026-10-14. It is distributed as @selfagency/git-mcp on npm, filed under Developer Tools by this index, and declares 8 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using io.github.selfagency/git-mcp in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Trust verdict · v1 advisory · method
REVIEWstatus: PARTIALfresh until 2026-11-14 01:02 UTC
screened 2026-10-15tier: scannedgranularity: description-levelsource: registry

Semantic screen found no manipulation pattern in the description. Conformance probe not yet run.

mcpindex.integrity.descriptionpassINFO

evidence“Tool is a Git MCP server that doesn't suck”via static_description

Limits of this verdict
  • - Semantic screen only - the deterministic conformance probe has not run on this server
  • - Confidence is reported but not yet calibrated (v1)
  • - Screen reads the tool description, not the live behavior
  • - advisory
  • - registry description only no input schema
  • - screen model 8b

Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.

Own this server? Test a description on the public screen → It is a separate check from the verdict above, so the two can differ.

That verdict was true at screening time (snapshot 2026-10-24).

Contracts can change after screening, with no version bump. The gate pins io.github.selfagency/git-mcp’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Cite this record

People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.

Markdown
[Independent trust record for io.github.selfagency/git-mcp](https://mcpindex.ai/server/io-github-selfagency-git-mcp) - screening verdict, registry provenance, and contract drift monitoring.
HTML
<a href="https://mcpindex.ai/server/io-github-selfagency-git-mcp">Independent trust record for io.github.selfagency/git-mcp</a> - screening verdict, registry provenance, and contract drift monitoring.
Embed this badge

A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.

Markdown
[![mcpindex](https://mcpindex.ai/api/v1/badge/io-github-selfagency-git-mcp)](https://mcpindex.ai/server/io-github-selfagency-git-mcp)
HTML
<a href="https://mcpindex.ai/server/io-github-selfagency-git-mcp"><img src="https://mcpindex.ai/api/v1/badge/io-github-selfagency-git-mcp" alt="mcpindex verdict" height="20" /></a>
Environment variables
GIT_REPO_PATH

Default repository path for all tool requests. Can also be set via the --repo / --repo-path CLI argument. If omitted, each tool call must supply repo_path explicitly.

GIT_ALLOW_NO_VERIFY

Set to 'true' to expose a no_verify parameter on commit and push tools, passing --no-verify to Git and bypassing pre-commit / pre-push hooks.

GIT_ALLOW_FORCE_PUSH

Set to 'true' to expose a force parameter on push tools. Remote branch protection rules (GitHub/GitLab) are still enforced server-side regardless.

GIT_ALLOW_FLOW_HOOKS

Set to 'true' to allow git_flow to execute git-flow-next-compatible hook and filter programs discovered from git config or repository hook locations.

GIT_SIGNING_KEY
secret

Default signing key: a GPG key ID, an SSH public key path, or empty to use git's configured user.signingkey. Used when GIT_AUTO_SIGN_COMMITS or GIT_AUTO_SIGN_TAGS is enabled.

GIT_SIGNING_FORMAT

Signing format for commits and tags. Accepted values: openpgp, ssh, x509.

GIT_AUTO_SIGN_COMMITS

Set to 'true' to automatically sign all commits produced by this server.

GIT_AUTO_SIGN_TAGS

Set to 'true' to automatically sign all tags produced by this server.

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
5
installability
25
documentation
15
stability
5
Alternatives in Developer Tools