Human For AI

dev.humanforai由 humanforai.dev 发布官方发布者v0.1.4更新于 Oct 24, 2026

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

已验证Streamable HTTP可网页运行效率与工作流沟通与协作

概览

AI 生成的概览

将 AI 助手连接到真人操作员,用于现实世界核实、产品测试、人工判断和本地跑腿任务。

可以做什么
查询真人操作员的服务目录、可接受的任务类型、工作时间和信任政策,并通过消息与操作员沟通,以电子邮件或签名 webhook 接收回复,用于定制或长期项目。提交现实世界任务,例如核实地点、价格或说法,测试应用,审阅 AI 输出或收集数据,然后用时间戳、操作员查看时间和预计交付时间轮询状态。使用消息 ID 和访问令牌读取并回复消息线程。
适用场景
当任务需要真人到场、人的感知或人的判断而助手无法提供时使用:确认现实世界中某事物确实存在、让人安装并测试产品,或在输出上线前获得人工审阅。
运行要求
可作为远程 streamable HTTP 端点使用,也可通过本地 npm 包(npx humanforai)作为连接托管端点的 stdio 代理运行。未声明 API 密钥或身份验证。提交任务和消息需要提供联系邮箱或用于接收回复的 https webhook 地址,并需要访问托管服务的网络连接。
安装前请注意
任务由第三方真人操作员执行,提交的内容会离开你的控制,可能包含个人或业务信息;提交内容应完整自洽,但避免不必要的敏感数据。操作员会审核并可能拒绝任务,交付并非即时。服务仅在概念验证试点期间免费,价格可能变化。消息线程需要提交时返回的访问令牌。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Human For AI,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/dev.humanforai%2Fhumanforai/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

{
  "mcpServers": {
    "human-for-ai": {
      "type": "http",
      "url": "https://humanforai.dev/mcp"
    }
  }
}

README

humanforai

[CI] [humanforai-mcp MCP server]

MCP server for Human For AI — a human endpoint for AI agents. Let your AI agent hire a real human operator for tasks that need physical presence, human perception, or human judgment:

  • Real-world verification — confirm a place, product, price, or claim exists, with photo/text evidence
  • Product or app testing — a real human installs, uses, and reports
  • Human judgment and feedback — tone, clarity, trustworthiness, design quality
  • AI output review — human review before your output reaches production
  • Data collection — gathering/labeling that needs human perception or local access
  • Local physical-world tasks — visit, photograph, check, measure, observe
  • …and more — call get_human_services for the full catalog

All services are free during the proof-of-concept pilot. No API key, no payment. Every task is reviewed by the human operator before acceptance; illegal, harmful, deceptive, unsafe, or privacy-invasive tasks are rejected. First response within 12 hours, any day of the week — typically much faster: the operator is push-notified the moment a task arrives.

Tools

ToolPurpose
get_human_servicesService catalog, accepted task types, limits
submit_human_taskSubmit a task; returns a task_id for status polling
check_task_statusPoll a submitted task by task_id
message_human_operatorAsk questions / scope work before submitting

Status transparency

check_task_status shows progress in real time, not just the final result:

  • seen_by_operator_at — the moment a human actually saw the task (usually well before the first status change)
  • eta — operator-set delivery estimate, added when the task is accepted
  • status_history — every transition (submitted → accepted → delivered, or rejected) with timestamps

Setup

Claude Code

bash
claude mcp add human-for-ai -- npx -y humanforai

Claude Desktop / other MCP clients (stdio)

json
{  "mcpServers": {    "human-for-ai": {      "command": "npx",      "args": ["-y", "humanforai"]    }  }}

Clients with native remote MCP support

You don't need this package — connect directly to the hosted endpoint (streamable HTTP, no auth):

https://humanforai.dev/mcp

E.g. Claude (Settings → Connectors → Add custom connector), or:

bash
claude mcp add --transport http human-for-ai https://humanforai.dev/mcp

How it works

This package is a thin stdio proxy to the hosted Human For AI MCP endpoint. Tool definitions come from the live server, so they are always current — the package itself has no logic to go stale.

Previously published as human-api, which still works but is deprecated in favor of this package.

Typical flow

  1. get_human_services — see what the operator can do
  2. submit_human_task — be specific and self-contained; include contact_email to receive the deliverable
  3. check_task_status — poll with the returned task_id

Links

License

MIT

来源:README.md,提交 c067642

工具

6

get_human_services

List human services

Fetch 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 human. The catalog is examples, not limits — unlisted needs are welcome as custom_human_in_the_loop.

无需输入参数。

submit_human_task

Submit a task to the human

Submit 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_status shows seen_by_operator_at once a human has seen the task. Free during the pilot. contact_email must be a real mailbox (MX-checked) — it is how the deliverable reaches you. No mailbox? Set delivery to 'status_poll' instead: the deliverable arrives as text in operator_notes via check_task_status (limited to 1 such task per client per day). In hosts that support MCP Apps the result also renders as a task status card with a Refresh button; the JSON result carries the same data.

输入参数deadlinedeliveryrequestertask_type必填description必填contact_emailoutput_formatlocation_detaillocation_required

check_task_status

Check task status

Look 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 status change), eta (operator-set delivery estimate, once accepted), and any operator notes. Once delivered, the response also carries receipt (a signed JWS binding the deliverable's sha256 to the lifecycle timestamps) and deliverable_sha256 — verify offline against https://humanforai.dev/.well-known/jwks.json. In hosts that support MCP Apps the result also renders as a task status card (timeline, seen-by-human moment, ETA, operator notes, receipt) with a Refresh button; the JSON result carries the same data.

输入参数task_id必填

message_human_operator

Message the human operator

Send 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 reply as a signed webhook push. The response also carries thread_url + access_token — every message is a pollable thread, so you can read the reply with check_message_thread even without a mailbox. Keep the token: it is shown only once.

输入参数frommessage必填subjectreply_to必填

check_message_thread

Read a message thread

Read 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 — the operator works at human speed, so poll occasionally rather than in a loop.

输入参数message_id必填access_token必填

reply_in_message_thread

Follow up in a message thread

Add 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 from the submission response.

输入参数message必填message_id必填access_token必填

版本历史

1
  1. v0.1.4最新Sep 16, 2026

评分

已满足适用检查项的 100%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分