Skip to main content
Glama
cqnce-app

@cqnce/mcp-server

by cqnce-app
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @cqnce/mcp-server

No user-submitted related servers found.

    Related Servers

    • vantagate-mcp-server

      Aderix
      A
      license
      Not graded
      quality
      D
      maintenance
      Human-in-the-Loop authorization gateway for AI Agents. Securely pause MCP workflows and route high-risk actions to human approvers via Slack or Email.
      36 npm
      1
      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.
      -

    • veor

      winterbim
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides a governed execution boundary for AI agents, enforcing deterministic policy, one-shot human approvals, and signed receipts for MCP tool effects.
      MIT

    • 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
    Deploy Server
    Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4/5.0

    Scored across 6 tools

    Disambiguation4/5

    The tools are mostly distinct, but submit_authorization_request and wait_for_approval overlap in that wait_for_approval also submits. The descriptions clarify the difference (blocking vs non-blocking), so an agent can distinguish them with careful reading. All other tools have clear boundaries.

    Naming Consistency4/5

    Tool names follow a verb_noun pattern with verbs like submit, poll, wait, cancel, list, get. However, the noun varies (authorization_request, request_status, approval, request, requests), so it is not perfectly uniform. The pattern is still predictable and easy to learn.

    Tool Count5/5

    Six tools cover the full authorization request workflow without redundancy or bloat. Each tool serves a distinct step in the lifecycle, making the count well-scoped for the server's purpose.

    Completeness5/5

    The tool set provides complete coverage of the authorization request domain: submit, wait/poll for status, cancel, list, and get details. There are no obvious missing operations for an agent-driven human approval workflow.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources