Skip to main content
Glama
vaibot-io

@vaibot/mcp-server

Official
by vaibot-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to @vaibot/mcp-server

No user-submitted related servers found.

    Related Servers

    • approval-gate

      yulinlina
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that provides human-in-the-loop approval for risky AI agent actions, with durable state and audit logs.
      MIT

    • governed-mcp

      rsiraj0
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that enforces governance on agentic decisions with auditable evidence records, providing tools for understanding, calibrating confidence, and navigating handoffs based on policy.
      1
      -

    • agent-security-gateway

      Un1u6ky
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that provides a security gateway for AI agents, enforcing allow/confirm/deny policies on tool calls and requiring human approval for risky operations, with full audit logging.
      -
    • Oakallow MCP Server by oakallow

      Oakallow MCP Serverofficial

      oakallow
      A
      license
      Not graded
      quality
      D
      maintenance
      Runtime permission, approval, and audit governance for AI agent tool execution, enabling human oversight of risky actions via an MCP server.
      1
      MIT

    • gov-mcp

      liuhaotian2024-prog
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enforces runtime governance on AI agent actions — file access, command execution, delegation chains, and permission escalation.
      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

    A4.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct role in the governance workflow: decide pre-checks actions, finalize reports outcomes, receipts lists history, and approve handles pending decisions. There is no overlap or ambiguity between them.

    Naming Consistency4/5

    All tools share the 'vaibot_' prefix and mostly use verb-based naming (decide, finalize, approve). 'receipts' is a noun rather than a verb, deviating slightly from the action-oriented pattern, but the prefix and clear purpose keep it readable.

    Tool Count5/5

    Four tools provide a well-scoped governance surface: pre-check, post-report, list, and approve. This is neither too thin nor excessive for the stated purpose.

    Completeness5/5

    The workflow is fully covered: initiate with decide, execute, finalize with the run_id, review via receipts, and handle pending approvals with approve. There are no obvious missing operations for the governance domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources