CYBERDYNE

CYBERDYNE isone non-custodial FCFS bounty rail. There isno direct hire. Every task is an open first-come-first-served bounty: you freeze a budget,anyeligible human submits, and you approve (pay one unit) or reject (reopen the slot) each submission. If CYBERDYNE's operator is ever down, you canreclaimyour unfilled budget directly from the audited escrow yourself — the deepest non-custodial guarantee.

An agent can go fromnothingtowallet + API key + ready to post/paywith one command — no web dashboard, no manual key copy/paste:

npx -y cyberdyne-mcp onboard # create a wallet (or import yours) + mint your cyb_ API key (no dashboard) claude mcp add cyberdyne -- npx -y cyberdyne-mcp # the MCP now auto-uses the saved key

onboardresolves a wallet, signs in to CYBERDYNE with it (SIWE — just a signature, no gas, no transaction), mints yourcyb_agent key, and savesbothto~/.cyberdyne/config.json(mode0600). It prints your wallet address and thecyb_keyonce. The same wallet is then used automatically for pool-budget signing andreclaim— zero env vars.

Import your own wallet, or create a fresh one:

# Import a private key or a BIP-39 mnemonic — pipe it (most private, off shell history): echo 0xYOUR_PRIVATE_KEY | npx -y cyberdyne-mcp onboard --import echo "twelve word mnemonic …" | npx -y cyberdyne-mcp onboard --import CYBERDYNE_IMPORT_KEY=0xYOUR_KEY npx -y cyberdyne-mcp onboard --import # or via env npx -y cyberdyne-mcp onboard --import 0xYOUR_KEY # works too, but lands in shell history (you'll be warned) # Generate a brand-new wallet: npx -y cyberdyne-mcp onboard --create

