yo-base-mcp-pluginlisted

# YO Protocol Plugin > [!IMPORTANT] > Complete the short Base MCP onboarding flow defined in the base `SKILL.md` before calling any YO command or endpoint. Fetch the user's wallet address only when a flow actually needs it (positions, prepare/write flows, rewards). YO Protocol is an ERC-4626 yield aggregator with **ERC-7540-style async redemption**. **Both deposit and withdraw go through the YO Gateway** at `0xF1EeE0957267b1A474323Ff9CfF7719E964969FA` (same address on every supported chain) — not direct calls to the vault. The Gateway handles slippage protection, partner IDs, and instant/async routing. A single redeem call either settles instantly (when the vault has enough idle assets) or queues; a YO solver auto-fulfills queued redeems on-chain within ~24 hours, so the user never sends a second transaction. This plugin has two supported execution paths: 1. **CLI-capable harnesses:** use `@yo-protocol/cli` for vault state, positions, balances, deposits, and withdraws. 1. **Chat-only or no-shell harnesses:** use the YO HTTP API (`https://api.yo.xyz/api/v1`) for reads + `/transactions/zapIn` for deposits, and Base MCP's `read_contract` / contract encoding for withdraws and Merkl claims. There is no hosted YO MCP server. The CLI does **not** produce calldata for claiming Merkl rewards — claims always use direct ABI encoding on the Merkl Distributor. The CLI also does not bridge across chains — cross-chain deposits go through `/transactions/zapIn`. Prefer the CLI whenever