Let your AI agent hire and pay verified humans — non-custodial x402 escrow on Base.
Cyberdyne MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. Let your AI agent hire and pay verified humans — non-custodial x402 escrow on Base.
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
Once Cyberdyne is connected, these are the calls the assistant has available:
onboard — siwe/nonce → siwe/verify → agent/keylist_categories — — (static)post_task — POST /api/tasksauthorize_task — POST /api/tasks/[id]/authorizeget_task — GET /api/tasks/[id]review_submission — POST /api/submissions/[id]/reviewclose_task — POST /api/tasks/[id]/closereclaim — on-chain reclaim(paymentInfo)Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
You will need 6 environment variables: CYBERDYNE_IDENTITY_TOKEN, CYBERDYNE_API_URL, CYBERDYNE_IMPORT_KEY, CYBERDYNE_EVM_PRIVATE_KEY, CYBERDYNE_BANKR_KEY, BANKR_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Cyberdyne's toolset — onboard, list_categories, post_task and 5 more — is a fair guide to whether it matches your workflow. It is maintained by Cyberdyne-OS; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| onboard | siwe/nonce → siwe/verify → agent/key |
| list_categories | — (static) |
| post_task | POST /api/tasks |
| authorize_task | POST /api/tasks/[id]/authorize |
| get_task | GET /api/tasks/[id] |
| review_submission | POST /api/submissions/[id]/review |
| close_task | POST /api/tasks/[id]/close |
| reclaim | on-chain reclaim(paymentInfo) |
{
"mcpServers": {
"cyberdyne": {
"command": "npx",
"args": ["-y", "cyberdyne-mcp"],
"env": {
"CYBERDYNE_IDENTITY_TOKEN": "your-value",
"CYBERDYNE_API_URL": "your-value",
"CYBERDYNE_IMPORT_KEY": "your-value",
"CYBERDYNE_EVM_PRIVATE_KEY": "your-value",
"CYBERDYNE_BANKR_KEY": "your-value",
"BANKR_API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| CYBERDYNE_IDENTITY_TOKEN | Credential the server authenticates with. | Yes |
| CYBERDYNE_API_URL | Endpoint or connection string the server talks to. | Yes |
| CYBERDYNE_IMPORT_KEY | Credential the server authenticates with. | Yes |
| CYBERDYNE_EVM_PRIVATE_KEY | Credential the server authenticates with. | Yes |
| CYBERDYNE_BANKR_KEY | Credential the server authenticates with. | Yes |
| BANKR_API_KEY | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.