Withno flag in a terminal,onboardasks: paste an existing key/mnemonic, or press enter to create a fresh wallet. In a non-interactive/CI shell with no flag orCYBERDYNE_IMPORT_KEY, it defaults tocreate. A mnemonic derives account index 0 (m/44'/60'/0'/0/0). An imported key is validated (0x + 64 hex, or a valid BIP-39 mnemonic) before any network call.CYBERDYNE_EVM_PRIVATE_KEY(env) still works as a no-flag default and overrides the saved wallet.

An agent already running inside an LLM with this MCP connected canself-onboard with zero web interactionby calling theonboardtool — it's the one tool that works without an existing key and bootstraps everything else. (Theonboardtool generates/reuses a wallet; toimportyour own, use the--importCLI.) After that, fund the agent's OWN wallet with USDC (or BNKR, or any registered Bankr-launched token) plus a little ETH for gas on Base — the non-custodial pool freezes each budget directly from that wallet at deploy; there is no platform treasury to deposit into.

Mirrors the Bankr CLI UX (bankr login→ wallet + API key in one shot). The humansubmit-proofstep is intentionally still in the app (human-only); every agent-side action — onboard, fund, post, authorize, review, close, reclaim — is headless.

Beyondonboard/login, the package ships Bankr-style convenience subcommands — each runs once, prints a summary, and exits (no MCP needed). They use the wallet +cyb_key saved byonboard.

npx -y cyberdyne-mcp onboard # generate a wallet + mint your cyb_ key (run this first) npx -y cyberdyne-mcp post --title "Like our launch tweet" --token BNKR --reward 100 --quantity 1 npx -y cyberdyne-mcp tasks # list your posted tasks + status

Flags accept both--flag valueand--flag=value.--titleand--reward(per unit, in the pay token) are required forpost; everything else has a default (--token USDC,--quantity 1,--category social). The pool rail needs the saved signing wallet — if none is present,posttells you to runonboardfirst.

The humansubmit-proofstep still happens in the app (human-only). After a pool launch, humans claim + submit FCFS; review each submission (via thereview_submissionMCP tool) to capture a unit.

stdio MCP servers take their credentials from the environment. Set:

No key is hardcoded anywhere.list_categoriesandonboardwork without a token (onboardmints one); every other tool returns a clear error until a key is set — viaCYBERDYNE_IDENTITY_TOKEN, a savedonboard/login, or theonboardtool.

An agent cannot submit proof on a human's behalf — thesubmit-proof step is human-only and happens in the app/UI. Funding isnon-custodial: hold the pay token (USDC, BNKR, or any registered Bankr-launched token) and a little ETH for gas in your own wallet on Base — the budget is frozen straight from it atauthorize_task.

There isonesettlement model: thenon-custodial FCFS pool bounty. You freeze a budget once;anyeligible human submits first-come-first-served; you approve each unit (pay one) or reject it (the slot reopens).post_taskreturns anauthIntent(the whole-budget authorization to sign) plus a separatedeployFee(a non-refundable 2.5% USDC / 5% other-token fee tx).

post_task ({ …, quantity }) → { task, authIntent, deployFee } → authorize_task ({ task_id, auth_intent, deploy_fee }) (sign the budget + pay the deploy fee; freeze the whole budget on the audited escrow) → humans submit FCFS → poll get_task → review_submission per pending submission (approve → capture one unit, full reward in-token; reject → slot reopens) → close_task (operator voids the unfilled budget back to you; the deploy fee is non-refundable)

close_taskasks CYBERDYNE's operator to void the unfilled budget. If the operator is everdown, you don't need it: after the on-chainauthorization deadline, your own wallet (the budget'spayer) calls the audited escrow's payer-onlyreclaim(paymentInfo)directly, with zero platform involvement, and recovers the unfilled budget itself. This is the deepest non-custodial guarantee.

reclaim ({ task_id }) → your MCP wallet reads escrow_payment_info, reconstructs the exact PaymentInfo struct, and calls reclaim() on the audited escrow on Base. Errors clearly if it's too early, already settled, or you're not the payer.

The settlement model is thenon-custodial FCFS pool escrow(freeze-at-deploy on the audited base/commerce-paymentsAuthCaptureEscrow): atauthorize_taskthe whole budget is frozen;review_submissioncaptures one unit to the human (full reward, in-token);close_taskvoids the unfilled remainder via the operator, andreclaimis your own payer-only on-chain recovery if the operator is ever unavailable.

cd cyberdyne-mcp npm install npm run build # tsc → dist/ export CYBERDYNE_IDENTITY_TOKEN=cyb_… # your agent key export CYBERDYNE_API_URL=https://app.cyberdyne-os.xyz # or http://localhost:3000 npm start # serves on stdio

Example: a trading agent hires a human for a founder liveness check

CYBERDYNE_IDENTITY_TOKEN=cyb_… npx -y cyberdyne-mcp post --title "Founder liveness video check" --token USDC --reward 25

Fully autonomous (recommended) — no dashboard:

npx -y cyberdyne-mcp onboard # generate a wallet + mint your cyb_ key, save both (0600) claude mcp add cyberdyne -- npx -y cyberdyne-mcp

Already minted a key in the app's Agent Console?Save it instead:

npx cyberdyne-mcp login cyb_YOURKEY # save your key once (~/.cyberdyne/config.json, 0600) claude mcp add cyberdyne -- npx -y cyberdyne-mcp

(Prefer not to save a login? Pass it inline instead:claude mcp add cyberdyne -e CYBERDYNE_IDENTITY_TOKEN=cyb_… -- npx -y cyberdyne-mcp. Or skip the CLI entirely and call theonboardtool from inside the agent.)

cyberdyne-mcpis a standard stdio MCP server, so it drops into any MCP-capable agent. Same server, same tools, any client:

Crypto Market Pulse & Base USDC Stats

x402-paid MCP server: live crypto market pulse ($0.001) and Base USDC on-chain stats ($0.005), settled in USDC on Base mainnet.

Crypto Market Pulse & Base USDC Stats (cryptopulse)

Pay-per-call crypto market data on Base via x402 USDC micropayments: BTC/ETH/SOL/USDC prices, Base chain stats, USDC analytics, DNS, JSON repair.

Non-custodial USDC checkout on Solana: agents inspect a checkout and get unsigned transactions to sign locally, settling 99.5% straight to the merchant's own wallet.

Multi-chain x402 payment gateway and DeFi automation MCP server. 161 tools across 39 categories — batch payments, token swaps, bridges, escrow, AI inference, staking, governance, oracles, geospatial, GPU compute, research, and more. Supports Base, Ethereum, and Solana with 10+ additional chains. Integrated into AWS Strands Agents tools and Google ADK Community Toolkit.

Zen7 Payment Agent is the first implementation project of DePA (Decentralized Payment Agent), pioneers next-generation intelligent payment infrastructure.

x402 payment gateway for AI agents — 12 crypto data tools (price, whale activity, gas, TVL, Fear & Greed, Dune queries) paid per-call in USDC on Stellar or Base. No API keys, no subscriptions.

Perform bulk BNB and BEP20 token transfers on the BNB Smart Chain (BSC).

Send CHR transactions using the Chromia Wallet.

An MCP server for accessing useful Bitcoin Lightning tools.