Side-by-Side Model Context Protocol Comparison
Humanforai MCP vs SandBase CLI
In-depth architectural comparison of the Humanforai MCP and SandBase CLI MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Humanforai MCP
Agreements & Coordination · Local stdio
Quality: 64/100 (Good) | Auth: No auth required
SandBase CLI
Aggregators · Local stdio
Quality: 67/100 (Great) | Auth: other
Verdict Summary: Choose Humanforai MCP if you need specialized Agreements & Coordination tools running via a local process. Choose SandBase CLI if your workspace requires Aggregators integration with local subprocess execution. Both servers can be configured concurrently in your client's
mcpServers manifest.Which MCP Server Should You Choose?
Choose Humanforai MCP when:
- You need dedicated capabilities in the Agreements & Coordination domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
- Primary tools included: get_human_services, submit_human_task, check_task_status.
S
Choose SandBase CLI when:
- You need dedicated capabilities in the Aggregators domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: other (Free / Open Source).
- Primary tools included: sandbase_discover, sandbase_inspect, sandbase_run.
Feature & Specification Comparison
Tools & Capabilities Breakdown
Humanforai MCP Tools (4)
get_human_services
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.
submit_human_task
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).
check_task_status
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.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Humanforai MCP Configuration
SandBase CLI Configuration
Frequently Asked Questions
More alternatives to Humanforai MCPMore alternatives to SandBase CLIAgreements & Coordination category hub