Skip to main content
Glama
luizfnsilva

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
      538
      Apache 2.0

    • 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

    • mcp-promptdiff

      prasad-a-abhishek
      A
      license
      Not graded
      quality
      B
      maintenance
      Zero-dependency stdio MCP server for token-aware prompt version diffs. Compare prompts or files and get machine-readable token delta reports with confidence labels.
      MIT
    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

    A3.6/5.0

    Scored across 4 tools

    Disambiguation4/5

    Each tool has a distinct read-only purpose: repository-wide label check, HEAD preflight, per-label path explanation, and two-ref comparison. However, explain_label and compare both list differing paths, and would_tag is a specific case of check_versions, creating minor overlap.

    Naming Consistency3/5

    All names use snake_case, but the verb patterns are mixed: check_versions and explain_label follow verb_noun, compare is a bare verb, and would_tag is an unusual modal_verb construction. The inconsistency is noticeable though names remain readable.

    Tool Count5/5

    Four tools is well-scoped for a specialized read-only drift-analysis server; each tool covers a distinct analysis step (bulk check, preflight, explain, compare) and none feels redundant.

    Completeness4/5

    The set covers the core drift-analysis workflow: detect drift, preflight a tag, investigate a drifting label, and compare refs. A minor gap is the lack of a standalone tool to list all version labels or inspect a single non-drift label's closure.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources