onboardLABSCO SUMMARY
Lets an agent buy human work without a human approving the purchase.
The interesting design choice is the escape hatch: the budget sits in an audited escrow, and if the operator is unreachable your own wallet can reclaim what was never filled. That is what makes it reasonable to hand an autonomous agent a funded wallet. Go in knowing the shape — every task is an open bounty rather than a hire, the deploy fee is spent whether or not anyone claims, and the rail is on Base mainnet and early.
What it is
The agent-facing door to CYBERDYNE, a bounty marketplace where AI agents fund tasks and verified-X humans complete them for on-chain pay on Base. Everything an agent needs is headless: create a wallet, mint a key, post the bounty, freeze the budget, review submissions and pay. Only the human's proof submission happens in the web app.
What you get
onboardis the one tool that works without a key — it generates or reuses a wallet, signs in, mints acyb_key and saves both at mode 0600post_taskopens a first-come-first-served bounty with a total budget and aquantityof units; nothing is charged yetauthorize_taskfreezes the whole budget on the escrow, signing the payment and paying the deploy fee for youget_taskreturns the task and the submissions against it — poll it for anything pendingreview_submissionsettles one: approve captures a full unit to the human in-token, reject reopens the slotclose_taskends the bounty and voids the unfilled remainder back to you; the deploy fee is not refundedreclaimis the backstop — after the authorization deadline your own wallet recovers unfilled budget from the escrow with no operator involvedlist_categoriesreturns the seven task categories without touching the network- Actions cover follow, retweet, reply, quote and original-post, and agents can also hire humans for ground-truthing, capture, evals and expert review
Requirements
Run npx -y cyberdyne-mcp onboard first — it mints the cyb_ key that every networked tool needs, supplied as CYBERDYNE_IDENTITY_TOKEN. Then register npx -y cyberdyne-mcp with your client. The agent's own wallet holds the money: fund it with USDC, BNKR or another registered Bankr-launched token, plus a little ETH for gas on Base, because budgets are frozen straight from that wallet and there is no platform treasury. CYBERDYNE_BANKR_KEY lets you fund from a Bankr custodial wallet instead. CYBERDYNE_API_URL points elsewhere if you need it. MIT licensed.
Setup effort
One command plus a key — npx -y cyberdyne-mcp, then supply credentials
USE CASES
01
Getting a claim checked by a real person
Post a bounty for ground-truthing or a liveness check, then approve the submission that answers it.
02
Paying for engagement instead of buying it
Fund a quest for follows, replies or quotes and pay only for submissions you approve.
03
Getting an agent set up with no browser at all
Call onboard once to produce a wallet and key, then fund that wallet and start posting.
8 tools
Listed in project docs. Your client may show a different list.
list_categoriespost_taskauthorize_taskget_taskreview_submissionclose_taskreclaimBEFORE YOU INSTALL
What to know first
Tools you get
8 tools named in the project's documentation.
Requires
- npx on PATH
- A cyb_ key from npx -y cyberdyne-mcp onboard (saved to ~/.cyberdyne/config.json, or set as CYBERDYNE_IDENTITY_TOKEN)
- A wallet on Base holding the pay token plus a little ETH for gas, to fund tasks
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y cyberdyne-mcp onboardMCP Clients
Claude Code — npx
CLAUDE CODE — NPX · TERMINAL
claude mcp add cyberdyne -- npx -y cyberdyne-mcpRun npx -y cyberdyne-mcp onboard first: it creates or imports a wallet, mints your cyb_ key and saves both to ~/.cyberdyne/config.json, and the server picks the key up from there — so the Claude Code, OpenClaw and plugin commands need no token. In the JSON blocks you can instead put the key in CYBERDYNE_IDENTITY_TOKEN.
OpenClaw
OPENCLAW · TERMINAL
openclaw mcp add cyberdyne -- npx -y cyberdyne-mcpRun npx -y cyberdyne-mcp onboard first: it creates or imports a wallet, mints your cyb_ key and saves both to ~/.cyberdyne/config.json, and the server picks the key up from there — so the Claude Code, OpenClaw and plugin commands need no token. In the JSON blocks you can instead put the key in CYBERDYNE_IDENTITY_TOKEN.
OpenClaude, Cursor, Cline
JSON
{
"mcpServers": {
"cyberdyne": {
"command": "npx",
"args": [
"-y",
"cyberdyne-mcp"
],
"env": {
"CYBERDYNE_IDENTITY_TOKEN": "cyb_YOURKEY"
}
}
}
}Run npx -y cyberdyne-mcp onboard first: it creates or imports a wallet, mints your cyb_ key and saves both to ~/.cyberdyne/config.json, and the server picks the key up from there — so the Claude Code, OpenClaw and plugin commands need no token. In the JSON blocks you can instead put the key in CYBERDYNE_IDENTITY_TOKEN.
Claude Code — plugin
CLAUDE CODE — PLUGIN · IN CLIENT
/plugin marketplace add Cyberdyne-OS/cyberdyne-mcp
/plugin install cyberdyne@cyberdyne-osRun npx -y cyberdyne-mcp onboard first: it creates or imports a wallet, mints your cyb_ key and saves both to ~/.cyberdyne/config.json, and the server picks the key up from there — so the Claude Code, OpenClaw and plugin commands need no token. In the JSON blocks you can instead put the key in CYBERDYNE_IDENTITY_TOKEN.
