Advertise
MCP.so
Sign In

CYBERDYNE — the engagement marketplace for the agent economy, na…

@Cyberdyne-OS

Repository

Basic information

Category

AI & Agents

Transports

stdio

Author

Cyberdyne-OS

Submitted by

Cyberdyne

About CYBERDYNE — the engagement marketplace for the agent economy, native to the Bankr ecosystem MCP Server

Engagement marketplace on Base, native to the Bankr ecosystem: AI agents and communities fund quests (follows, reposts, replies, quotes, original posts); verified-X humans complete them and are paid per approved action from a non-custodial x402 escrow — in USDC, BNKR, or any Bank

#payments#marketplace#x402#base#usdc#escrow#human-in-the-loop#agents#finance

CYBERDYNE — the engagement marketplace for the agent economy, native to the Bankr ecosystem MCP Server config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "cyberdyne": {
      "command": "npx",
      "args": [
        "-y",
        "cyberdyne-mcp"
      ],
      "env": {
        "CYBERDYNE_LOGIN_TOKEN": "cyb_your_agent_key",
        "CYBERDYNE_EVM_PRIVATE_KEY": "0x_optional_signer_key"
      }
    }
  }
}

CYBERDYNE — the engagement marketplace for the agent economy, native to the Bankr ecosystem MCP Server tools

8

List the kinds of quests CYBERDYNE humans can complete — engagement quests (follow, repost, reply, quote, original posts) plus ground-truthing, capture, agent evals, demos, and expert review. Static (no network). Use this to learn the valid `category` values before posting a quest.

BOOTSTRAP (works WITHOUT an existing key — the one tool that self-onboards). Zero-browser: generates a fresh wallet if you don't have one, signs in to CYBERDYNE with it (SIWE), mints your `cyb_` agent API key, and saves both to ~/.cyberdyne/config.json (0600) so every other tool here authenticates automatically. No web dashboard, no env vars. Returns your wallet address, the cyb_ key (shown once), and the next steps (fund your WALLET with USDC + a little ETH for gas on Base → post_task → authorize_task → review_submission → close_task). The non-custodial pool freezes the budget directly from your wallet at deploy — there is no platform treasury to deposit into. The same generated wallet auto-signs pool budgets. To bring your OWN wallet instead, use the CLI: `npx cyberdyne-mcp onboard --import <0xKEY | mnemonic>` (or --create for a fresh one). Idempotent-ish: re-running with a saved wallet reuses it and mints a fresh key.

Fund a quest on the engagement marketplace (an FCFS pool bounty). There is NO direct hire and NO agent-picks-human — every quest is an open bounty: you freeze a budget, ANY eligible verified-X human submits first-come-first-served, and you approve/reject each submission. Funds are NOT charged at post — the budget is frozen later at authorize_task. `reward_usd` is the total budget; `quantity` is how many identical units (humans) it pays — each unit holds reward_usd/quantity (each unit must be >= $0.01). Returns the created task (with its id) plus `authIntent` (the budget authorization to sign) and `deployFee` { usd, bps, recipient, token } (a SEPARATE non-refundable fee tx) — pass BOTH to authorize_task. The non-custodial POOL escrow (USDC/BNKR/GITLAWB on Base) is the only settlement rail; a non-real token (CYOS) or non-live config has no rail and returns 422 settlement_unavailable.

Freeze the bounty budget on-chain (the second step of the FCFS flow). REAL-TOKEN POOL rail: pass BOTH `auth_intent` (the authIntent from post_task) AND `deploy_fee` (the deployFee object from post_task) — with CYBERDYNE_EVM_PRIVATE_KEY set, the MCP signs the whole-budget authorization AND pays the separate 2.5% USDC / 5% other-token deploy fee tx from its wallet, then freezes the budget on the audited escrow; or pass a pre-signed `signed_payment` and a pre-paid `fee_tx_hash`. After this, any eligible human submits FCFS and you review_submission each. The non-custodial POOL escrow is the only rail; a non-real token / non-live config returns 409 settlement_unavailable. Idempotent once frozen.

Get the live state of a task: the task row plus the submissions and per-unit claims the agent (as poster) may see. Poll this after authorize_task until a submission with status 'pending' appears — that is the human's proof, ready for review_submission (approve pays one unit; reject reopens the slot).

THE settle tool (poster-only): approve or reject ONE submission on your FCFS pool bounty — this is how you pay humans (there is no direct hire). approve:true → CAPTURE one unit from the frozen budget to the human (full reward, in-token) and consume a slot; approve:false → reject (the slot reopens for the next submitter — no spot-blocking). Poll get_task for pending submissions and review each one. When the budget is consumed (or you're done) call close_task to refund the unfilled remainder.

Close your FCFS pool bounty (poster-only): refund the unfilled budget back to your wallet on-chain (the uncaptured remainder = unfilled units × per-unit reward) and stop further submissions. The deploy fee is non-refundable. Idempotent on an already-closed task. (close_task goes through CYBERDYNE's operator; if the operator is ever down, use `reclaim` to recover the budget yourself after the authorization deadline.)

Trustless self-recovery — if CYBERDYNE's operator is ever down, after the authorization deadline you can reclaim your unfilled budget directly from the audited escrow yourself, no platform involvement. This is the DEEPEST non-custodial guarantee: your MCP wallet (the payer) calls the audited AuthCaptureEscrow's payer-only `reclaim(paymentInfo)` ON-CHAIN itself — CYBERDYNE never touches it. Normally you close_task (operator voids the unfilled remainder back to you); reclaim is the backstop that needs no operator. Requirements: this MCP wallet MUST be the budget's payer (the wallet that froze it), and the on-chain authorizationExpiry must have passed (errors clearly if it's too early, already settled, or you're not the payer). Reads escrow_payment_info from GET /api/tasks/[id], reconstructs the exact PaymentInfo struct, signs+sends on Base, and waits for the receipt. Returns { ok, tx_hash, reclaimed }.

Overview

What is CYBERDYNE — the engagement marketplace for the agent economy, native to the Bankr ecosystem?

CYBERDYNE is a marketplace where AI agents and communities fund engagement tasks—such as follows, reposts, replies, quotes, and original posts—and verified-X humans complete them for on-chain payment in USDC, BNKR, or any registered Bankr-launched token. It is native to the Bankr ecosystem and uses a non-custodial, audited escrow contract on Base mainnet.

How to use CYBERDYNE — the engagement marketplace for the agent economy, native to the Bankr ecosystem?

Install via npx -y cyberdyne-mcp onboard. Then use the following functions: post_task to fund a quest, authorize_task to deploy the escrow pool, review_submission to approve or reject completions, and close_task / reclaim to refund unfilled units. The live app is available at https://app.cyberdyne-os.xyz.

Key features of CYBERDYNE — the engagement marketplace for the agent economy, native to the Bankr ecosystem

  • Non-custodial x402 auth-capture pool escrow on Base mainnet.
  • Audited Commerce-Payments contract; budget frozen on deploy.
  • Tasks completed first-come-first-served by verified-X humans.
  • Supports ground-truthing, capture, agent evals, and expert review.
  • Real engagement from real people, never bots.
  • Trustless payer-only recovery for unfilled units.

Use cases of CYBERDYNE — the engagement marketplace for the agent economy, native to the Bankr ecosystem

  • Fund social media engagement tasks (follows, reposts, replies, etc.) for AI agents.
  • Obtain ground-truth data through human verification tasks.
  • Run agent evaluations by having humans review and score outputs.
  • Commission expert reviews or content capture from verified users.

Frequently asked questions

1

What types of tasks can be funded?

The marketplace supports follows, reposts, replies, quotes, and original posts. It also enables ground-truthing, capture, agent evals, and expert review.

2

How are payments handled?

Rewards are paid on-chain in USDC, BNKR, or any registered Bankr-launched token. A non-custodial escrow pool is deployed on Base mainnet; the budget is frozen from the agent's wallet at deploy, and funds are released to humans upon approval.

3

What blockchain is used?

All escrow and payment operations happen on Base mainnet.

4

Does this use bots for engagement?

No—only verified-X humans complete tasks. The system is designed to deliver real engagement, never bots.

Comments

More AI & Agents MCP servers

Hypnothera

La-Salida

Agent skill: turn what your AI assistant knows about you into a personalized hypnosis session on hypnothera.ai

OpenZiti / LLM-Gateway

openziti

NetFoundry LLM Gateway is an OpenAI-compatible API proxy that routes requests across multiple LLM providers using zero-trust networking. Zero trust LLM gateway. OpenAI-compatible proxy with semantic routing and load bala

93

treg.to

Jason Zhou

OpenRouter for tools & data — 3,028 APIs for your agent, one token, pay per call. treg.to is a remote MCP server at https://treg.to/mcp/ that gives an agent 3,028 ready-to-call API endpoints across 82 platforms: SEO and

HeyLead: LinkedIn Outreach & Lead Generation MCP Server

D4umak

HeyLead: AI agent for LinkedIn outreach. Finds the right people, writes in your voice, follows up and handles replies, from Claude Code, Cursor, any MCP client or a web dashboard.

9

q-ring

I4cTime

Quantum-inspired keyring for AI coding agents. Secure secrets with superposition, entanglement, tunneling, and teleportation — CLI + 44 MCP tools.

3
Advertise