Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GITPIN_REGISTRYNoRegistry YAML path (alias: REPOCONTEXT_REGISTRY)
GITPIN_MCP_TOKENNoHTTP bearer token (alias: REPOCONTEXT_MCP_TOKEN)
GITPIN_ALLOWED_HOSTSNoHTTP host allowlist (alias: REPOCONTEXT_ALLOWED_HOSTS)

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
prompts
{
  "listChanged": true
}
resources
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
pin.catalogA

Call first to discover registered Git roots (HEAD SHAs, doc counts, stale). Not a content claim. Use before search/prove.

pin.search_docsA

Find documentation candidates (not claims). Before any factual assertion call pin.prove or pin.prove_set, then pin.verify.

pin.search_codeA

Find code candidates via git grep at HEAD. Never treat hits as final claims—pin.prove then pin.verify (or prove_set/verify_set).

pin.proveA

Primary product tool: one-path evidence pack (slice, path, line, full SHA, content hash, handle, verify next-step). Prefer for every factual claim.

pin.prove_setA

Multi-cite evidence set (1–8 paths, multi-repo OK). Use when an answer needs several citations. Next: pin.verify_set.

pin.get_docA

Read one committed documentation page as a pinned evidence slice with full SHA. Prefer pin.prove for claims.

pin.readA

Read a HEAD-only source slice (path, lines, full SHA). Sensitive paths blocked. Prefer pin.prove when making a claim.

pin.verifyA

Close the prove loop: re-check path@SHA with git show; optional mustContain for claim-text. Reports HEAD match and claimVerdict.

pin.verify_setA

Batch re-check up to 8 citations (from pin.prove_set or a pack). For multi-repo answers and CI citation gates.

pin.analyzeC

EvidenceBrief (knownFacts/gaps/evidenceSetId), documentation gaps, or coverage compare. Decision evidence—not a dump.

pin.inspectA

Inspect HEAD-pinned status, commits, manifests, tests, or recent changes. status shows dirty work excluded from evidence.

pin.compareA

Diff changed paths between two hex revisions. Bounded change evidence for reviews—not semantic search.

Prompts

Interactive templates invoked by user choice

NameDescription
prove-with-git-headForce GitPin product loop: catalog → candidates → pin.prove/prove_set → pin.verify/verify_set. No invented content.

Resources

Contextual data attached and managed by the client

NameDescription
catalogGitPin multi-repo catalog with HEAD SHAs

Latest Blog Posts

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