gitpin
Require exact PR evidence before agent-authored changes merge. Local evidence MCP + base-trusted gate.
Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
Verified is a snapshot. Live keeps it current, and builds your track record.
⚡ Connect GitHub → continuous verification on every pushwhy connect →Who stands behind it
shmindmaster
Source: Glama · also listed on github_repo_search
Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →
Install from
The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.
These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.
pin.catalogCall first to discover registered Git roots (HEAD SHAs, doc counts, stale). Not a content claim. Use before search/prove.
pin.search_docsFind documentation candidates (not claims). Before any factual assertion call pin.prove or pin.prove_set, then pin.verify.
pin.search_codeFind code candidates via git grep at HEAD. Never treat hits as final claims—pin.prove then pin.verify (or prove_set/verify_set).
pin.provePrimary product tool: one-path evidence pack (slice, path, line, full SHA, content hash, handle, verify next-step). Prefer for every factual claim.
pin.prove_setMulti-cite evidence set (1–8 paths, multi-repo OK). Use when an answer needs several citations. Next: pin.verify_set.
pin.get_docRead one committed documentation page as a pinned evidence slice with full SHA. Prefer pin.prove for claims.
pin.readRead a HEAD-only source slice (path, lines, full SHA). Sensitive paths blocked. Prefer pin.prove when making a claim.
pin.verifyClose the prove loop: re-check path@SHA with git show; optional mustContain for claim-text. Reports HEAD match and claimVerdict.
pin.verify_setBatch re-check up to 8 citations (from pin.prove_set or a pack). For multi-repo answers and CI citation gates.
pin.analyzeEvidenceBrief (knownFacts/gaps/evidenceSetId), documentation gaps, or coverage compare. Decision evidence—not a dump.
pin.inspectInspect HEAD-pinned status, commits, manifests, tests, or recent changes. status shows dirty work excluded from evidence.
pin.compareDiff changed paths between two hex revisions. Bounded change evidence for reviews—not semantic search.
Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.
simple-git has blockUnsafeOperationsPlugin bypass via case-insensitive protocol.allow config key enables RCE
simple-git is vulnerable to Remote Code Execution
simple-git Affected by Command Execution via Option-Parsing Bypass
yaml is vulnerable to Stack Overflow via deeply nested YAML collections
ComSpecGITHUB_OUTPUTGITHUB_REF_NAMEGITHUB_REF_TYPEGITHUB_STEP_SUMMARYGITPIN_ALLOWED_HOSTSHTTP host allowlist (alias: REPOCONTEXT_ALLOWED_HOSTS)GITPIN_CI_USE_DISTGITPIN_CONTAINER_PORTGITPIN_DEMO_PACE_MSGITPIN_DEMO_VIDEO_DIRGITPIN_INDEX_PATHGITPIN_MCP_TOKENHTTP bearer token (alias: REPOCONTEXT_MCP_TOKEN)GITPIN_MCP_URLGITPIN_QWEN_TTS_CLIGITPIN_QWEN_TTS_PYTHONGITPIN_REGISTRYRegistry YAML path (alias: REPOCONTEXT_REGISTRY)HF_HOMEHOSTPOSTHOG_GITPIN_PROJECT_KEYREPOCONTEXT_ALLOWED_HOSTSGITPIN_ALLOWED_HOSTS HTTP host allowlist (alias: )REPOCONTEXT_CONTAINER_PORTREPOCONTEXT_DEMO_NARRATION_PROVIDERREPOCONTEXT_DEMO_PACE_MSREPOCONTEXT_DEMO_ROOTREPOCONTEXT_DEMO_VIDEO_DIRREPOCONTEXT_INDEX_PATHREPOCONTEXT_MCP_TOKENGITPIN_MCP_TOKEN HTTP bearer token (alias: )REPOCONTEXT_PACKAGE_TARBALLREPOCONTEXT_REGISTRYGITPIN_REGISTRY Registry YAML path (alias: )REPOCONTEXT_SITE_PORTPORTDependencies
10 dependencies, 1 flagged: @playwright/test
Tool annotations
No tools have read-only/destructive annotations
Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.
All four hints declared on every tool
12/12 tools missing one or more hints — pin.catalog (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); pin.search_docs (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); pin.search_code (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +9 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.
For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.
Tool inputs are validated
10/12 tool handlers declare input schemas (83%)
Declare an inputSchema with zod/joi/yup on every tool definition.
Tool handlers catch errors
Only 0/12 tool handlers wrap calls in try/catch (0%)
Wrap each tool handler body in try/catch and return a structured error response.
Shell command execution
3 child_process calls — runs shell commands
Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.
Production dependencies are patched
1 critical, 2 high severity in production deps — simple-git@3.27.0 (critical), simple-git@3.27.0 (high)
Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.
Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.
[](https://m8ven.ai/mcp/shmindmaster/gitpin)?variant=verified from the URL.Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.
https://m8ven.ai/api/mcp/tool-check