MCP Tools DirectoryAbout this integration
Give an AI agent a Solana spending allowance instead of your key. Chain-enforced cap, x402.
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- user-authorization
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.1.0
- Package
- @three-ws/onchain-agent-wallets
- Last compatibility test
- Not independently tested
Connect your agent
@three-ws/onchain-agent-walletsPublisher README and package manifest reviewed. The package, Solana connection, wallet operations, and x402 endpoints were not executed or independently security-audited; value-moving use requires separate risk review.
Capabilities: Delegated Solana wallet management, Guardrailed token transfers and x402 payments, Wallet status and spend logs
Connected profiles
Additional details
io.github.nirholas/onchain-agent-wallets
Source ↗ · Checked 2026-09-170.1.0
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17npm
Source ↗ · Checked 2026-09-17@three-ws/onchain-agent-wallets
Source ↗ · Checked 2026-09-190.1.0
Source ↗ · Checked 2026-09-19The documented local MCP command launches the npm artifact, and the post-setup agent can spend within the delegated allowance and configured guardrails.
Source ↗ · Checked 2026-09-19Owner actions use unsigned transactions approved in the owner's wallet, or an optional OWNER_SECRET_KEY for server-side signing; this wallet-signature model is outside the native authentication taxonomy.
Source ↗ · Checked 2026-09-19An MCP client launches the package locally with npx -y @three-ws/onchain-agent-wallets.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19