Developer · Remote MCP server
Human For AI
Hire a real human for real-world verification, product testing, AI output review, and errands.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.humanforai/humanforai- Version
- 0.1.4
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-07-13
- Updated
- 2026-07-13
- Publisher
- dev.humanforai
- Namespace
- Namespace verified by the MCP Registry via the domain humanforai.dev · how
- Website
- humanforai.dev
- Repository
- github.com/humanforai/humanforai-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://humanforai.dev/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- human-for-ai 1.9.0 · protocol 2025-06-18
- Tools discovered
- 6:
get_human_services,submit_human_task,check_task_status,message_human_operator,check_message_thread,reply_in_message_thread - Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | humanforai | 0.1.4 | stdio |
How to connect Human For AI
Human For AI is a remote MCP server: there is nothing to install. Its endpoint is https://humanforai.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: humanforai version 0.1.4. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y humanforai@0.1.4.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"humanforai": {
"command": "npx",
"args": [
"-y",
"humanforai@0.1.4"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| HubdThe project tracker for teams of humans and AI agents - in plain files. MCP server + CLI. | Local · stdio |
| hubmeshDeterministic multi-hop graph retrieval for RAG. Zero LLM calls in the query path. | Local · stdio |
| HubrisOpenAI-compatible LLM gateway for Russia: 500+ models, ruble pricing, balance, chat. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Huffines for Comptroller AI GatewayMCP gateway for donhuffines.com: articles, search and full text. Read-only, no auth. | Remote · HTTPLive check: ✓ handshake |
| Humane ProxyAI safety middleware - detects self-harm and criminal intent in LLM prompts. | Local · stdio |
| Humanread PublisherPublish Git-backed multilingual novels with agents, safe layouts, reviews, and author approval. | Remote · HTTPLive check: sign-in required |
| humantextpro MCP-SERVERAI text detection and humanization for Claude Code, Cursor, and Windsurf. | Local · stdio |
| Humsana MCPDetect developer stress, focus, fatigue from typing. Block dangerous commands when tired. | Local · stdio |