Uniswap Setup DCA
WarnAudited by ClawScan on May 10, 2026.
Overview
This Uniswap DCA skill is purpose-aligned, but it can approve and execute recurring wallet trades, including an immediate first swap, so users should review it carefully before use.
Use this only if you are comfortable letting an agent help sign approvals and swaps. Prefer testnet first, cap the allowance and total spend, avoid indefinite schedules, require explicit confirmation before every approval or first swap, and make sure you know how to pause the keeper and revoke approvals before using a mainnet wallet.
Findings (6)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If invoked with a funded wallet, the agent may be able to submit swaps that spend the user's tokens.
The skill grants the agent and a trade-executor subagent access to tools that can inspect balances and execute swaps, which is high-impact financial mutation authority.
allowed-tools:\n - Task(subagent_type:trade-executor)\n - mcp__uniswap__execute_swap\n - mcp__uniswap__get_quote\n - mcp__uniswap__get_agent_balance
Require explicit user confirmation immediately before any approval or swap, show exact token amounts, chain, recipient, route, slippage, and gas, and prefer testnet or very small amounts first.
An overly broad or long-lived approval could let recurring executions continue spending from the user's wallet beyond what they intended.
Permit2 approvals and swap execution require delegated wallet authority, and the visible artifact does not clearly bound approval allowance, duration, revocation, or signer controls.
handles Permit2 approvals, executes the first swap, and sets up ongoing automation
Use tightly capped allowances, set a clear end date and execution count, confirm the spender contract, and provide clear revocation instructions before enabling mainnet use.
A recurring bot or keeper could continue trading on schedule and spend funds repeatedly if the user does not know how to pause, stop, or revoke it.
The skill's default mode involves recurring automated execution, including agent-triggered swaps or an on-chain keeper, which can keep acting after initial setup.
keeperMode | No | self-execute | "self-execute" (agent-triggered) or "gelato" (on-chain keeper automation)
Do not use indefinite schedules by default; require a maximum execution count, spend cap, end date, and clear pause/cancel/revoke procedure.
A user who intended only to configure or preview a DCA strategy could trigger an immediate swap.
The default is to execute the first financial transaction immediately, which raises user-control risk unless there is an explicit final confirmation step.
startImmediately | No | true | Whether to execute the first swap now
Default to preview-only setup and require an explicit 'execute first swap now' confirmation.
Wallet balance, strategy details, and trading actions may be exposed to or handled by external tool/provider components.
The workflow delegates financial context and actions to a subagent and Uniswap MCP tools; this appears purpose-aligned, but the artifact does not describe those communication boundaries.
Task(subagent_type:trade-executor)\n - mcp__uniswap__execute_swap\n - mcp__uniswap__get_token_price\n - mcp__uniswap__get_agent_balance
Use only trusted MCP servers and subagents, and verify what wallet/account data they can access before connecting a production wallet.
Installing from moving sources can change what is installed over time.
The README documents installation through a moving GitHub branch and an @latest package; this is common setup documentation, but users should verify provenance.
npx skills add https://github.com/wpank/Agentic-Uniswap/tree/main/.ai/skills/setup-dca\n...\nnpx clawhub@latest install setup-dca
Install from a trusted registry or pinned commit/version, especially before connecting a wallet with funds.