QuantConnect vs TradeOS (test)
QuantConnect is an MCP server published by QuantConnect. Marketplaces we read that list it: 1 (Docker MCP Catalog). TradeOS (test) is an MCP server published by TradeOS-AI. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:f96cc99e83a0 Forks (GitHub): 33 Pulls (Docker Hub): 36 179 Stars (Docker Hub): 1 Stars (GitHub): 79 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0-alpha.6 Downloads/month (npm): 122 Downloads/week (npm): 24 Forks (GitHub): 7 Stars (GitHub): 13 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | QuantConnect | TradeOS (test) |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 79 (better) | 13 (worse) |
| Pulls (Docker Hub) (differs) | 36 179 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 33 (better) | 7 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/quantconnect) | Remote server (ai.tradeos.xyz/api/agent/mcp-call) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 64 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 0 | 1, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/quantconnect/mcp-server | github.com/tradeos-ai/tradeos-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 404 (3 days ago) |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
QuantConnect
The QuantConnect MCP Server is a bridge for AIs (such as Claude and OpenAI o3 Pro) to interact with our cloud platform. When equipped with our MCP, the AI can perform tasks on your behalf through our API such as updating projects, writing strategies, backtesting, and deploying strategies to production live-trading.
TradeOS (test)
[TEST] TradeOS MCP bridge: ticker search, My Agent, chart TA, macro news. npm or HTTP.
How to run each
QuantConnect As a local MCP server: Docker image
claude mcp add --transport stdio quantconnect -- docker run -i --rm mcp/quantconnect
TradeOS (test) As a remote MCP server
claude mcp add --transport http tradeos-mcp-test https://ai.tradeos.xyz/api/agent/mcp-call
Requires: TRADEOS_ACCESS_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only TradeOS (test) has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of TradeOS (test) publish no list of tools, so we do not compare tools.
Settings each asks for
Only QuantConnect asks for
AGENT_NAMEQUANTCONNECT_API_TOKENQUANTCONNECT_USER_ID
Only TradeOS (test) asks for
TRADEOS_ACCESS_TOKEN (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: QuantConnect · What it can do: TradeOS (test) · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.