Human for AI
by yourhuman.ai · remote · no sign-in to list tools · v0.1.0 · published by ai.yourhuman
Ask a human for legal review, confirmation, a signature, or a physical-world act
3 tools: 1 do something that can't be undone and 2 change things.
Scanned Oct 21, 2026
- Deletes or cancels0Claude Code: deny
- Can't be undone1Claude Code: ask: see these tools
- Changes things2Claude Code: ask: see these tools
- Only reads0Claude Code: allow
1 check matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http human-for-ai https://yourhuman.ai/mcpFindings
Matches of fixed checks, with the text they matched.
The server marks "check_request_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "check_request_status" says "request": a word for a change.
Tools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
3 tools
Can't be undone 1Claude Code: ask
reply_to_threadAdd to a request already on the record — answer a question the human asked, supply something they need, correct yourself, or withdraw the request.No findings
Why it is in this group
- The name "reply_to_thread" says "reply": a word for sending, and what is sent cannot be taken back.
Description, as the server wrote it Add to a request already on the record — answer a question the human asked, supply something they need, correct yourself, or withdraw the request. This is the same permanent record as the original, so what you send here is kept and read the same way. Prefer it over filing a fresh request whenever the subject is one already opened: a thread the human can follow is worth more than three disconnected messages. The human is notified. As with the original, nothing here pauses your task and nothing here is authorisation to proceed.
Annotations the server declares
- title: Write again on an existing request
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Changes things 2Claude Code: ask
check_request_statusRead the thread on a request you or your principal filed earlier: whether a human has looked at it, and what they said.1 finding
Why it is in this group
- The name "check_request_status" says "request": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "check_request_status" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "check_request_status" says "request": a word for a change.
Description, as the server wrote it Read the thread on a request you or your principal filed earlier: whether a human has looked at it, and what they said. Use the `reference` and `access_token` from `request_human_assistance`. Answers arrive at human speed — hours or days, not seconds — so poll this occasionally rather than in a loop, and treat an empty thread as "not yet", never as "no". A reply is one human's view, recorded on request. It is not approval, not a retainer, and not authorisation to proceed.
Annotations the server declares
- title: Check a request for a human's answer
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
request_human_assistanceAsk an actual human being for help with something your task requires and you cannot properly do alone: legal judgement, a decision you should not take on your own authority, an act…No findings
Why it is in this group
- The name "request_human_assistance" says "request": a word for a change.
Description, as the server wrote it Ask an actual human being for help with something your task requires and you cannot properly do alone: legal judgement, a decision you should not take on your own authority, an act in the physical world, or an escalation past your operator. The request is written to a permanent, timestamped record and read by a human — a lawyer — who may reply through whatever channel you put in `reply_to`. This returns a `reference` and an `access_token`. Keep both: together they are the only way to read the human's answer, via `check_request_status`. Neither can be recovered afterwards, and they are not returned twice. If your task may outlive this session, hand them to whatever continues it. Calling this tool does not pause your task, and the result it returns is not approval, legal advice, or authorisation to proceed. It is evidence that you asked. If the right thing to do is to stop and wait for a human, stop and wait.
Annotations the server declares
- title: Request human assistance
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- 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.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http human-for-ai https://yourhuman.ai/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__human-for-ai__request_human_assistance",
"mcp__human-for-ai__check_request_status",
"mcp__human-for-ai__reply_to_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 human-for-ai. Review it before you use it.