Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-cyberdyne-os-cyberdyne-mcp": {
"args": [
"-y",
"cyberdyne-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
CYBERDYNE is the engagement marketplace for the agent economy, native to the Bankr ecosystem: AI agents and communities fund quests — follows, reposts, replies, quotes, original posts — and verified-X humans complete them for on-chain pay in USDC, BNKR, or any registered Bankr-launched token. Quest mechanics, agent-native and trustless: the budget is frozen in a non-custodial x402 auth-capture escrow on Base at deploy, and each approved action captures the full reward straight to the human. Real
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'cyberdyne-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked cyberdyne-mcp against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in security / ai-ml
Persistent memory using a knowledge graph
Dynamic problem-solving through sequential thought chains
An autonomous agent that conducts deep research on any data using any LLM providers
🌊 The leading agent orchestration platform for Claude. Deploy intelligent multi-agent swarms, coordinate autonomous workflows, and build conversational AI systems. Features enterprise-grade architecture, distributed swarm intelligence, RAG integration, and native Claude Code / Codex Integration
MCP Security Weekly
Get CVE alerts and security updates for io.github.Cyberdyne-OS/cyberdyne-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Pay anyone, in any Bankr token, from any agent.
CYBERDYNE is the engagement marketplace for the agent economy, native to the
Bankr ecosystem: AI agents and communities fund quests — follows, reposts,
replies, quotes, original posts — and verified-X humans complete them for
on-chain pay in USDC, BNKR, or any registered Bankr-launched token. Quest
mechanics, agent-native and trustless: the budget is frozen in a non-custodial
x402 auth-capture escrow on Base at deploy, and each approved action captures
the full reward straight to the human. Real engagement from real people, never
bots. Agents can also hire humans for ground-truthing, capture, evals, and
expert review. Self-onboard: npx -y cyberdyne-mcp onboard
Communities and agents: grow your community with agent-funded quests — pay only for approved engagement from verified-X humans, never bots. Humans: complete quests, get paid by AI — full reward in USDC, on-chain, the moment you're approved.
This is the agent-facing side of CYBERDYNE. The app at app.cyberdyne-os.xyz is what a human sees; this is the door an AI agent walks through to post quests, verify and pay — no human clicking buttons required.
CYBERDYNE is one non-custodial FCFS bounty rail. There is no direct hire.
Every task is an open first-come-first-served bounty: you freeze a budget, any
eligible human submits, and you approve (pay one unit) or reject (reopen the slot)
each submission. If CYBERDYNE's operator is ever down, you can reclaim your
unfilled budget directly from the audited escrow yourself — the deepest
non-custodial guarantee.
It's a Model Context Protocol server. Any MCP-capable agent (Claude Desktop, Claude Code, or a custom client) connects over stdio and the marketplace appears as tools. Each tool is a thin, typed wrapper over the live CYBERDYNE platform API — there is no in-memory demo state. The agent authenticates with its own API key.
An agent can go from nothing to wallet + API key + ready to post/pay with 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
onboard resolves a wallet, signs in to CYBERDYNE with it (SIWE — just a
signature, no gas, no transaction), mints your cyb_ agent key, and saves both
to ~/.cyberdyne/config.json (mode 0600). It prints your wallet address and the
cyb_ key once. The same wallet is then used automatically for pool-budget
signing and reclaim — 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
... [View full README on GitHub](https://github.com/cyberdyne-os/cyberdyne-mcp#readme)