Skip to main content
Glama

Related Servers

Alternatives to GitPin

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for fast, bounded, read-only Git evidence, enabling AI agents to query commit history, diffs, status, and snapshots by parsing repository storage directly.
      345 npm
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI agents to read and search code across many git repositories — files at any branch, tag or commit, history, diffs, blame and cross-repo search — over local paths or remote hosts like GitHub, GitLab and Bitbucket. It is read-only by construction, hiding secrets found in files and working with any MCP client over stdio or Streamable HTTP.
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      A local-first MCP server that provides read-only access to Git repository history, exposing commit metadata and optionally content patches via configurable policies, with optional AI-powered analysis while never modifying Git state.
      2 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP hosts to batch known repository reads, literal searches and Git inspections, summarize noisy command output into compact diagnostics, and recover captured stdout/stderr bytes through bounded, expiring evidence receipts. Optional guarded TypeSafe decisions select among validated candidate actions or escalate to the current host, while deterministic local reads run without a key and never send repository contents externally.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides bounded repository context and edit-grant MCP tools to coding agents such as Codex, indexing local repositories and enabling fingerprint-checked patch application.
      23
      Apache 2.0

    TDQS

    A3.7/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a distinct purpose: reading source vs docs, searching code vs docs, single vs multi evidence creation, single vs batch verification, plus analysis, inspection, and comparison. No two tools overlap in function.

    Naming Consistency5/5

    All tools share the 'pin.' prefix and use lowercase snake_case. The names follow a predictable verb or verb_noun pattern (e.g., prove, prove_set, search_docs, get_doc), creating a clean, uniform naming convention.

    Tool Count5/5

    At 12 tools, the set is well-scoped for its domain. Each tool serves a distinct role in the evidence workflow, and the count is comfortably within the ideal 3-15 range, neither sparse nor bloated.

    Completeness5/5

    The server covers the full evidence lifecycle: discovery (catalog), search (search_docs/search_code), reading (read/get_doc), evidence creation (prove/prove_set), verification (verify/verify_set), analysis (analyze), inspection (inspect), and diffing (compare). No obvious gaps or dead ends for the stated purpose.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing