Skip to main content
Glama
dvir-shamay

mcp-convention-gate

by dvir-shamay

Related Servers

Alternatives to mcp-convention-gate

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      A
      maintenance
      AI code review against your team's own rules from your repository, before the pull request: two tools, review_changes and get_team_rules. Closed-source binary distributed via GitHub Releases; published in the official MCP Registry as dev.reviewgate/reviewgate.
      2
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents and MCP clients to govern code changes through transactional begin/step/audit/finish workflows, enforce scope and anti-laziness guardrails, and obtain commit clearance tokens before Git commits.
      9
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Extracts a repository's hidden contribution rules (assignment-first, claim-first, DCO, CLA, vouch requirements) from its docs into a machine-readable contribution-gates.json. Also lets clients check a committed gates file for drift and render a plain-language README badge snippet.
      0
      MIT
    • F
      license
      B
      quality
      C
      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
      A
      maintenance
      A trust-first repository copilot to audit signed commit provenance, preview editor configuration safety, and manage Git hook rollouts.
      13
      39 PyPI
      5
      Apache 2.0
    • A
      license
      B
      quality
      B
      maintenance
      Enables coding agents to record, search, and supersede ADR-style decisions and machine-checkable constraints stored as git-friendly markdown in a repository, linked to SpecGate requirement ids, tests and commits. It also surfaces the relevant constraints and decisions for a task and checks a proposed change or diff for conflicts before it is committed.
      7
      0
      MIT

    TDQS

    A4.1/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct phase of the gate workflow: session creation, gate registration, status inspection, commit logging, and listing. There is no meaningful overlap between tool purposes, and the guarded_commit description clearly differentiates it from actually running a commit.

    Naming Consistency3/5

    create_gate_session, register_gate, and list_sessions follow a clean verb_noun pattern, but gate_status is a noun phrase and guarded_commit reads as an adjective_noun rather than an action. The naming is still readable and snake_case is consistent throughout, but the deviations are noticeable enough to lower the score.

    Tool Count5/5

    Five tools is well-scoped for a focused gate-review workflow: create, register, check, log, and list. Each tool serves a necessary function in the lifecycle, and none feel redundant or ornamental.

    Completeness4/5

    The core workflow is covered end-to-end: session creation, gate registration, status verification, commit logging, and session listing. Minor gaps exist, such as no way to retrieve the detailed findings recorded during register_gate or to cancel/abort a session, but these do not block the primary gate-enforcement flow.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues