Skip to main content
Glama

Related Servers

Alternatives to Secure Git MCP

No user-submitted related servers found.

    Related Servers

    • F
      license
      B
      quality
      D
      maintenance
      Enables secure, policy-controlled operations on local git repositories through MCP, including bounded reads, context-checked patches, allowlisted tasks, and guarded git operations.
      10
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables safe filesystem and git operations confined within a single allowed directory tree, using symlink-resolved path containment to protect against path traversal. Users can read, write, list, and search files, as well as initialize repos and run status, stage, commit, diff, and log operations through MCP.
      11
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only, allowlisted filesystem and Git inspection of explicitly configured local repositories through MCP, with bounded reads and no arbitrary path or write access.
      11 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables policy-first defensive security operations for MCP, providing repository and web-security analysis with controlled authorization, scoped execution, and auditability.
      9
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to inspect local Git repositories through five focused, read-only tools for repository trees, literal text search, numbered file reads, bounded git diffs, and project summaries while confining paths, skipping secret-like and binary files, and enforcing output limits.
      MIT

    TDQS

    B3.2/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools map to clearly distinct git operations, and the four diff variants are separated by explicit language (worktree vs. commit, staged vs. unstaged, two committed trees). The main weak spot is git_unstage vs git_reset, which both describe unstaging a permitted staged set, and git_restore vs git_checkout could be confused by an agent reasoning about destructive state changes.

    Naming Consistency5/5

    Every tool uses the same git_<snake_case_operation> pattern, with verbs matching the underlying git subcommand. No mixed conventions or stray casings.

    Tool Count4/5

    18 tools is on the heavier side, but each corresponds to a real, separate git operation rather than an artificial split. The only near-redundancy is the unstage/reset pair and the four-way diff split, which keeps it just under a full 5.

    Completeness4/5

    The read/inspect surface (status, log, show, diff family, blame, grep, ls-files, branch) and the staging-to-commit lifecycle (add, unstage, reset, restore, commit) are well covered. Gaps exist around merge/rebase, branch delete/rename, tags, stash, and any remote push/pull, though a deliberately local, policy-restricted server may exclude these by design.