MCP server
HomeO-Exchange Compute Futures
On-chain compute futures exchange: live GPU price index + USDC-settled trading for AI agents.
- Endpoint
- Answering
- Works in
- 20 of 21 clients
- Tools
- 9
- Last checked
- Oct 5, 2026
Does O-Exchange Compute Futures work in your MCP client?
Registry name host.workbuddy.app.a959e52db0499cef3/oexchange-compute-futures, endpoint https://a959e52db0499cef3.app.workbuddy.host/mcp.
- Claude Codeworks
- Claude Desktopworks
- Claude.aiworks
- Claude API MCP connectorworks
- ChatGPTworks
- OpenAI Responses APIworks
- Codexworks
- Gemini CLIworks
- Cursorworks
- VS Code (GitHub Copilot)works
- Windsurf (Devin Desktop)works
- Zedworks
- JetBrains AI Assistantworks
- Junieunknownno source confirms Junie supports Streamable HTTP
- Clineworks
- Continueworks
- Gooseworks
- Lovableworks
- Replit Agentworks
- Bolt.newworks
- v0works
How clients sign in
No credentials: it answered lurq's probe without any.
Tools
futures_indexfutures_tradefutures_mandatefutures_opengpu_cheapestgpu_quoteexchange_bookplace_compute_orderlist_compute_offer
Get the setup for your client from your agent
This page is a daily snapshot. lurq's connect_check answers for the client you are wiring this server into, with the exact steps and the config to paste in that client's own format, and lurq mcp-pin tells you when the server changes. One command connects Claude Code, Cursor, VS Code and other agents:
npx lurqrun
Free to start. How connect_check works
From lurq's credential-free probe of this server's endpoint on Oct 5, 2026, and each client's own documentation. This page refreshes every 168 hours. How the probe works, and how maintainers opt out.