# Human For AI (remote · humanforai.dev)

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

- Trust score: 67/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `humanforai.dev`: 67/100 (this document), [markdown](https://verifymcp.io/servers/dev-humanforai-humanforai/humanforai.md), [page](https://verifymcp.io/servers/dev-humanforai-humanforai/humanforai)
- npm · `humanforai`: 35/100, [markdown](https://verifymcp.io/servers/dev-humanforai-humanforai/humanforai-2.md), [page](https://verifymcp.io/servers/dev-humanforai-humanforai/humanforai-2)

## Channel facts

- Endpoint: `https://humanforai.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.4`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1428 tokens (~357/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http dev-humanforai-humanforai https://humanforai.dev/mcp
```

### Codex

```toml
[mcp_servers.dev-humanforai-humanforai]
url = "https://humanforai.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-humanforai-humanforai": {
      "type": "remote",
      "url": "https://humanforai.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-humanforai-humanforai --url https://humanforai.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-humanforai-humanforai:
    url: "https://humanforai.dev/mcp"
```

### Other

```json
{
  "mcpServers": {
    "dev-humanforai-humanforai": {
      "type": "http",
      "url": "https://humanforai.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 65, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 64, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 62, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 62)

First indexed and scored.

## MCP tools (4)

### `get_human_services` (~79 tokens)

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` (~447 tokens)

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).

Input parameters:

- `contact_email` (string): Where the deliverable and clarifying questions are sent. Required unless delivery is 'status_poll'. Must be a real, reachable mailbox — placeholder domains are rejected and the domain is MX-checked.
- `deadline` (string): ISO 8601 datetime, e.g. 2026-07-10T12:00:00+03:00
- `delivery` (string): How the deliverable reaches you. 'email' (default) needs contact_email. 'status_poll' is the no-mailbox path for autonomous agents: the result arrives as text in operator_notes via check_task_status…
- `description` (string, required): What to do, where, and what success looks like. Specific, self-contained tasks are accepted faster.
- `location_detail` (string): City, address, or area — required in practice when location_required is true
- `location_required` (boolean): true if the task needs physical presence (coverage is confirmed at review)
- `output_format` (string): text_report (default), text_report_with_photos, structured_json, annotated_screenshots, or video
- `requester` (string): Your agent or system identifier, e.g. my-agent/1.0
- `task_type` (string, required): Service category — see get_human_services for descriptions. The list is not exhaustive: use custom_human_in_the_loop for anything that fits no other category

### `check_task_status` (~161 tokens)

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.

Input parameters:

- `task_id` (string, required): Task ID returned by submit_human_task, e.g. HFAI-2026-A1B2C3D4E5F60718

### `message_human_operator` (~127 tokens)

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

Input parameters:

- `from` (string): Your agent or system identifier
- `message` (string, required): The message. Plain language, English.
- `reply_to` (string, required): REQUIRED. Email address for the reply — must be a real, reachable mailbox (MX-checked).
- `subject` (string): Short subject line

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-humanforai-humanforai/humanforai#diagnostics

## Score history

- 2026-08-03: 67
- 2026-08-02: 66
- 2026-08-01: 66
- 2026-07-31: 65
- 2026-07-30: 64
- 2026-07-29: 64
- 2026-07-28: 63
- 2026-07-27: 62
- 2026-07-26: 62

## Links

- Remote endpoint: https://humanforai.dev/mcp
- Repository: https://github.com/humanforai/humanforai-mcp
- Website: https://humanforai.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-humanforai-humanforai/humanforai/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-humanforai-humanforai/humanforai/changelog.json
- HTML version of this page: https://verifymcp.io/servers/dev-humanforai-humanforai/humanforai