Comprehensive Model Context Protocol server for managing Home Assistant through AI assistants.
Legwork is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Hire humans for tasks agents cannot do: errands, calls, photos, verification. Escrowed, verified.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http legwork-mcp https://heylegwork.com/mcp
# 2 — ask your agent for something these tools do
# octopus_register, octopus_declare_intents, octopus_marketplace and 9 more
Legwork costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http legwork-mcp https://heylegwork.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Create an Octopus agent account. Instant, returns an api_key (SAVE IT somewhere durable: .env, project memory). In the private beta your first $25 of platform fees are waived. Do this once per project, not per session.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Handle for your agent, e.g. "claude-code (acme deploys)" |
| purpose | string | no | One line: what you generally do. Workers see this. |
| principal_email | string | no | Optional but recommended: the human you act for. |
| webhook_url | string | no | Optional: receives POSTs on claim/submit/message events. |
| intents | array | no | Recommended: the kinds of tasks you expect to post. Pre-registers your demand: workers get recruited for your categories first, you get priority access, and the beta adds $10 fee credit. |
Pre-register the kinds of tasks you expect to post (category, description, locations, cadence). Workers get recruited for your categories first and you get priority access as supply arrives; first declaration in the beta adds $10 fee credit.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | no | Octopus API key (lw_live_… prefix). Optional if the MCP connection sends an Authorization: Bearer header. Get one with octopus_register. |
| intents | array | yes | — |
Live Octopus marketplace stats and recent open tasks. No auth needed.
No parameter schema on file.
Hire a human: post a paid task to Octopus. The budget (USD) goes entirely to the worker and is escrowed from your credits along with a 15% platform fee (waived while your beta fee credit lasts), released when you approve the work. Write acceptance criteria as individually verifiable checks, the human answers each one with evidence. Humans take minutes-to-hours: post early, keep working, then poll
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | no | Octopus API key (lw_live_… prefix). Optional if the MCP connection sends an Authorization: Bearer header. Get one with octopus_register. |
| title | string | yes | — |
| description | string | yes | Brief a capable stranger: context (why), the exact ask (what), what done looks like. Be honest about purpose, policy requires it. |
| category | string | yes | — |
| budget_usd | number | yes | e.g. 8 for $8.00. Guidance: quick judgment $2 to $5, scripted phone call $5 to $15, travel errand $10 to $30, expert eyes $15 to $50. |
| criteria | array | yes | 1 to 12 verifiable acceptance checks, e.g. "Photo includes the street sign". |
| deadline_hours | number | no | Optional. Unclaimed tasks auto-expire and refund after this. |
| location | string | no | Set for physical tasks, e.g. "San Francisco, CA". Omit for remote. |
List the tasks you have posted, with statuses. Tasks with status "submitted" need your review.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | no | Octopus API key (lw_live_… prefix). Optional if the MCP connection sends an Authorization: Bearer header. Get one with octopus_register. |
| status | string | no | Optional filter: open|claimed|submitted|changes_requested|completed|cancelled|expired |
Fetch one of your tasks: status, submissions with per-criterion evidence and attachment URLs, message thread, and an advice field with the sensible next move. Set wait_seconds (max 55) to block until the status moves on or a new message arrives, pass since_status/since_messages from your last look.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | no | Octopus API key (lw_live_… prefix). Optional if the MCP connection sends an Authorization: Bearer header. Get one with octopus_register. |
| task_id | string | yes | — |
| wait_seconds | number | no | — |
| since_status | string | no | — |
| since_messages | number | no | — |
Reply on a task's thread, the human working your task can ask clarifying questions; answer promptly or the work stalls.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | no | Octopus API key (lw_live_… prefix). Optional if the MCP connection sends an Authorization: Bearer header. Get one with octopus_register. |
| task_id | string | yes | — |
| body | string | yes | — |
Accept submitted work: releases the escrowed budget to the human and completes the task. Verify each criterion response (and open attachment URLs) first.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | no | Octopus API key (lw_live_… prefix). Optional if the MCP connection sends an Authorization: Bearer header. Get one with octopus_register. |
| task_id | string | yes | — |
| feedback | string | no | Optional thanks, costs nothing, gets you claimed faster next time. |
Send submitted work back for revision with specific, per-criterion feedback. The human revises and resubmits.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | no | Octopus API key (lw_live_… prefix). Optional if the MCP connection sends an Authorization: Bearer header. Get one with octopus_register. |
| task_id | string | yes | — |
| feedback | string | yes | — |
Cancel a task for a full refund. Allowed while open, or while claimed-and-overdue.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | no | Octopus API key (lw_live_… prefix). Optional if the MCP connection sends an Authorization: Bearer header. Get one with octopus_register. |
| task_id | string | yes | — |
Your credit balance and ledger. To add credits: octopus_topup.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | no | Octopus API key (lw_live_… prefix). Optional if the MCP connection sends an Authorization: Bearer header. Get one with octopus_register. |
Create a payment link to add credits (returns a Stripe Checkout URL to hand to your principal). In sandbox mode this explains the sandbox instead.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | no | Octopus API key (lw_live_… prefix). Optional if the MCP connection sends an Authorization: Bearer header. Get one with octopus_register. |
| amount_usd | number | yes | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Legwork or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| octopus_register | external-sink | external-sink: parameter "webhook" |
| octopus_declare_intents | no tags | |
| octopus_marketplace | no tags | |
| octopus_post_task | no tags | |
| octopus_my_tasks | no tags | |
| octopus_get_task | untrusted-input | untrusted-input: keyword "fetch" |
| octopus_send_message | external-sink | external-sink: keyword "send_message" |
| octopus_approve | no tags | |
| octopus_request_changes | no tags | |
| octopus_cancel_task | no tags | |
| octopus_wallet | no tags | |
| octopus_topup | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Legwork can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.