GitPin
NPM · GITPIN
Prove and verify multi-repo claims at Git HEAD: path, line, full SHA, no index.
Available components
Last scanned (4 hours ago)
Scores higher than 0% of npm servers
Category Code Search and Documentation
Recent critical change
CVE-2026-102828 affects this package (6 Oct 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security73
- No malware found by supply-chain analysis.Pass
- CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. See how to fix → View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 32 of 98 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to shmindmaster/gitpin). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 49 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 658 tokens (~50/item across 13 items; 12 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Security disclosure: pass → unverified ▼ functional
- Stability: pass → 0.80 functional
- 30 Oct 26 0
- Stability: 0.97 → pass security
- 29 Oct 26 0
- Stability: pass → 0.97 functional
- 28 Oct 26 0
- Security disclosure: unverified → pass ▲ functional
- 27 Oct 26 0
- Security disclosure: pass → unverified ▼ functional
- 23 Oct 26 0
- Stability: 0.97 → pass security
- 22 Oct 26 0
- Stability: pass → 0.97 functional
- 16 Oct 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/gitpin@0.6.4
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | shmindmaster/gitpin |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/shmindmaster/gitpin/.github/workflows/release.yml@refs/tags/v0.6.4 |
| Rekor log index | 2858121701 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:c8329f2193040489bf68f0f3b4dd2137d5abaa6559157bd05fdd1e87b19ac824d759b450a3269b7dd43a94f799268b9d5dad6af5723cba51b7debd10b |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 4 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-v5rq-49vh-5v5c | CVE-2026-102829 | critical | yes | |
| GHSA-858h-whjf-mvg5 | CVE-2026-102827 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H | yes |
| GHSA-g4wm-2vf7-vfgr | CVE-2026-102826 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H | yes |
| GHSA-x6jw-m9v5-85vh | CVE-2026-102828 | critical | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 98 packages
| Packages resolved | 98 |
|---|---|
| Stale | 32 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
pin.analyze ~34
EvidenceBrief (knownFacts/gaps/evidenceSetId), documentation gaps, or coverage compare. Decision evidence—not a dump.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
pin.catalog ~43
Call first to discover registered Git roots (HEAD SHAs, doc counts, stale). Not a content claim. Use before search/prove.
| Name | Type | Req | Description |
|---|---|---|---|
| view | string | – | – |
No output schema declared.
No examples provided.
pin.compare ~47
Diff changed paths between two hex revisions. Bounded change evidence for reviews—not semantic search.
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | yes | – |
| head | string | yes | – |
| repository | string | yes | – |
No output schema declared.
No examples provided.
pin.get_doc ~45
Read one committed documentation page as a pinned evidence slice with full SHA. Prefer pin.prove for claims.
| Name | Type | Req | Description |
|---|---|---|---|
| repository | string | yes | – |
| sourcePath | string | yes | – |
No output schema declared.
No examples provided.
pin.inspect ~53
Inspect HEAD-pinned status, commits, manifests, tests, or recent changes. status shows dirty work excluded from evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| operation | string | yes | – |
| repository | string | yes | – |
No output schema declared.
No examples provided.
pin.prove ~80
Primary product tool: one-path evidence pack (slice, path, line, full SHA, content hash, handle, verify next-step). Prefer for every factual claim.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | – | – |
| lineEnd | integer | – | – |
| lineStart | integer | – | – |
| repository | string | yes | – |
| sourcePath | string | yes | – |
No output schema declared.
No examples provided.
pin.prove_set ~47
Multi-cite evidence set (1–8 paths, multi-repo OK). Use when an answer needs several citations. Next: pin.verify_set.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
No output schema declared.
No examples provided.
pin.read ~66
Read a HEAD-only source slice (path, lines, full SHA). Sensitive paths blocked. Prefer pin.prove when making a claim.
| Name | Type | Req | Description |
|---|---|---|---|
| lineEnd | integer | – | – |
| lineStart | integer | – | – |
| repository | string | yes | – |
| sourcePath | string | yes | – |
No output schema declared.
No examples provided.
pin.search_code ~53
Find code candidates via git grep at HEAD. Never treat hits as final claims—pin.prove then pin.verify (or prove_set/verify_set).
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
| repository | string | yes | – |
No output schema declared.
No examples provided.
pin.search_docs ~48
Find documentation candidates (not claims). Before any factual assertion call pin.prove or pin.prove_set, then pin.verify.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
| repository | string | – | – |
No output schema declared.
No examples provided.
pin.verify ~74
Close the prove loop: re-check path@SHA with git show; optional mustContain for claim-text. Reports HEAD match and claimVerdict.
| Name | Type | Req | Description |
|---|---|---|---|
| line | integer | – | – |
| mustContain | string | – | – |
| repository | string | yes | – |
| sha | string | yes | – |
| sourcePath | string | yes | – |
No output schema declared.
No examples provided.
pin.verify_set ~53
Batch re-check up to 8 citations (from pin.prove_set or a pack). For multi-repo answers and CI citation gates.
| Name | Type | Req | Description |
|---|---|---|---|
| evidenceSetId | string | – | – |
| items | array | yes | – |
No output schema declared.
No examples provided.
How do I install the GitPin MCP server?
GitPin runs locally as an npm package, launched with npx -y gitpin. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · gitpin
claude mcp add shmindmaster-gitpin -- npx -y gitpin
What is the GitPin MCP server?
GitPin is an MCP server listed in the public MCP registry as io.github.shmindmaster/gitpin. Prove and verify multi-repo claims at Git HEAD: path, line, full SHA, no index. This page covers its npm package (gitpin).
What tools does the GitPin MCP server expose?
GitPin exposes 12 tools: pin.catalog, pin.search_docs, pin.search_code, pin.prove, pin.prove_set, and 7 more. Their descriptions and schemas cost roughly 643 tokens of context every time the server is loaded.
Is the GitPin MCP server still maintained?
GitPin is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the GitPin MCP server under?
GitPin declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.