humanforai
OfficialRelated Servers
Alternatives to humanforai
No user-submitted related servers found.
Related Servers
AlicenseAqualityAmaintenanceEnables 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.452 npm1MIT- AlicenseAqualityFmaintenanceEnables AI agents to search for and hire humans for real-world tasks.3345 npm7MIT
- FlicenseNot gradedqualityDmaintenanceLets AI agents natively discover and hire human experts for tasks they can't do themselves, such as research, verification, and expert calls.-
- AlicenseAqualityCmaintenanceEnables AI agents to dispatch human verifiers for physical world tasks like product authentication, property inspection, and document verification, returning timestamped evidence reports.347 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to route tasks requiring human judgment (e.g., content moderation, refund decisions, data verification) to a vetted worker pool, with verified results returned via Lightning Network payments.MIT

handsforagents-mcpofficial
AlicenseNot gradedqualityBmaintenanceEnables agents to request physical-world tasks such as 3D printing, CNC fabrication, assembly, measurement, testing, on-site verification, and receive-repack-ship services from a human operator, with fixed-price quotes, status tracking, and evidence packages.MIT
TDQS
Scored across 6 tools
Each tool targets a distinct resource and action: service discovery, task submission, task status polling, initiating a message thread, reading a thread, and replying within a thread. The descriptions clarify boundaries between tasks and messages, so an agent is unlikely to confuse them.
All tool names follow a consistent verb_noun pattern: get_human_services, submit_human_task, check_task_status, message_human_operator, check_message_thread, reply_in_message_thread. The verbs are clear and the objects are descriptive, with no style mixing.
Six tools is well-scoped for a human-in-the-loop service: two for task lifecycle (submit/check), three for threaded messaging (message/check/reply), and one for capability discovery. Every tool serves a distinct purpose without bloat.
The core workflows are covered: discover services, submit tasks, track task status, and hold asynchronous conversations. Minor gaps exist such as no explicit task cancellation or listing all tasks, but these can be worked around via messaging and the returned task_id, so the surface is largely complete for the stated purpose.