sap_phoenix_build_register_trader

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

Create a Phoenix trader account (RegisterTrader only — the account stays FROZEN with NO deposit capability until activation). Full onboarding = registration + activation: 1) sap_phoenix_build_register_trader → preview/sign/submit locally (creates the account); 2) sap_phoenix_build_onboard_trader + sap_phoenix_submit_onboard_trader (Phoenix co-signs, enables deposit/withdraw/trade); 3) verify with sap_phoenix_get_trader_state — state must leave "frozen" and depositCollateral must be immediate before sap_phoenix_build_deposit can succeed. 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.