Sato Hub
MCP

QuantConnect MCP

Official open-source QuantConnect MCP for quant project management, doc search, code checks, and backtesting.

  • Sato Score48
ActiveSelf-Reported

QuantConnect MCP is an open-source MCP server by QuantConnect, with no code activity tracked. Sato Score 48/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-15. How the score works →

See how to install QuantConnect MCP →

No code activity tracked

Listed from quantconnect.com on 2026-07-13. Install: not attempted. Evidence →

Next step

Check it from your agent

Add Sato Hub’s MCP server (no key), then ask:

https://satohub.ai/api/mcp
Ask Sato Hub what is on record about QuantConnect MCP before I use it.
Full setup: Claude Code, Cursor, others →

Your project?

Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.

Claim this listing →

Overview

QuantConnect MCP is an official, open-source server maintained by QuantConnect that bridges AI coding assistants to its quantitative trading platform. It provides project/file management, vector search across docs and the QCAlgorithm API, static code checks, autonomous backtesting and result analysis, parameter optimization, and live trading deployment/management. Agent builders plug it in to let an agent draft, test, and iterate on trading strategies directly against QuantConnect's research and backtesting infrastructure.

Sato Score

48/100· Medium

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness
20/35
Code transparency
8/20
Interface verifiability
0/10
Docs & demo
6/10
Listing transparency & provenance
11/15
Independent verification
3/10

Evidence — listed vs checked · what the words mean

Listed from quantconnect.com on 2026-07-13. Install: not attempted.

ClaimValueEvidenceSourceChecked
Chains supportednot statedself-reportedquantconnect.comas of 2026-10-15
Verification statusSelf-Reported — not independently reviewedself-reportedquantconnect.comas of 2026-10-15
Install worksdocumented by the project, not run by Sato Hubnot attempted by Sato Hubself-reportedraw.githubusercontent.comas of 2026-07-20
Website answersanswered (HTTP 200)observedquantconnect.com2026-10-15
Daily check record90 of 90 daily checks since 2026-07-17 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-10-14
Deploys asLocal/self-hosted (Deploy Container), GitHub Copilot integration (localhost HTT…confidence 0.75self-reportedquantconnect.comas of 2026-07-14
Works withGitHub Copilotconfidence 0.85self-reportedquantconnect.comas of 2026-07-14
Sato Score48/100 (Medium)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-10-15

Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.

Install — as documented by the project, not run by us

Runtime: Docker (official image quantconnect/mcp-server)

docker pull quantconnect/mcp-server
{"mcpServers": {"quantconnect": {"command": "docker", "args": ["run", "-i", "--rm", "-e", "QUANTCONNECT_USER_ID", "-e", "QUANTCONNECT_API_TOKEN", "-e", "AGENT_NAME", "--platform", "<your_platform>", "quantconnect/mcp-server"], "env": {"QUANTCONNECT_USER_ID": "<your_user_id>", "QUANTCONNECT_API_TOKEN": "<your_api_token>", "AGENT_NAME": "MCP Server"}}}}

You supply: QUANTCONNECT_USER_ID, QUANTCONNECT_API_TOKEN (QuantConnect API token), AGENT_NAME optional

MCP invocation: docker run -i --rm quantconnect/mcp-server (stdio)

Read from the project’s own docs as of 2026-07-20. What a deploy spec is →

Observed record — 91 daily checks since 2026-07-17

100%of 91 checks since 2026-07-17 succeeded
Currently responding for 91 days
Succeeded
91
Failed
0
Their error
0
Unattributed
0

This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 46 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.

Last 30 days — to 2026-10-15, one point per UTC day

Share of OUR checks that succeeded
100%
7-day rolling; unattributable days are gaps · 30/30 days
Tools listed
fewer than 2 points—
from the server's own tools/list · 0/30 days
Sato Score
48
as snapshotted that day · 29/30 days

A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.

Details

Chains
Unknown
Agent types
MCP Server, Trading
Open source
Yes
Deploys as
Local/self-hosted (Deploy Container), GitHub Copilot integration (localhost HTTP endpoint)
Works with
GitHub Copilot
Last checked
2026-10-15

Marketplace Signals

No marketplace signals recorded for this resource yet.

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#quant-trading#backtesting#developer-tools#strategy-testing

Where QuantConnect MCP fits

Related concepts: How Agents Interact With Smart Contracts, How Agents Use Wallets

See something inaccurate or outdated?Submit a correction →

Listing History

Recorded changes to QuantConnect MCP's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

  1. Jul 20, 2026
    Edited: deploy spec
  2. Jul 18, 2026
    Sato Hub began tracking this listing
  3. Jul 14, 2026
    Enriched: deployment options
  4. Jul 14, 2026
    Auto-enriched: supported integrations
  5. Jul 13, 2026
    Listed on Sato Hub

Compared with

Appears in

Related Resources

Reference

QuestionsShowHide

Questions people ask about QuantConnect MCP

Is QuantConnect MCP open source?
Yes. QuantConnect MCP is open source under the Unknown license. Checked as of 2026-10-15.
Which chains does QuantConnect MCP support?
Sato Hub has no confirmed chain list for QuantConnect MCP as of 2026-10-15; treat chain support as unknown.
Is QuantConnect MCP still maintained?
Sato Hub tracks no commit or release for QuantConnect MCP; it cannot say whether it is maintained.
How do I install or run QuantConnect MCP?
Docker (official image quantconnect/mcp-server). Install: docker pull quantconnect/mcp-server. Entry: {"mcpServers": {"quantconnect": {"command": "docker", "args": ["run", "-i", "--rm", "-e", "QUANTCONNECT_USER_ID", "-e", "QUANTCONNECT_API_TOKEN", "-e", "AGENT_NAME", "--platform", "<your_platform>", "quantconnect/mcp-server"], "env": {"QUANTCONNECT_USER_ID": "<your_user_id>", "QUANTCONNECT_API_TOKEN": "<your_api_token>", "AGENT_NAME": "MCP Server"}}}}. This is taken from the project's own documentation and has not been reproduced by Sato Hub. It runs as an MCP server (docker run -i --rm quantconnect/mcp-server (stdio)).
Is QuantConnect MCP verified on Sato Hub?
No independent verification is on record for QuantConnect MCP; its verification status is "Self-Reported" and its Sato Score is 48 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "QuantConnect MCP — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/quantconnect-mcp

Data last refreshed 2026-10-15; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.

Join the Sato Hub Briefing

Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.