Skip to main content
Glama
confirm-ai

confirm-mcp

by confirm-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to confirm-mcp

No user-submitted related servers found.

    Related Servers

    • Relay

      andeya
      A
      license
      Not graded
      quality
      B
      maintenance
      Adds a human-in-the-loop checkpoint to MCP-capable AI coding agents, enabling them to pause and request user feedback before executing actions.
      12 npm
      71
      MIT

    • Agent Inbox

      Zijian-Ni
      A
      license
      Not graded
      quality
      C
      maintenance
      A local human-in-the-loop gate for AI agents that blocks actions until human approval, with timeout defaulting to denial.
      12 npm
      MIT

    • AgentGuard MCP Server

      vaasu202
      F
      license
      Not graded
      quality
      B
      maintenance
      Provides a secure MCP boundary for AI agents, intercepting and validating tool calls, redacting secrets, and requiring human approval for sensitive actions with a tamper-evident audit trail.
      -

    • 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

    • call-a-human-mcp

      nishantmodak
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that enables AI agents to pause and request human approval or information via Slack, Telegram, or macOS dialogs before proceeding with actions.
      2
      15
      Apache 2.0
    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.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one initiates an approval request and blocks, the other polls an existing request's status. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    Both tool names follow the consistent verb_noun pattern (request_approval, check_approval), using snake_case and parallel structure. This is a predictable and coherent naming convention.

    Tool Count4/5

    With only 2 tools, the server is slightly under the typical 3-15 range, but the scope is highly focused on approval workflows. Both tools are essential and the count does not feel excessive or severely lacking.

    Completeness4/5

    The core lifecycle of approval is covered: creating a request and checking its status. A possible gap is cancellation of an approval request, but the blocking behavior of request_approval partially mitigates this, so the missing functionality is minor.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources