rustok-wallet MCP server
Commit Oct 11, 2026Connects AI agents to a self-custody Ethereum wallet for reading balances, previewing transactions, and executing transfers via a human-in-the-loop console.
Also known as rustok-org/mcp, mcp
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.4.2
- Last commit
- Oct 11, 2026
- License
- MIT-0
What is rustok-wallet MCP?
rustok-wallet connects AI agents to a self-custody Ethereum wallet for reading balances, previewing transactions, and executing transfers via a human-in-the-loop console.
Summary generated from the project's README
About rustok-wallet MCP server
Connecting AI agents to a self-custody Ethereum wallet is what this server enables for developers using Claude Desktop, Cursor, or cloud-based agents. It acts as a bridge between large language models and the Rustok Gateway, allowing agents to interact with blockchain assets while keeping private keys secured in a local container volume. The server supports Ethereum, Base, and Arbitrum by default, though users can configure custom RPC URLs.
Users can choose between two distinct trust models. The agent edition allows for unrestricted signing by the AI, while this TUI edition requires a human-in-the-loop approach. In the TUI version, any transaction that moves funds must be manually approved via a separate terminal using the rustok-console command and a 6-digit PIN. This setup ensures that the agent cannot drive fund transfers without your direct intervention.
Capabilities are managed through specific tools like read_wallet, preview_tx, and execute_tx. While the local stdio transport is process-trusted, the network-facing SSE transport requires a bearer token for authentication. The system provides informed previews by returning decoded calls, gas estimates, and risk levels through the preview_transaction tool.
What you can do with it
- 1Monitor crypto asset balancesAsk an AI agent to check the current holdings of your Ethereum or Base wallet.
- 2Simulate blockchain transactionsHave an agent decode a transaction call and check for potential reverts before you commit to it.
- 3Execute transfers with human approvalInstruct an agent to send funds while requiring a manual PIN entry in a separate terminal to finalize the move.
Written from the project's README. Every use case is checked against a quote from it.
How to install rustok-wallet MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall rustok-wallet MCP in Claude Code
$ claude mcp add mcp -- docker run -i --rm ghcr.io/rustok-org/rustok-wallet:v0.4.2Install rustok-wallet MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/rustok-org/rustok-wallet:v0.4.2"
]
}
}
}Install rustok-wallet MCP in VS Code
.vscode/mcp.json
{
"servers": {
"mcp": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/rustok-org/rustok-wallet:v0.4.2"
]
}
}
}Install rustok-wallet MCP in VS Code CLI
$ code --add-mcp '{"name":"mcp","type":"stdio","command":"docker","args":["run","-i","--rm","ghcr.io/rustok-org/rustok-wallet:v0.4.2"]}'Install rustok-wallet MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/rustok-org/rustok-wallet:v0.4.2"
]
}
}
}Install rustok-wallet MCP in Codex
$ codex mcp add mcp -- docker run -i --rm ghcr.io/rustok-org/rustok-wallet:v0.4.2Install rustok-wallet MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp] command = "docker" args = ["run", "-i", "--rm", "ghcr.io/rustok-org/rustok-wallet:v0.4.2"]
Install rustok-wallet MCP in Gemini CLI
$ gemini mcp add -s user mcp docker -- run -i --rm ghcr.io/rustok-org/rustok-wallet:v0.4.2Install rustok-wallet MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/rustok-org/rustok-wallet:v0.4.2"
]
}
}
}Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablerustok-org/mcp is public and reachablegithub.com/rustok-org/mcp ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MIT-0spdx.org/licenses/MIT-0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-11github.com/rustok-org/mcp ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubrustok-mcp
MCP Server for Rustok — connects Claude Desktop, Cursor, and cloud agents to the Rustok wallet via Gateway.
Two editions
Rustok ships two wallet products — pick the trust model you want:
rustok-wallet (agent edition) |
rustok-wallet-tui (this repo) |
|
|---|---|---|
| Who signs | the agent, unrestricted | you, in a separate terminal (rustok-console, y/N + PIN) |
| Where | rustokwallet.com · ClawHub · image ghcr.io/rustok-org/rustok-wallet |
this repo (main) · ClawHub · image ghcr.io/rustok-org/rustok-wallet-tui |
| Line | 0.4.x (maintained from the wallet-v0.4.0 tag) |
0.5.x+ |
Install (rustok-wallet-tui, self-custody)
Install trusted cosign 3+ independently, then use the verify-before-execute bootstrap in the published release skill. It downloads over --proto '=https' --tlsv1.2, verifies the manifest signature and installer hash before running the installer. There is no pipe-to-shell path. The repository skill is an unfilled source template; install wallet binaries only from the generated release/listing package.
rustok init # you choose a 6-digit PIN; the recovery phrase prints once
rustok connect claude # read-only; also cursor / hermes / openclaw
rustok connect claude --force --capabilities read_wallet,preview_tx,execute_tx requires confirmation in the user's own terminal before expanding rights. Core policy and PIN remain separate from the capability grant. rustok update verifies a signed release and preserves explicit subsets; live sessions retain their old image/grants until a human restart. There are no hard-coded spending limits after the user acknowledges unlimited autonomy.
The wallet is one self-contained image (Core + Gateway + MCP over stdio + the
human-approval console); keys live only in a local container volume and never
leave your machine. Transactions that move funds are approved by a human in a
second terminal with rustok console — the agent cannot drive it.
Install as an agent skill
The wallet skill (skills/rustok-wallet-tui/)
installs straight from this repo:
# skills CLI (Claude Code, Cursor, and other agents) — https://skills.sh
npx skills add rustok-org/mcp
# Hermes Agent
hermes skills tap add rustok-org/mcp
hermes skills install rustok-org/mcp/rustok-wallet-tui
Both editions are on ClawHub as separate listings: the agent edition at
@temrjan/rustok-wallet, and the
console edition — the maintained one — at
@rustok/wallet, published as
Rustok Agentic Wallet.
Registries
- Official MCP Registry — the agent edition is published as
io.github.rustok-org/rustok-wallet(OCI packageghcr.io/rustok-org/rustok-wallet, stdio). A TUI-edition registry entry ships separately asio.github.rustok-org/rustok-wallet-tui. - ClawHub — two listings: the console edition (maintained) at
@rustok/wallet, and the agent edition at@temrjan/rustok-wallet.
Quick Start (Development)
# Install dependencies
uv sync --dev
# Run the server
uv run rustok-mcp
# Or run stdio transport
uv run rustok-mcp-stdio
Docker
docker build -t rustok-mcp .
docker run -p 127.0.0.1:3001:3001 -e RUSTOK_MCP_HOST=0.0.0.0 rustok-mcp
To run the full stack (MCP → Gateway → Core + Redis), use the compose file
in rustok-org/meta.
Authentication
The network-facing SSE transport is gated by a shared bearer token.
- Inbound (
RUSTOK_MCP_INBOUND_API_KEY) — clients must sendAuthorization: Bearer <token>to reach/mcp/sseand/mcp/message. Distinct from the outboundRUSTOK_MCP_API_KEY(MCP → Gateway). - Dev: leave it empty — the loopback flow stays open and the server logs a warning at startup.
- Prod: required. The token must travel in the request header, never in a
query string (query strings leak into access logs). Generate one with
openssl rand -hex 32. - The browser
EventSourceAPI cannot set headers and is not a supported client; use an MCP client that sends request headers. /healthis always public (used by the container healthcheck).- The local stdio transport is process-trusted and not gated.
⚠️ The MCP has no built-in brute-force / rate-limit protection. Terminate it behind the edge proxy (Caddy) with host-level rate limiting (see the
rustok-org/metadeploy docs); do not expose it to the internet directly.
What is Rustok?
Rustok is a self-custody AI-native crypto wallet. The MCP Server is a thin bridge between LLM agents and the Rustok Gateway — private keys never leave the Core service (they stay in the local keystore volume).
- Self-custody: keys are encrypted at rest (Argon2id + AES-256-GCM) and only decrypted inside Core on your machine.
- Capability-gated tools (
read_wallet/preview_tx/execute_tx): the stdio transport defaults to read-only (explicit grants useRUSTOK_MCP_CAPABILITIES); the network-facing SSE transport is bearer-gated. - No spending policy by design: no hard-coded limits, budgets, or blocklists —
you consciously accept the risk of funds on the agent wallet.
txguardsurfaces a risk level on preview but does not block. Opt-in limits may come later. - Chains:
RUSTOK_ALLOWED_CHAINSdecides which ones are shown (default1,8453,42161— Ethereum, Base, Arbitrum). Those read out of the box: the build carries two public nodes for each. Naming your own (RUSTOK_RPC_URLS_<id>, or an Alchemy key) replaces the carried list rather than joining it. Any node that reads a balance learns the address and the IP that asked — that is true of ours, yours, and your provider's alike. - Informed preview:
preview_transactionreturns the decoded call (who/what is authorized), a pre-sign simulation (revert check), gas, and a txguard risk level. Execution is not exposed as an MCP tool. - Audit logging: every action is append-only logged to SQLite in Core.
Documentation
License
This repository is licensed under MIT-0.
The warranty and liability terms it carries, and the limit of every safeguard this wallet advertises, are stated in full here: https://github.com/rustok-org/mcp/blob/main/DISCLAIMER.md
The Rustok Core wallet engine is a proprietary artifact built from the private rustok-org/core repository.
rustok-wallet MCP questions
How do I add rustok-wallet MCP to Claude Code?
Run claude mcp add mcp -- docker run -i --rm ghcr.io/rustok-org/rustok-wallet:v0.4.2 in your terminal. Add --scope user to make it available in every project.
How do I add rustok-wallet MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Can the AI agent spend my funds without permission?
In the TUI edition, transactions must be approved by a human in a separate terminal using the rustok console.
Which blockchain networks are supported?
By default, it supports Ethereum, Base, and Arbitrum.