Skip to main content
Glama
Sign In
closure_drift

closure_drift

by luizfnsilva
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to closure_drift

No user-submitted related servers found.

    Related Servers

    • Foremerge

      naw103
      A
      license
      A
      quality
      B
      maintenance
      Coordination protocol for parallel coding agents, built above Git. The MCP server exposes the full 17-tool lifecycle over stdio: register agents, publish intents with semantic scopes and declared operations, claim work, check for conflicts before code is written, publish ChangeSets, run trusted named verification checks, and record accepted work. Deterministic rules raise findings when two agents'
      18
      529
      Apache 2.0

    • repomcp

      kanchingyg
      A
      license
      Not graded
      quality
      B
      maintenance
      It introspects a repository and exposes guarded MCP tools over stdio, enabling clients to query code and optionally perform mutating operations when explicitly allowed.
      37 npm
      MIT

    • mcp-git

      William12556
      A
      license
      Not graded
      quality
      A
      maintenance
      A local git MCP server. It exposes 12 git operations to an MCP client over stdio, allowing the client to inspect and work with a git repository on your machine, including status, diffs, log, branches, staging, and commits.
      MIT

    • viberevert

      madeinplutofabio
      A
      license
      A
      quality
      B
      maintenance
      Local MCP server for AI agents and vibe coding safety: deterministic risk checks (payments, auth, database, secrets, infrastructure), sessions, checkpoints, policy inspection, and fix prompts. Runs over stdio against a local git repository; no language model judges risk.
      8
      Apache 2.0
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.4/5.0

    Scored across 4 tools

    Disambiguation4/5

    The four tools have largely distinct scopes: would_tag is for a forthcoming single release, check_versions audits all tag history, explain_label drills into one drifted label, and compare examines any two refs. The main possible confusion is between would_tag and check_versions, but their descriptions explicitly separate pre-tag single-release checks from full-history audits.

    Naming Consistency4/5

    Three tools follow a verb_noun pattern (would_tag, check_versions, explain_label), while compare is a bare verb. This is a minor deviation and still readable, with no mixed casing styles.

    Tool Count5/5

    Four tools are well-scoped for a focused read-only version/tag drift audit server. Each tool earns its place and covers a distinct step in the workflow.

    Completeness4/5

    The surface covers pre-tag checking, whole-history auditing, drift explanation, and arbitrary ref comparison. Minor gaps remain, such as listing tags or labels directly, but the core read-only lifecycle for this domain is covered.

    Maintenance

    ActivityActive
    ResponsivenessSyncing

    Resources