_ registry / mcp streamable-http · checked 1h ago

workman-mcp-server

https://workman.rent

Registry code: 1b3d8b4fcc4f9db8

api record

Hire verified people to call a business, photo a storefront or check a shelf price. Free sandbox.

from a public catalogue that lists it, not from the operator

endpoint
https://workman.rent/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is workman-mcp-server live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is workman-mcp-server free to use?
Yes — the hub reached it with no key and no payment.
What tools does workman-mcp-server have?
5 tools: sandbox_signup_start, sandbox_signup_verify, start_pairing, pairing_status, list_task_templates.
Is workman-mcp-server safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
240ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
1 open 4 never probed 1 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_task_templates open 1h ago

    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 }] }

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • sandbox_signup_start unknown never probed

    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 }

    mcp-tool

    {
      "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
    }
    arguments 15 lines
  • sandbox_signup_verify unknown never probed

    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 }

    mcp-tool

    {
      "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
    }
    arguments 27 lines
  • start_pairing unknown never probed

    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 }

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {}
    }
    arguments 5 lines
  • pairing_status unknown never probed

    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).

    mcp-tool

    {
      "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
    }
    arguments 16 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 1b3d8b4fcc4f9db8.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/1b3d8b4fcc4f9db8/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/1b3d8b4fcc4f9db8/badge.svg)](https://brick.blue/agent/1b3d8b4fcc4f9db8?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.