Index / MCP servers / Human For AI

Human For AI MCP server

Human For AI is a remote MCP server that gives an AI agent 6 tools, among them check_message_thread, check_task_status, get_human_services. It answers at https://humanforai.dev/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 5 September 2026; the last check, on 18 October 2026, succeeded.

Status
Answering
Tools
6
Official
yes, served from humanforai.dev
Reliability
10 of 10 checks
Response time
353 ms
Transport
streamable HTTP
Last checked
18 October 2026

Hire a real human for real-world verification, product testing, AI output review, and errands.

Description as the publisher wrote it.

The 6 tools Human For AI offers

ToolWhat it does
check_message_threadRead the thread for a message you sent: the original text, every reply oldest-first, and whether the operator has answered. Needs the message_id and the access_token from the submission response. An empty replies list means no answer yet —
Inputs: message_id, access_token
check_task_statusLook up a submitted task by its task_id. Returns current status (submitted → accepted → delivered, or rejected), status history with timestamps, seen_by_operator_at (the moment a human actually saw the task — usually well before the first s
Inputs: task_id
get_human_servicesFetch the Human For AI manifest: available services, operator profile (location, languages, working hours), response times, accepted and rejected task types, and trust & safety policy. Call this first to decide whether and how to hire the h
message_human_operatorSend a free-form message to the human operator — questions, scoping, custom or recurring projects, anything that is not yet a ready-made task. reply_to is REQUIRED: an email a human can read (MX-checked), or an https URL to receive the repl
Inputs: message, reply_to, subject, from
reply_in_message_threadAdd a follow-up to a thread you opened — answer a question the operator asked, add detail, correct yourself, or withdraw the request. Prefer this over sending a brand-new message about the same subject. Needs the message_id and access_token
Inputs: message_id, access_token, message
submit_human_taskSubmit a task for the human operator to perform in the real world. Returns a task_id immediately; the human reviews every task before accepting it (this is not instant execution). The operator is push-notified on submission; check_task_stat
Inputs: task_type, description, location_required, location_detail, deadline, output_format

Add Human For AI to your AI client

Every block below points at https://humanforai.dev/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http human-for-ai https://humanforai.dev/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "human-for-ai": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://humanforai.dev/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "human-for-ai": {
      "url": "https://humanforai.dev/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "human-for-ai": {
      "type": "http",
      "url": "https://humanforai.dev/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "human-for-ai": {
      "url": "https://humanforai.dev/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "human-for-ai": {
      "serverUrl": "https://humanforai.dev/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "human-for-ai": {
      "url": "https://humanforai.dev/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: Human For AI
version: 0.0.1
schema: v1
mcpServers:
  - name: Human For AI
    type: streamable-http
    url: https://humanforai.dev/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "human-for-ai": {
      "httpUrl": "https://humanforai.dev/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "human-for-ai": {
      "type": "http",
      "url": "https://humanforai.dev/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "human-for-ai": {
      "url": "https://humanforai.dev/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fhumanforai.dev%2Fmcp&type=streamable_http&id=human-for-ai&name=Human%20For%20AI

Is Human For AI up right now?

It answered our last check on 18 October 2026 in 353 ms. Over 10 checks since 5 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Human For AI

Questions about Human For AI

Is there an official Human For AI MCP server?

Yes. It is published by humanforai.dev and served from humanforai.dev, the vendor's own domain: https://humanforai.dev/mcp.

How many tools does Human For AI have?

6, as returned by the server's own tools/list on 31 August 2026: check_message_thread, check_task_status, get_human_services, message_human_operator, reply_in_message_thread, submit_human_task.

Is Human For AI down?

It answered our last check on 18 October 2026 in 353 ms. Over 10 checks since 5 September 2026 it answered 10.

How do I add Human For AI to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://humanforai.dev/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Human For AI need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: dev.humanforai. Endpoint host: humanforai.dev. ARD identifier: urn:air:dev.humanforai:mcp:humanforai. First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.