Aurey Wallet MCP
Self-hosted Model Context Protocol server for EVM wallet tools: balances, swaps, and prepare/execute signing through 1Claw Intents (no private keys in chat or MCP env for Alchemy).
Works with Hermes Agent, Cursor, Claude Desktop, and OpenClaw.
Quick start (aurey-setup)
One 1Claw human API key (1ck_… from 1claw.xyz) in your terminal only—never in LLM chat.
Install without a git clone (full guide):
curl -fsSL https://agentic-pantheon.github.io/aurey-mcp/install.sh | bash
aurey-setup --host hermes
Manual: pip install 'aurey-wallet-mcp[hermes]' or uv tool install 'aurey-wallet-mcp[hermes]', then aurey-setup --host hermes.
Contributors (develop from source):
git clone https://github.com/agentic-pantheon/aurey-mcp.git
cd aurey-mcp
uv sync --group dev --extra hermes
uv run aurey-setup --host hermes
Masked prompts: 1ck_…, then optional Alchemy key (stored in 1Claw, not MCP env). Typed secrets show * in the terminal.
Version / upgrade: aurey-version · aurey-update --host hermes (PyPI upgrade + re-wire from ~/.aurey/mcp.env) — see install/index.md.
Choose your MCP host
--host |
After install |
|---|---|
hermes (default) |
hermes mcp test aurey-wallet → chat /reload-mcp |
cursor |
Restart Cursor or reload MCP in Settings |
claude |
Quit and reopen Claude Desktop |
openclaw |
Restart the OpenClaw gateway |
aurey-setup --host cursor
aurey-setup --host claude
aurey-setup --host openclaw
(From a dev clone, prefix with uv run.)
Host-specific notes: install/hermes.md · cursor · claude · openclaw.
What aurey-setup does
- 1Claw (Human API) — auth with
1ck_…; pick or create vault; create Intents agent; read policy onapi-keys/**; optional Alchemy atapi-keys/alchemy; provision Ethereum signing key. - Credentials —
~/.aurey/mcp.env(vault id, agent id,ocv_…, mode600). - MCP launcher —
~/.aurey/run-aurey-wallet-mcp.sh(sourcesmcp.env; keeps secrets out of host JSON). - Host config — patches Hermes / Cursor / Claude / OpenClaw MCP entry to use the wrapper.
- Alchemy path —
~/.aurey/config.toml→alchemy_secret_path = "api-keys/alchemy". - Smoke test — optional MCP bootstrap check.
Hermes also updates ~/.hermes/config.yaml and ~/.hermes/.env. For Hermes YAML edits: uv sync --extra hermes (included when you run aurey-setup --host hermes).
Useful flags
uv run aurey-setup --vault-id '<uuid>' # use existing vault
uv run aurey-setup --skip-alchemy # add Alchemy in 1Claw later
uv run aurey-setup --from-env # ephemeral: read AUREY_ONECLAW_HUMAN_API_KEY once, never written to mcp.env
uv run aurey-setup --provision-only # 1Claw + mcp.env only
uv run aurey-setup --host cursor --skip-provision # re-wire MCP from ~/.aurey/mcp.env
uv run aurey-setup --host cursor --cursor-project . # project .cursor/mcp.json
uv run aurey-setup --config /path/to/mcp.json # override config file
Verify in chat
Load agent skills (SKILL.md). Ask your agent to call get_agent_wallet_addresses, then a read-only balance. Swaps/sends: prepare → you confirm → tx_execute(prepared_id=…).
Secrets (do not paste in chat)
| Value | Where |
|---|---|
1ck_… (human) |
aurey-setup prompt only — never in ~/.aurey/mcp.env or MCP host env |
ocv_… (agent) |
~/.aurey/mcp.env, ~/.hermes/.env (Hermes) |
| Alchemy | 1Claw vault api-keys/alchemy |
| Vault / agent UUID | OK in chat for debugging |
Manual / advanced
Hermes without full provision (you already have vault, agent, ocv_ in the dashboard):
uv sync --group dev --extra hermes
uv run aurey-hermes-install --prompt-secrets
Run MCP in a shell (after 1Claw is configured):
export AUREY_ONECLAW_VAULT_ID=...
export AUREY_ONECLAW_VAULT_API_KEY=...
export AUREY_ONECLAW_AGENT_ID=...
uv run aurey-wallet-mcp
Manual 1Claw steps: docs/1claw-onboarding-guide.md.
Components
| Component | Purpose |
|---|---|
aurey-setup |
1Claw provision + MCP install (all hosts) |
aurey-hermes-install |
Hermes-only install when 1Claw is already done |
aurey-wallet-mcp |
MCP stdio server + optional local dashboard |
| aurey-route-builder | Hosted LiFi quote proxy (25 bps fee; used by default) |
| x402 MCP tools | Paid HTTP APIs via 1Claw wallet (x402_preview, x402_fetch, …) |
Docs
| Doc | Audience |
|---|---|
| install/hermes.md | Full aurey-setup reference + Hermes |
| install/cursor.md | Cursor |
| install/claude.md | Claude Desktop |
| install/openclaw.md | OpenClaw |
| docs/setup.md | Env vars, route builder, dashboard |
| docs/1claw-onboarding-guide.md | 1Claw + agent coaching |
| ONBOARDING_1CLAW.md | One-page agent playbook |
| docs/releasing.md | PyPI + GitHub Pages releases (maintainers) |
| SKILL.md | Load skills/aurey-wallet-onboarding + skills/aurey-wallet |
Safety
tx_executeonly accepts server-issuedprepared_idvalues.- Signing via 1Claw Intents; private keys are not exposed to the model.
- Autonomy tools default to dry-run; arming is explicit and local.
Metadata
Release files for aurey-wallet-mcp 0.1.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| aurey_wallet_mcp-0.1.8.tar.gz | 1.0 MB | With provenance | Details for aurey_wallet_mcp-0.1.8.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| aurey_wallet_mcp-0.1.8-py3-none-any.whl | Python 3 | none | any | Details for aurey_wallet_mcp-0.1.8-py3-none-any.whl |
Total release size: 2.1 MB
Release files / aurey_wallet_mcp-0.1.8.tar.gz
| Download URL | aurey_wallet_mcp-0.1.8.tar.gz |
|---|---|
| Size | 1.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1e07b1ab8c29a1256bd2f7b0fd1d161a46864d33a5b9ca293b4b12fafb750794
|
|
BLAKE2b-256 checksum How to use checksums |
918b0b805f2f35389b2c9d933013092d7fe9df7df87c12c08467c7e4ab6879f9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 12, 2026.
Transparency logRelease files / aurey_wallet_mcp-0.1.8-py3-none-any.whl
| Download URL | aurey_wallet_mcp-0.1.8-py3-none-any.whl |
|---|---|
| Size | 1.1 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b795b5477f66783611fe0d818668c9869f0f8fec2c5985c9437bb899ef721c4e
|
|
BLAKE2b-256 checksum How to use checksums |
f925e2045c65b8301f808f74201921cd51fc869100745fb7a3c4b5e62b88bc24
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 12, 2026.
Transparency logSecurity for aurey-wallet-mcp 0.1.8
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for aurey_wallet_mcp-0.1.8.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 12, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.