Skip to main content
Glama
TomPhillipsLabs

loopquest-mcp

by TomPhillipsLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to loopquest-mcp

No user-submitted related servers found.

    Related Servers

    • Datashift MCP Server by datashift-io

      Datashift MCP Serverofficial

      datashift-io
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to submit tasks for human or AI review and receive decisions via MCP tools, adding human review checkpoints to workflows.
      MIT

    • multi-judge-consensus

      ElonAug7
      A
      license
      A
      quality
      B
      maintenance
      Enables AI/agent-generated content to be reviewed by a cross-vendor committee of LLMs, returning verdicts, issues, votes, and cost estimates through an MCP review tool for consensus-based hallucination defense before shipping.
      1
      1
      GPL 3.0

    • MCP-Human

      olalonde
      A
      license
      D
      quality
      F
      maintenance
      Enables AI assistants to request human input by creating tasks on Amazon Mechanical Turk, integrating human-in-the-loop capabilities via the MCP standard.
      2
      4 npm
      26
      ISC

    • jev

      nandansrikrishna
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to evaluate single records or batches with dynamically authored typed questions, returning structured decisions and probabilities.
      MIT
    • mcp-review by apatureai

      mcp-reviewofficial

      apatureai
      A
      license
      A
      quality
      A
      maintenance
      An MCP server for in-loop design review of web previews. It enables agents to submit a preview URL, receive structured findings with suggested fixes, and recheck after applying changes, while never editing code itself.
      5
      1
      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.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: one creates a review task, the other checks its status. No overlap or ambiguity.

    Naming Consistency5/5

    Both tool names follow a consistent verb_noun pattern in snake_case: create_review_task and get_task_status.

    Tool Count4/5

    With only 2 tools, the server is lightly scoped but still covers the core review workflow. The count is slightly low but acceptable for a focused utility.

    Completeness3/5

    The tool surface covers creation and status polling, but lacks operations like canceling or listing tasks, which could be needed in real workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources