Skip to main content
Glama
Alexnikolaev1

Culprit

by Alexnikolaev1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Culprit

No user-submitted related servers found.

    Related Servers

    • PowerSwarm

      willykeenan
      A
      license
      B
      quality
      B
      maintenance
      Enables an agent to fan out a build into independent targets, each run by a headless coding agent in its own git worktree and gated by a shell-free kill check that must print an exact line. Exposes tools to validate requests, launch and track runs, inspect lane status, cancel or recover runs, and produce review-ready markdown reports, without ever merging or pushing.
      6
      Apache 2.0

    • horizon-ledger

      TTAWDTT
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to read and manage a Git-native decision ledger, providing tools for querying decisions, evidence, cross-repository workspaces, validation, and commit tracing, all operating locally and without a cloud service.
      MIT

    • gpp

      mahabubul470
      A
      license
      B
      quality
      A
      maintenance
      Version-control-native project memory for AI agents: an encrypted knowledge graph whose beliefs are staleness-checked deterministically against repo history — belief bisect names the commit that invalidated a fact, and agents write their own evidence-anchored beliefs via propose_belief. Also exposes changeset proposals and per-changeset token cost reporting; bridges to plain Git.
      9
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: start_bisect initializes a bisect, step_bisect tests one candidate, run_bisect drives stepping to completion, bisect_status reports the current session, and list_bisect_sessions enumerates stored sessions. There is no overlap that would cause misselection.

    Naming Consistency4/5

    start_bisect, step_bisect, and run_bisect follow a consistent verb_bisect pattern, but bisect_status inverts to noun_verb and list_bisect_sessions inserts bisect in the middle. The deviations are minor and the names remain readable and predictable.

    Tool Count5/5

    Five tools is well-scoped for git bisect automation, with each tool earning its place across initialization, stepping, driving, status, and session listing. No obvious bloat or thinness.

    Completeness4/5

    The core bisect lifecycle is covered: start, step, run, status, and list sessions. Minor gaps exist, such as no explicit abort/cleanup or delete-session operation, but agents can work around this by ignoring or overwriting sessions.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources