Skip to main content
Glama
olalonde

MCP-Human

by olalonde
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to MCP-Human

No user-submitted related servers found.

    Related Servers

    • manusia

      chozzz
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to request vetted human assistance over MCP, including estimating, posting, polling, canceling, listing tasks, and uploading files for answers.
      -
    • 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

    • MeatSpace

      zmarten
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to request human decisions for subjective or high-stakes choices through MCP tools like ask_human and provision_api_key.
      -

    • AskMeMCP

      roman-vm
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to request human input through a web interface during execution. Supports single questions, multiple choice selections, hypothesis challenges, and decision workflows for human-in-the-loop interactions.
      6 npm
      MIT

    • AskMeMCP

      thlandgraf
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to request human input through a web interface, allowing them to pause execution and wait for responses via interactive tools like single questions, multiple choice selections, hypothesis challenges, and decision workflows.
      6 npm
      2
      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

    D1.6/5.0

    Scored across 2 tools

    Disambiguation3/5

    The two tools have distinct names suggesting different functions (asking vs. checking status), but without descriptions, an agent may not fully grasp their specific roles or parameters, leading to potential confusion.

    Naming Consistency4/5

    Both tool names follow a camelCase pattern with verb-first structure (askHuman, checkHITStatus), though 'HIT' is capitalized, which is acceptable for an acronym. Overall, naming is clear and consistent.

    Tool Count3/5

    With only 2 tools, the server feels minimal for a domain centered on human interaction. It could be acceptable for a very narrow purpose, but likely leaves users wanting more functionality.

    Completeness2/5

    The tool set covers only asking a human and checking status of a HIT, but lacks essential operations like creating, updating, or listing HITs. This creates significant gaps for typical interaction workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources