Skip to main content
Glama
aryaminus

ControlKeel

by aryaminus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

Related Servers

Alternatives to ControlKeel

No user-submitted related servers found.

    Related Servers

    • mcp-gatekeeper

      saimsheikh
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides a governance layer for MCP servers, enforcing policy-based allow/deny/approval rules, requiring human approval for risky calls, and recording an auditable trail of every AI agent tool call.
      MIT

    • veor

      winterbim
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides a governed execution boundary for AI agents, enforcing deterministic policy, one-shot human approvals, and signed receipts for MCP tool effects.
      MIT

    • codex-router

      rixzkiye
      A
      license
      Not graded
      quality
      B
      maintenance
      A durable MCP control plane for starting, observing, steering, continuing, cancelling, and handing off long-running coding agents, with bounded MCP calls and persistent worktrees.
      5 npm
      MIT

    • WhitePact

      Guruprasath-Annadurai
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that exposes governance, trust-scoring, compliance, guardrail, cost, drift, and supply-chain scanning tools and resources to any MCP client over stdio, Streamable HTTP, or legacy HTTP+SSE. It lets agents route every tool call through a deterministic five-way decision (allow, redact, require approval, deny, or quarantine) with hash-chained evidence, human approval workflows, and in-agent trust gates for LangChain, LangGraph, and Google ADK.
      30
      2
      MIT

    • sp-devcontrol

      PRojas01
      A
      license
      Not graded
      quality
      A
      maintenance
      Local governance layer for AI-assisted development, providing human authorization gates, policy enforcement, change approval workflow, and rollback capabilities through a universal MCP server.
      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

    A3.7/5.0

    Scored across 55 tools

    Disambiguation3/5

    Most tools have distinct purposes (git, fs, review, memory), but there is significant conceptual overlap: ck_memory_search vs ck_experience_search both perform freeform search over findings/tasks; ck_context vs ck_context_pack are adjacent and rely on descriptions to separate; several ck_experience_* tools overlap with ck_memory_search. Multi-mode tools like ck_task and ck_session pack many actions into one tool, making boundaries fuzzier.

    Naming Consistency4/5

    Strong consistent ck_<domain>_<action> pattern (ck_fs_read, ck_git_diff, ck_memory_record, ck_review_submit). Minor deviations exist where domain is dropped (ck_validate, ck_route, ck_delegate, ck_copilot, ck_loop), but these are still readable and follow the ck_ prefix convention.

    Tool Count2/5

    55 tools is heavy, well beyond the 15-tool sweet spot, and the surface spans many sub-domains (git, fs, memory, review, budget, delegate, deploy, skills, checkpoints, worktrees, copilot). This breadth makes selection costly and increases the chance of picking the wrong tool.

    Completeness4/5

    Coverage is broad and deep, with CRUD/lifecycle for memory, findings, reviews, goals, checkpoints, sessions, and git. Read-only exploration is well covered. Some operations are missing or indirect (e.g., no direct memory update tool—only re-record with source_id; no push tool), but most workflows can be completed.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources