Hire verified people to call a business, photo a storefront or check a shelf price. Free sandbox.
Maintained byworkman.rent(verified)Also a maintainer?
Call this server's tools from your browser. Nothing to install.
Bearer <client_id>:<api_key> from pairing_status or sandbox_signup_verify; omit for onboarding tools
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Catalogue of ready-made task templates (call_check, storefront_photo, shelf_price_check, store_open_check). Each has a result spec (checklist questions, minimum photos, done-when), a recommended and minimum budget in USDC, the executor skill, the location type and a default deadline. Create a task from one with create_task { template_id, purpose, place or lat/lng, + your own description where required }. No account needed. Read-only. Returns: { templates: [{ id, title, summary, recommended_budget_usdc, min_budget_usdc, required_skill, location_type, remote, default_deadline_hours, result_spec, required_fields }] }
This tool takes no arguments.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
Run in a terminal
claude mcp add --transport http workman https://workman.rent/mcp
Headers
Authorization (optional, not in the config above): Bearer <client_id>:<api_key> from pairing_status or sandbox_signup_verify; omit for onboarding toolsCatalogue of ready-made task templates (call_check, storefront_photo, shelf_price_check, store_open_check). Each has a result spec (checklist questions, minimum photos, done-when), a recommended and minimum budget in USDC, the executor skill, the location type and a default deadline. Create a task from one with create_task { template_id, purpose, place or lat/lng, + your own description where required }. No account needed. Read-only. Returns: { templates: [{ id, title, summary, recommended_budget_usdc, min_budget_usdc, required_skill, location_type, remote, default_deadline_hours, result_spec, required_fields }] }
No arguments.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
}Step 2 of onboarding. While pending returns { status }. When the requester has confirmed, returns { status: "ready", client_id, api_key } exactly ONCE — store them. Then reconnect to https://workman.rent/mcp with header Authorization: Bearer <client_id>:<api_key> to get the task tools (no header support, e.g. Claude.ai / ChatGPT connectors: use the returned connector_url as the connector URL).
| Argument | Type | Description |
|---|---|---|
| code* | string | Pairing code from start_pairing |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"code"
],
"properties": {
"code": {
"type": "string",
"maxLength": 64,
"minLength": 4,
"description": "Pairing code from start_pairing"
}
},
"additionalProperties": false
}Try workman.rent in 5 minutes without business verification (KYB): the SANDBOX runs the full task flow (create → fund → accept → submit → confirm, same statuses and webhooks as production) but tasks are taken by a bot and payments are simulated; no real people, no real money. Ask your human operator for their email, call this, then ask them for the 6-digit code from the email and call sandbox_signup_verify. Returns: { sent: true }
| Argument | Type | Description |
|---|---|---|
| email* | string | Your human operator's email (the code is sent there) |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"email"
],
"properties": {
"email": {
"type": "string",
"format": "email",
"description": "Your human operator's email (the code is sent there)"
}
},
"additionalProperties": false
}Confirms the 6-digit code and returns { client_id, api_key: "sk_sandbox_…" } ONCE — store them. Calling it again for the same email issues a new key and disables the old one. accept_rules must be true: your human operator accepts the Platform Rules (https://workman.rent/oferta.html) — ask them before you send it. Then reconnect to https://workman.rent/mcp with header Authorization: Bearer <client_id>:<api_key> (or stdio env WORKMAN_CLIENT_ID / WORKMAN_API_KEY). Client cannot set headers (Claude.ai / ChatGPT custom connector)? Use the returned connector_url as the connector URL. Returns: { sandbox: true, client_id, api_key, connector_url, limits, quickstart, go_live }
| Argument | Type | Description |
|---|---|---|
| code* | string | 6-digit code from the email |
| email* | string | Same email as in sandbox_signup_start |
| accept_rules* | boolean | true = your human operator accepted the Platform Rules |
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"email",
"code",
"accept_rules"
],
"properties": {
"code": {
"type": "string",
"pattern": "^\\d{6}$",
"description": "6-digit code from the email"
},
"email": {
"type": "string",
"format": "email",
"description": "Same email as in sandbox_signup_start"
},
"accept_rules": {
"type": "boolean",
"const": true,
"description": "true = your human operator accepted the Platform Rules"
}
},
"additionalProperties": false
}Step 1 of onboarding. Returns a short code (valid 15 min). Show it to your human operator: a VERIFIED requester confirms it in the dashboard at https://workman.rent/zamovnik.html. Then call pairing_status with the code. There is no anonymous self-registration. No verified requester yet? Try the SANDBOX first (sandbox_signup_start): full task flow with a bot, no verification. Returns: { code, expires_in, poll_after, instruction }
No arguments.
{
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Nov 21, 2026.