Back to Browse

Gitpin MCP Server

Developer ToolsModerate5.2MCP RegistryLocal
Free

Server data from the Official MCP Registry

Prove and verify multi-repo claims at Git HEAD: path, line, full SHA, no index.

About

Prove and verify multi-repo claims at Git HEAD: path, line, full SHA, no index.

Security Report

5.2
Moderate5.2Moderate Risk

GitPin is a well-structured MCP server for Git evidence verification with strong security fundamentals. The codebase demonstrates careful attention to read-only operations, authentication via bearer tokens, and comprehensive test coverage. Minor code quality concerns around error handling and logging exist, but do not significantly impact the security posture. Permissions align appropriately with the server's purpose of local Git repository access and optional HTTP communication. Supply chain analysis found 4 known vulnerabilities in dependencies (1 critical, 2 high severity). Package verification found 1 issue.

3 files analyzed · 11 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

File System Read

Reads files on your machine. Normal for tools that analyze or process local data.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

process_spawn

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

Path to a GitPin registry YAML listing local Git repository roots.Optional

Environment variable: GITPIN_REGISTRY

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-shmindmaster-gitpin": {
      "env": {
        "GITPIN_REGISTRY": "your-gitpin-registry-here"
      },
      "args": [
        "-y",
        "gitpin"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

GitPin

Validate License: MIT Node.js Version MCP Protocol npm

Make agent-authored changes show exact evidence before merge.

GitPin is an agent-delivery assurance gate with a local evidence MCP. It makes material PR claims cover the actual diff and point to exact committed line slices. The local MCP supplies index-free, read-only, multi-repo evidence that humans and CI can re-check with git show.

Agent claim
    → pin.search_*   (candidates only)
    → pin.prove      (evidence pack: path + line + full SHA + content hash)
    → pin.verify     (git show re-check; HEAD match report)
    → you run: git show <sha>:<path>
Crowded categoryGitPin product
Vector / SQLite “repo context” serversNo embeddings, no DB, no reindex
Filesystem MCP (writes)Never writes indexed repos
One-shot repo dumpsLive prove → verify MCP loop
Grep hits as “the answer”Candidates → evidence pack → verification report
GitHub platform MCPLocal Git roots (private/offline)

Formerly RepoContext 0.3.x. See migration.

Required PR evidence gate

gitpin gate --base <full-base-sha> --head <full-head-sha>

The gate reads policy only from the trusted base commit, reads the submitted manifest only from the head commit, compares the merge-base diff, and verifies exact line-slice hashes. It never executes PR code and never labels a locator match as proof of semantic correctness. Use the GitPin GitHub Action setup to make it a required check. That guide also documents an optional, separate CrewScore check for teams that want written-control coverage alongside GitPin evidence verification.

Current release: GitPin 0.6.3 is verified on npm, the MCP Registry, GitHub Releases, and Pages. Install with npx -y gitpin@0.6.3. Node 20+.

GitPin is maintained by Sarosh Hussain, who leads the project's technical direction. Pendoah is his company and operating context; GitPin remains the product and repository.

Five-minute path

# From a committed Git repository
npx -y gitpin@0.6.3 init --client codex

init creates ~/.gitpin/repositories.yaml outside the repo, runs doctor, prints a first evidence line with full SHA, and paste-ready MCP config. It never edits the indexed repository.

# Independently verify any claim (same contract as pin.verify)
npx -y gitpin@0.6.3 verify \
  --repository my-service \
  --path docs/architecture.md \
  --line 42 \
  --sha <full-or-short-hex>

Product job

When agents invent file contents, mix dirty worktrees, or cite the wrong branch
You want every fact re-checkable with git show <sha>:<path>
GitPin registers local Git roots, serves HEAD-only docs/code, flags stale tracked docs, returns path / line / SHA, and closes the loop with pin.verify.

Agent tool surface (pin.*) — 12 read-only tools

JobTools
Discoverpin.catalog
Find candidatespin.search_docs, pin.search_code
Provepin.prove (primary), pin.prove_set (1–8 cites), pin.get_doc, pin.read
Verifypin.verify, pin.verify_set
Decidepin.analyzeEvidenceBrief
Inspect / diffpin.inspect, pin.compare

Resource: gitpin://catalog. Prompt: prove-with-git-head (forces the product loop).
Cite formats: docs/cite-spec.md. Agent skill template: templates/gitpin-skill.md.

Functionality that is the pivot (not a rename)

  • Evidence pack (pin.prove): claim binding, line slice, full SHA, contentSha256, citation.cite / handle, next-step verify.
  • Multi-cite sets (pin.prove_set / pin.verify_set): stable evidenceSetId for multi-repo answers and CI.
  • Verification report (pin.verify / CLI): independent git show; optional mustContain claim-text; status includes contradicted.
  • Candidates, not claims: search returns kind: evidence-candidates with forced next: pin.prove.
  • EvidenceBrief: multi-repo knownFacts / gaps / stable evidenceSetId (schema v2).
  • Dirty exclusion: uncommitted work is never cited as HEAD evidence.

Explicit non-goals

  • Semantic / embedding search
  • Writing, committing, or pushing
  • Replacing GitHub Issues/PRs automation
  • Indexing non-Git umbrella folders as one “repo”

Configuration

VariablePurpose
GITPIN_REGISTRYRegistry YAML path (legacy compatibility alias: REPOCONTEXT_REGISTRY)
GITPIN_MCP_TOKENHTTP bearer token (legacy compatibility alias: REPOCONTEXT_MCP_TOKEN)
GITPIN_ALLOWED_HOSTSHTTP host allowlist (legacy compatibility alias: REPOCONTEXT_ALLOWED_HOSTS)

Default registry: ~/.gitpin/repositories.yaml (legacy compatibility fallback: ~/.repocontext/... if present).

Docs

Tools · Compare · FAQ · Migration · Clients · Architecture · Competitive landscape

Site: shmindmaster.github.io/gitpin. GitPin is the canonical product and repository name; legacy repocontext references exist only for migration compatibility.

Development

corepack enable
pnpm install --frozen-lockfile
pnpm validate
pnpm build
pnpm verify:package
pnpm site:test

License

MIT

Reviews

No reviews yet

Be the first to review this server!