sap_perpspad_build_launch

ai.oobeprotocol.sap.mcp/sap-mcp · Verify this server

Build a PerpsPad token launch backed by a leveraged perp: returns the UNSIGNED config + pool transactions. This tool does NOT broadcast anything — sign and send BOTH transactions from the user wallet (pays rent, dev-buy 0.1-5 SOL or 5-5000 USDC, and the 0.01 SOL fee), then poll sap_perpspad_get_launch_status until live. Backing: underlying+leverage+direction (single) or 2-leg basket. Validate leverage against sap_perpspad_get_markets. BUILDER tier. SAP MCP execution guidance: Intent: hosted unsigned transaction builder. Pricing: paid builder; estimate first, then pay/build and finalize unsigned transactions locally when returned. Routing: paid hosted call; call sap_estimate_tool_cost first, then use sap_payments_call_paid_tool if the runtime cannot handle x402 natively. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.