Skip to main content
Glama

Related Servers

Alternatives to Omega API MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      A local gate that lets agents submit risky tool actions for policy evaluation and receive ALLOW, DENY, or REQUIRE_APPROVE decisions before executing irreversible side effects. It can also open human approval holds and record an activity trail without executing the side effect itself.
      1,549 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A pre-action authorization server for AI agents that classifies tool calls into 14 intent categories, scores risk 0-100, and produces deterministic allow/deny/ask decisions with full audit trail.
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to score their outgoing responses against groundedness and prompt-injection risks mid-turn, returning allow, warn, or block verdicts before the response reaches the user.
      9 npm
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enforces deterministic policy decisions on AI agent tool calls, supporting allow, deny, correct, escalate, and human review actions with verifiable audit receipts.
      200 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A gateway that enforces permissions, sanitization, approval, and audit for AI agent MCP tool calls, with a policy engine and local proxy CLI.
      34 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to retrieve customer, order, ticket, policy, and agreement information, and to prepare or execute state-changing support actions like escalations and follow-ups with confirmation and access control.
      -

    TDQS

    A4.4/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of overlap or confusion. The tool's purpose is clearly specified and distinct by default.

    Naming Consistency5/5

    The single tool name 'omega_judge_turn' follows a clear verb-object pattern and is internally consistent. There is no other tool to conflict with.

    Tool Count3/5

    The server has only one tool, which feels thin for a general-purpose API server. While the tool is well-scoped, the count is borderline per the calibration guidelines.

    Completeness5/5

    Within the narrow domain of judging agent turns, the tool provides a complete lifecycle: it evaluates a turn and returns a decision with the necessary gate action. No obvious dead ends or missing operations are apparent.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues