Skip to main content
Glama
finalapproval

final-approval

by finalapproval
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to final-approval

No user-submitted related servers found.

    Related Servers

    • @looppause/mcp

      soteeabam
      A
      license
      Not graded
      quality
      C
      maintenance
      Pauses AI agent execution and routes approval requests to humans via Slack or email, with cryptographically signed proof of the human's decision.
      25 npm
      MIT

    • Approval Gate

      Keldrik
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides a human approval gate for AI agents, enabling interactive inline cards for approving, editing, or rejecting actions before they are executed.
      MIT

    • LoopIn MCP Server

      nicholasemccormick
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to pause execution at critical decision points and request human review before proceeding. Provides tools for creating interrupts, polling for decisions, and managing approvals through a simple REST API interface.
      5 npm
      MIT
    • @quirna/mcp by quirna

      @quirna/mcpofficial

      quirna
      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.
      MIT

    • AgentGate

      agentkitai
      A
      license
      A
      quality
      A
      maintenance
      Human-in-the-loop approval gateway for agent tool calls: agents request, policies decide, humans approve via Slack/Discord/web — with an OWASP-LLM-Top-10-tagged audit trail. Self-hostable.
      10
      18 npm
      33
      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.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clear and distinct purpose for submitting approvals.

    Naming Consistency5/5

    The tool name 'submit_approval' follows a clear verb_noun pattern. Since there is only one tool, consistency is inherently perfect with no deviations or mixed conventions.

    Tool Count2/5

    A single tool is too few for most practical server purposes, as it severely limits functionality and scope. While it might serve a narrow use case, it feels thin and incomplete for typical agent workflows.

    Completeness2/5

    The server's domain appears to be approval workflows, but with only a submit tool, there are significant gaps. Missing operations likely include checking approval status, listing pending approvals, or handling approvals programmatically, which could cause agent failures.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources