{"jsonrpc":"2.0","result":{"protocolVersion":"2024-11-05","serverInfo":{"name":"ailinux-mcp-server","version":"2.86.8","description":"AILinux TriForce MCP Server"},"capabilities":{"tools":true,"prompts":true,"resources":true},"transports":["http","sse"],"endpoints":{"sse":"/v1/mcp/sse","messages":"/v1/mcp/messages"},"instructions":"This is the public TriForce MCP. Safe TriForce cloud tools execute on the server. For local workspace/device work, first inspect workspace_status and treat the live capability list as authoritative. connected=true alone is insufficient for local execution: require transport_state=online and executor_online=true. Android computer_observe/computer_input/app_ops require the user's Computer Control grant plus a ready AccessibilityService; if they disappear, re-check workspace status and Helper state rather than retrying a missing tool. Pair codes are short-lived bootstrap credentials; after successful pairing the Helper must resume with its persisted server-issued credential, so do not ask for a new pair code merely because the app was backgrounded or the backend restarted. For Android UI control use observe -> semantic target/invoke -> observe and re-resolve targets after every UI transition. Never expose workspace/resume tokens, lease IDs, pairing internals, or other credentials. If no workspace is paired and local access is needed, ask the user to open https://api.ailinux.me/v1/mcp, choose the intended share/capabilities, and paste the one-time pairing ID into this chat; then call workspace_pair."}}