# humanforai/humanforai-mcp [Health: Active]

**Category:** 🤝 Agreements & Coordination  
**Repository:** https://github.com/humanforai/humanforai-mcp  
**GitHub Stars:** 1  
**npm Downloads (last month):** 406  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/humanforai-humanforai-mcp

## Description
Hire a real human operator for tasks that need physical presence, perception, or judgment: real-world verification, product testing, AI output review, data collection, and local errands. Remote streamable HTTP at https://humanforai.dev/mcp or local stdio via npx -y humanforai.

## Tools
Capabilities this server exposes over MCP:

- **get_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 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).
- **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.
- **message_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 you or your principal can read); it is the only way the operator can answer.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "humanforai-mcp": {
    "command": "npx",
    "args": ["-y","humanforai"]
  }
}
```

## Documentation

## What humanforai/humanforai-mcp MCP server does

The humanforai/humanforai-mcp MCP server lets an AI agent request work from a real human operator. Supported use cases include checking whether a place, product, price, or claim exists; testing an application or product; reviewing AI-generated output; collecting information that requires local access or human perception; and performing visits, photographs, measurements, or observations.

The operator reviews each submitted task before accepting it. Requests that are illegal, harmful, deceptive, unsafe, or privacy-invasive are rejected. Services are free during the proof-of-concept pilot described in the source material.

## How it works

Begin with `get_human_services` to retrieve the current service manifest. It includes the operator's profile, location, languages, working hours, response expectations, accepted and rejected task types, and trust-and-safety policy. The listed services are examples, so an agent can also describe a custom human-in-the-loop request.

Use `submit_human_task` for a specific, self-contained request. The tool immediately returns a `task_id`, but that identifier represents submission rather than completion. The operator receives a push notification and decides whether to accept the task. A real mailbox must be supplied through `contact_email` for delivery; it is checked for a valid mail domain. If email delivery is unavailable, `status_poll` can return the deliverable in `operator_notes`, subject to one such task per client per day.

Call `check_task_status` with the returned identifier to follow the lifecycle. Results include status transitions, timestamps, the time the operator first saw the request, an estimated delivery time after acceptance, and operator notes. Completed tasks also include a signed receipt and a SHA-256 digest for offline verification using the published JWKS endpoint.

## Setup and configuration

The humanforai/humanforai-mcp MCP server can be run locally through npm:

```bash
npx -y humanforai
```

For a stdio client, configure the command as `npx` with arguments `-y` and `humanforai`. The package acts as a thin proxy to the hosted Human For AI MCP endpoint, so tool definitions come from the live service rather than being implemented locally.

Clients with native remote MCP support can connect directly to `https://humanforai.dev/mcp` over streamable HTTP. The provided material states that this endpoint requires no authentication. Claude Desktop is shown as a supported stdio configuration target, and Claude is also given as an example of a client with native remote connector support.

## Tools and capabilities

The humanforai/humanforai-mcp MCP server exposes four tools:

- `get_human_services` retrieves the live catalog, operator profile, availability details, task boundaries, and safety policy.
- `submit_human_task` sends a request to the operator and returns a task identifier.
- `check_task_status` reports progress, timestamps, estimates, notes, and completed-task verification data.
- `message_human_operator` sends a free-form question or project discussion. It requires `reply_to`, an email address that the operator can use to respond.

## Limitations and notes

This service is asynchronous: submission does not mean immediate execution, and every request is subject to human acceptance. The stated first-response target is within 12 hours on any day, although responses may arrive sooner. The pilot terms, including free access, may not describe future pricing.

The local npm package was previously published under the name `human-api`; that package remains available but is deprecated in favor of `humanforai`. Completed-task receipts can be checked against `https://humanforai.dev/.well-known/jwks.json`.

_Full upstream README: https://allmcps.com/mcp/humanforai-humanforai-mcp/readme_