RepoContext MCP server
io.github.shmindmaster/repocontext·v0.3.1Read-only, commit-pinned repository context for coding agents.
0 stars
Reviews
Write oneNobody has reviewed RepoContext yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
RepoContext tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 1 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Findings (1)
- highPackage @shmindmaster/repocontext not found on npm
code.package-missing
How RepoContext compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,255 servers
Install RepoContext in Claude Code, Cursor or VS Code
Runs npx -y @shmindmaster/repocontext on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add repocontext -- npx -y @shmindmaster/repocontext
What the publisher says
From the RepoContext repository's README, as published. We do not edit it. Read it on GitHub
GitPin
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.
Public-good thesis: evidence for agent-authored software changes should remain inspectable with ordinary local Git, independent of the coding agent or proprietary hosted platform that produced the change.
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>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.
Versioned distribution: This source tree and its packed documentation describe GitPin 0.6.4 without asserting publication status. Availability is established only by independently verifying the npm, MCP Registry, GitHub Release, and Pages receipts. Install with npx -y gitpin@0.6.4 only after the npm receipt resolves. 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
# This exact version becomes usable only after npm publication is verified.
npx -y gitpin@0.6.4 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)
# This exact version becomes usable only after npm publication is verified.
npx -y gitpin@0.6.4 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 : 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.
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
RepoContext: common questions
- Is RepoContext MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the RepoContext safety report
- How do I install RepoContext?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does RepoContext need an API key?
- No secret keys are declared. It reads 1 setting from the environment.
- Is RepoContext maintained?
- The last commit was 42 days ago (2026-09-23). The latest release is v0.3.1.