Skip to main content
Glama
shmindmaster

GitPin

by shmindmaster
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to GitPin

No user-submitted related servers found.

    Related Servers

    • weavatrix-git

      Weavatrix
      A
      license
      Not graded
      quality
      A
      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
      MIT

    • git-history-viewer

      peekaboo-develop
      A
      license
      Not graded
      quality
      B
      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.
      61
      Apache 2.0

    • lattice

      moulwyse
      A
      license
      Not graded
      quality
      A
      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.
      14
      Apache 2.0
    • mentu-navigator-mcp by mentu-ai

      mentu-navigator-mcpofficial

      mentu-ai
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides read-only, provenance-first repository navigation for agents and humans, with ranked lexical retrieval, exact query, document handles, symbol context, and change impact analysis.
      107
      Apache 2.0

    • Change Trace MCP

      Canlendula
      A
      license
      A
      quality
      B
      maintenance
      A local-first, model-neutral MCP server for collecting and normalizing change-scoped release evidence. It provides deterministic Git change summaries, evidence collection, and review bundles for agent review.
      7
      6
      Apache 2.0
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    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

    ActivityActive
    ResponsivenessWithin a week

    Resources