mcp-registry/com.heylegwork/legwork · v1.0
As of 2026-10-19 08:52 UTC, the Heylegwork Legwork MCP server is up with a Glimind reliability score of 73/100 (grade C). Over the last 30 days it answered 99.2% of Glimind's liveness checks. It had 134 outages in 90 days, with a median recovery of 4 minutes.
Hire humans for tasks agents cannot do: errands, calls, photos, verification. Escrowed, verified.
Claude Code
claude mcp add --transport http heylegwork-legwork-mcp-server https://heylegwork.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"heylegwork-legwork-mcp-server": {
"type": "http",
"url": "https://heylegwork.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
12 of 12 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
14 parameter(s) across 8 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
4 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Handshake + tools/list takes ~1,731 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
In the last 30 days: 12 tool(s) removed and 0 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 8 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.heylegwork%2Flegwork/fixes
{
"name": "octopus_approve",
"description": "Accept submitted work: releases the escrowed budget to the human and completes the task. Verify each criterion response (and open attachment URLs) first.",
"inputSchema": {
"type": "object",
"required": [
"task_id"
],
"properties": {
"api_key": {
"type": "string",
"description": "Octopus API key (lw_live_… prefix). Optional if the MCP connection sends an Authorization: Bearer header. Get one with octopus_register."
},
"task_id": {
"type": "string"
},
"feedback": {
"type": "string",
"description": "Optional thanks, costs nothing, gets you claimed faster next time."
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "octopus_cancel_task",
"description": "Cancel a task for a full refund. Allowed while open, or while claimed-and-overdue.",
"inputSchema": {
"type": "object",
"required": [
"task_id"
],
"properties": {
"api_key": {
"type": "string",
"description": "Octopus API key (lw_live_… prefix). Optional if the MCP connection sends an Authorization: Bearer header. Get one with octopus_register."
},
"task_id": {
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": true,
"idempotentHint": true
}
}{
"name": "octopus_get_task",
"description": "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.",
"inputSchema": {
"type": "object",
"required": [
"task_id"
],
"properties": {
"api_key": {
"type": "string",
"description": "Octopus API key (lw_live_… prefix). Optional if the MCP connection sends an Authorization: Bearer header. Get one with octopus_register."
},
"task_id": {
"type": "string"
},
"since_status": {
"type": "string"
},
"wait_seconds": {
"type": "number"
},
"since_messages": {
"type": "number"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.heylegwork/legwork"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.heylegwork/legwork"}) over MCP.
octopus_post_task ~459 tokensoctopus_register ~322 tokensoctopus_declare_intents ~241 tokensoctopus_get_task ~201 tokensoctopus_approve ~164 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.heylegwork%2Flegwork?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.heylegwork%2Flegwork?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.heylegwork%2Flegwork.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.heylegwork%2Flegwork.svg :target: https://glimind.com/server/mcp-registry%2Fcom.heylegwork%2Flegwork?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:33e18a66cb2fea41…, first seen 2026-10-17, included at leaf 6707 of 25,799. Version history · verify what your client received.
Compare: most reliable finance servers · most reliable communication servers · most reliable retrieval servers · most reliable other servers · most reliable payments servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-19 08:52 UTC, the Heylegwork Legwork MCP server is up with a Glimind reliability score of 73/100 (grade C). Over the last 30 days it answered 99.2% of Glimind's liveness checks. It had 134 outages in 90 days, with a median recovery of 4 minutes.
Heylegwork Legwork MCP server advertises 23 tools, including approve_task, cancel_task, get_balance, get_messages, get_task.
Point your MCP client at this streamable-http endpoint: https://heylegwork.com/mcp
Glimind scanned all 12 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.