Account and network
Legend connector grants are bound to a main account onhyperliquid_mainnet. The connector has no paper or testnet mode. Trading-enabled access can change real positions and incur losses, fees, funding, and liquidation risk.
Preview access
MCP access additionally requires the server-sideai-connectors-enabled feature flag. The production preview is limited to Legend employees. Disabling access blocks new approvals, token exchange, refresh, and subsequent MCP requests once the flag configuration reaches the server. Direct Trading API access has its own separate gate.
Scopes
These MCP scopes are distinct from the underlying Trading API key scopes,
trading:read and trading:write. The server checks both the OAuth grant and its associated account credential. A read-only grant cannot acquire trading permission by calling the other endpoint.
Neither endpoint provides withdrawals or transfers. No tool accepts an arbitrary wallet signer or a caller-selected account override.
Consent and confirmation
The OAuth flow opens Legend for sign-in and permission approval. It uses authorization code flow with PKCE S256. Access tokens expire after one hour. Refresh tokens rotate, have a maximum lifetime of 30 days for the grant, and reuse of a consumed refresh token revokes that token family. Approving execution permission authorizes subsequent supported tool calls. The MCP server does not enforce a separate on-site confirmation for every execution call. A host may provide additional confirmation UI; do not assume that UI exists in every integration. Theprepare_order tool is different: it creates a review link without submitting an order. You can open the link, inspect the values, and separately submit through Legend’s trade form.