Skip to main content
Glama
DOC Model Safety Gate

DOC Model Safety Gate

by laceykes

Related Servers

Alternatives to DOC Model Safety Gate

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to propose changes, obtain human or policy approval, and safely apply them with drift checks, idempotency, verified completion, compensation, and a tamper-evident ledger.
      82 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to draft, review, preview, and publish content across multiple websites through typed MCP tools. Ensures safe, policy-gated, and auditable publication without requiring a conventional CMS admin interface.
      Apache 2.0
    • A
      license
      B
      quality
      D
      maintenance
      Enables safe, human-in-the-loop AI document collaboration by letting agents create isolated workspaces, edit tracked files, open reviewable Change Requests, and get human approval before merging, with Git-backed conflict detection and resolution.
      35
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to publish work mid-task and request reviews from real human reviewers, who pin issues and return verdicts so agents can iterate until approved.
      38 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to request human approval before consequential actions, with policy-based routing, phone-based approver decisions, and signed audit evidence.
      32 npm
      MIT

    TDQS

    B3.3/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools map cleanly to a resource+action, and the review tools (listPendingReviews vs getGateReview, reviewOutput vs bulkReviewOutputs) are well separated by granularity. Minor overlap remains between runWorkflow in LIVE mode and publishReviewedRun, and between getRunStatus and getNodeRuns, where an agent must reason about which is authoritative.

    Naming Consistency5/5

    All 15 tools use camelCase with a verb-first pattern (list/get/create/run/review/publish/rollback + noun), including predictable variants like reviewOutput vs bulkReviewOutputs and listWorkflows vs listWorkflowNodes. No mixed conventions or stray vague verbs.

    Tool Count4/5

    15 tools is at the upper edge of the well-scoped band, but it covers two genuine sub-domains (workflow authoring/execution and the Safety Gate review lifecycle). Each tool has a defensible role, though the graph node/edge tools add weight for what may be an occasional editing path.

    Completeness3/5

    Read/create/run/review/publish/rollback are covered well, but the surface is asymmetric: workflows and graph nodes/edges can be created yet there is no updateWorkflow, deleteWorkflow, deleteWorkflowNode, or deleteWorkflowEdge, leaving dead ends in graph editing. There is also no way to list all runs for a workflow, only run-specific status lookups.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues