GitPin
Provides tools for proving and verifying agent claims against Git repositories, pinning answers to HEAD commits, full SHAs, and specific files and lines, with read-only access and support for local Git roots.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@GitPinProve the claim that the API key is loaded in src/config.ts:42 and verify the SHA."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
GitPin
Pin agent answers to Git HEAD. Path. Line. Full SHA. Prove. Verify.
GitPin is not another “repo context” MCP. That category is full of vector indexes, dump files, and remote GitHub browsers. GitPin is a trust product: index-free, read-only, multi-repo evidence agents must prove and humans 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 category | GitPin product |
Vector / SQLite “repo context” servers | No embeddings, no DB, no reindex |
Filesystem MCP (writes) | Never writes indexed repos |
One-shot repo dumps | Live prove → verify MCP loop |
Grep hits as “the answer” | Candidates → evidence pack → verification report |
GitHub platform MCP | Local Git roots (private/offline) |
Formerly @shmindmaster/gitpin (0.3.x). See migration.
Release:
@shmindmaster/gitpin@0.4.0. Install:npx -y @shmindmaster/gitpin@latest. Node 20+.
Five-minute path
# From a committed Git repository
npx -y @shmindmaster/gitpin@latest init --client codexinit 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 @shmindmaster/gitpin@latest verify \
--repository my-service \
--path docs/architecture.md \
--line 42 \
--sha <full-or-short-hex>Related MCP server: repo-context
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
Job | Tools |
Discover |
|
Find candidates |
|
Prove |
|
Verify |
|
Decide |
|
Inspect / diff |
|
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): stableevidenceSetIdfor multi-repo answers and CI.Verification report (
pin.verify/ CLI): independentgit show; optionalmustContainclaim-text; status includescontradicted.Candidates, not claims: search returns
kind: evidence-candidateswith forcednext: 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
Variable | Purpose |
| Registry YAML path (alias: |
| HTTP bearer token (alias: |
| HTTP host allowlist (alias: |
Default registry: ~/.gitpin/repositories.yaml (falls back to ~/.repocontext/... if present).
Docs
Tools · Compare · FAQ · Migration · Clients · Architecture · Competitive landscape
Site: shmindmaster.github.io/gitpin (GitHub path may stay repocontext; product name is GitPin).
Development
corepack enable
pnpm install --frozen-lockfile
pnpm validate
pnpm build
pnpm verify:package
pnpm site:testLicense
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- Alicense-qualityAmaintenanceProvides local codebase intelligence as an MCP server, enabling AI agents to query dependencies, assess change impact, and produce tamper-evident change evidence packets.Last updated502Apache 2.0
- AlicenseDqualityBmaintenanceRead-only repository context explorer for coding agents. Provides repository exploration tools via CLI or MCP adapter.Last updated1GPL 3.0
- AlicenseBqualityBmaintenanceProvides a read-only MCP interface to query and retrieve verifiable evidence from a local memory bank, supporting search, dossier, chronology, source, and evidence tools.Last updated6BSD Zero Clause
- AlicenseAqualityBmaintenanceA local-first, model-neutral MCP server for collecting and normalizing change-scoped release evidence. It provides deterministic Git change summaries, evidence collection, and review bundles for agent review.Last updated740Apache 2.0
Related MCP Connectors
Read-only Remote MCP for externally grounded AI agent trust receipts.
Independent static verification for exact immutable public GitHub commits.
Agent-native MCP server over the public saagarpatel.dev corpus. Read-only, stateless.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/shmindmaster/gitpin'
If you have feedback or need assistance with the MCP directory API, please join our Discord server