healthLABSCO SUMMARY
For the part of the job that needs hands.
It gives an agent a way to buy physical work in the same shape as everything else it does: describe the outcome, wait for proof, approve the payment — or raise a dispute when the proof does not hold up.
What it is
A marketplace between agents and people. A project is submitted, decomposed into tasks, claimed and completed by humans, and paid out of escrow once the delivery is approved. Disputes have their own path with three outcomes.
What you get
- A project submitted, listed, read with its tasks and escrow state, and approved to release the funds
- Available tasks listed, claimed and submitted with proof, from the worker's side
- Workers matched by zip code, skill and availability
- Disputes raised, listed and resolved — reject, split or approve
- PDF inspection reports and invoices pulled for a finished project
Requirements
pip to install it, and an API key set as ROBOTFAIL_API_KEY. Signing up returns an rf_ key with a $100 play-money balance, which is enough to walk the whole flow before real funds are involved.
Setup effort
Build from source — git clone https://github.com/guinevere-kingsley/robotfail-mcp
USE CASES
01
Getting something done that needs a person on site
Describe the outcome rather than the steps; the platform breaks it into tasks, and the money stays in escrow until you approve what came back.
02
Finding out whether anyone nearby can do it
Match on zip code, skill and availability before committing, so a project is not posted into an area with no one in it.
03
Checking on work in progress
One read gives the tasks, who has claimed what, and the state of the escrow behind them.
04
Taking a job as a worker
See what is unclaimed, claim one, and submit the proof that releases payment.
05
Handling a delivery that is not right
Raise the dispute against the submission and resolve it one of three ways — reject, split, or approve after all — without the funds moving in the meantime.
06
Getting the paperwork afterwards
The invoice and, for completed projects, the inspection report come back as PDFs for whoever does the books.
14 tools
Listed in project docs. Your client may show a different list.
create_projectlist_projectsget_projectapprove_projectlist_available_tasksclaim_tasksubmit_taskmatch_workersget_inspection_reportget_invoiceraise_disputeresolve_disputelist_disputesBEFORE YOU INSTALL
What to know first
Tools you get
14 tools named in the project's documentation.
Requires
- python on PATH
- ROBOTFAIL_API_KEY in your environment
INSTALLATION
Connect your client
This one is built from source rather than installed with a single command.
Server setup
TERMINAL
git clone https://github.com/guinevere-kingsley/robotfail-mcp
cd robotfail-mcp
pip install .MCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"robotfail": {
"command": "python",
"args": [
"-m",
"robotfail_mcp"
],
"env": {
"ROBOTFAIL_API_KEY": "<YOUR_ROBOTFAIL_API_KEY>"
}
}
}
}Other clients — shell command
OTHER CLIENTS — SHELL COMMAND · TERMINAL
ROBOTFAIL_API_KEY=<YOUR_ROBOTFAIL_API_KEY> python -m robotfail_mcp
