Skip to content

Human For AI

by humanforai.dev · remote · local (npm) · no sign-in to list tools · v0.1.4 · published by dev.humanforai

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

Final · 2Changes · 1
CompareRegistry entry

6 tools: 2 do something that can't be undone, 1 change things and 3 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

6 tools

Can't be undone 2Claude Code: ask
  • message_human_operatorSend a free-form message to the human operator — questions, scoping, custom or recurring projects, anything that is not yet a ready-made task.No findings

    Why it is in this group

    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • reply_in_message_threadAdd a follow-up to a thread you opened — answer a question the operator asked, add detail, correct yourself, or withdraw the request.No findings

    Why it is in this group

    • The name "reply_in_message_thread" says "reply": a word for sending, and what is sent cannot be taken back.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Changes things 1Claude Code: ask
  • submit_human_taskSubmit a task for the human operator to perform in the real world.No findings

    Why it is in this group

    • The name "submit_human_task" says "submit": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 3Claude Code: allow
  • check_message_threadRead the thread for a message you sent: the original text, every reply oldest-first, and whether the operator has answered.No findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
  • check_task_statusLook up a submitted task by its task_id.No findings

    Why it is in this group

    • The name "check_task_status" says "status": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
  • get_human_servicesFetch the Human For AI manifest: available services, operator profile (location, languages, working hours), response times, accepted and rejected task types, and trust & safety pol…No findings

    Why it is in this group

    • The name "get_human_services" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.1.4. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__humanforai__get_human_services",
      "mcp__humanforai__check_task_status",
      "mcp__humanforai__check_message_thread"
    ],
    "ask": [
      "mcp__humanforai__submit_human_task",
      "mcp__humanforai__message_human_operator",
      "mcp__humanforai__reply_in_message_thread"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as humanforai. Review it before you use it.