GoHireHumans
OfficialRelated Servers
Alternatives to GoHireHumans
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceDelegates real-world digital tasks to vetted humans directly from AI chat. Provides tools to get quotes, post tasks, and check status with escrow protection.25 npmMIT
- AlicenseAqualityFmaintenanceEnables AI agents to search for and hire humans for real-world tasks.3392 npm7MIT
- AlicenseAqualityCmaintenanceEnables AI assistants such as Claude, Cursor, and Windsurf to create and fund agent wallets, check balances, and move money idempotently between wallets. It also lets them find and hire people by skill, rate, and rating through posted jobs with escrowed budgets, deliverables, payment release, and disputes.1348 npmMIT

humanforaiofficial
AlicenseAqualityBmaintenanceEnables 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.458 npm1MIT
ReverseCentaurofficial
AlicenseAqualityBmaintenanceWe make it easy for AI agents to hire humans ethically and fairly.651 npmMIT- AlicenseAqualityDmaintenanceHuman Menu is a marketplace where AI clients post tasks for human workers.1011 npmMIT
TDQS
Scored across 13 tools
Most tools are distinct, and the descriptions actively cross-reference each other (e.g. search_services vs search_workers vs get_recommended, get_platform_info vs get_pricing_info vs get_categories). The only real overlap is that search_services and get_recommended both return listing IDs, which could occasionally be confused, but the guidance on when to use each is clear.
Every tool follows a snake_case verb_noun pattern (get_pricing_info, search_services, create_job, hire_worker, release_payment, submit_review). No mixing of conventions or vague verbs.
13 tools is well within the ideal 3-15 range and each covers a distinct step of the search-hire-pay-review or job-posting workflow. No redundant or filler tools.
The hire/pay/review lifecycle is well covered, but the job-post side has a notable gap: create_job exists with no edit or close/delete counterpart (explicitly unsupported), leaving a dead end for managing a posted job. Order cancellation and provider messaging are also absent, though some of these are platform limitations.