Human For AI
Hire a real human for real-world verification, product testing, AI output review, and errands.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http human-for-ai 'https://humanforai.dev/mcp'
{
"mcpServers": {
"human-for-ai": {
"type": "http",
"url": "https://humanforai.dev/mcp"
}
}
}
humanforaiclaude mcp add human-for-ai -- npx -y humanforai@0.1.4
{
"mcpServers": {
"human-for-ai": {
"command": "npx",
"args": [
"-y",
"humanforai@0.1.4"
]
}
}
}
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
humanforai
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_servicesfor 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
| Tool | Purpose |
|---|---|
get_human_services | Service catalog, accepted task types, limits |
submit_human_task | Submit a task; returns a task_id for status polling |
check_task_status | Poll a submitted task by task_id |
message_human_operator | Ask 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 acceptedstatus_history— every transition (submitted → accepted → delivered, orrejected) with timestamps
Setup
Claude Code
claude mcp add human-for-ai -- npx -y humanforai
Claude Desktop / other MCP clients (stdio)
{
"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:
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
get_human_services— see what the operator can dosubmit_human_task— be specific and self-contained; includecontact_emailto receive the deliverablecheck_task_status— poll with the returnedtask_id
Links
- Website: https://humanforai.dev
- API docs: https://humanforai.dev/api
- Machine-readable manifest: https://humanforai.dev/.well-known/agent.json
- OpenAPI spec: https://humanforai.dev/openapi.json
- Trust & safety: https://humanforai.dev/trust
License
MIT
Frequently asked questions
What is Human For AI?
Hire a real human for real-world verification, product testing, AI output review, and errands.
How do I install Human For AI?
It runs as a remote server. In Claude Code: claude mcp add --transport http human-for-ai 'https://humanforai.dev/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does Human For AI need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is Human For AI open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains Human For AI?
It is published by humanforai. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.