callable
Server Details
API for AI agents to delegate tasks to real humans.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2024-11-05
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 3 tools
Each tool serves a distinct stage in the task lifecycle: submit creates a task, get_task_status polls it, and review acts on the pending_review outcome. There is no overlap or ambiguity between them.
All tool names follow a consistent verb_noun pattern (submit_task, get_task_status, review_task) with clear, specific verbs and the same domain object. This is a model of naming consistency.
Three tools is the ideal number for this server's narrow purpose—submitting, monitoring, and reviewing human tasks. Each tool is necessary and there are no redundant or missing tools.
The toolset fully covers the workflow: task creation, status polling, and final approval/dispute resolution. The documented auto-approval mechanism fills any edge case, leaving no obvious functional gaps.
Available Tools
3 toolsget_task_statusARead-onlyIdempotentInspect
Poll the status and retrieve the result of a previously submitted task. Returns the current status (pending, in_progress, pending_review, completed, disputed), the result payload, and any output URLs (video, screenshot). Use this in a polling loop after submit_task if no callback_url was provided.
Inputs: task_id (required). Returns: result, status, task_id, operator, +2 more
review_taskAIdempotentInspect
Optional. Approve or dispute a task that is in pending_review status. Use this after get_task_status reports the operator has completed the work. Approving releases the operator payout. Disputing requires a reason and a description of what is needed for acceptance; the operator is then allowed to resubmit. If you never call review_task, tasks are auto-approved after the review window expires.
Inputs: task_id (required), decision (required), dispute_reason, what_is_needed. Returns: status, success
submit_taskAInspect
Submit an account verification task to a real human operator. Use this when your agent is blocked on something only a real person can complete — a KYC check, a platform sign-in or 2FA prompt, a CAPTCHA, an identity confirmation, or any verification step that requires a human. The task is charged automatically via Stripe ($39). A vetted operator claims it, performs the verification on real hardware, and returns the result (with optional screenshot) to your callback_url or via get_task_status. Typical completion: 30 minutes.
Inputs: task_type (required), instructions (required), deadline_minutes (required), callback_url, +1 more. Returns: status, message, task_id, estimated_completion
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Human-as-a-Service for AI agents. Delegate tasks that need a real human, get results via API.
Human execution API for AI agents needing voluntary help with physical-world tasks.
Hand bounded tasks from AI agents to trusted humans.
Human-in-the-loop API for AI agents. CAPTCHA, OTP, KYC, and approvals by real humans.
Related MCP Servers
AlicenseAqualityCmaintenanceEnables AI agents to hire real human operators for tasks requiring physical presence, human perception, or judgment, such as verification, testing, data collection, and physical-world tasks.446 npm1MIT- AlicenseAqualityDmaintenanceEnables AI agents to search for and hire humans for real-world tasks.33102 npm9MIT

humanforaiofficial
AlicenseAqualityCmaintenanceEnables AI agents to hire verified human operators for tasks requiring physical presence, human perception, or judgment, such as real-world verification, product testing, and data collection.6MIT- AlicenseAqualityCmaintenanceRoutes tasks from AI agents to human workers via webhook providers with smart matching, fallback chains, and proof-of-completion tracking.859 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.