QuantConnect vs HEY Research Lab
QuantConnect is an MCP server published by QuantConnect. Marketplaces we read that list it: 1 (Docker MCP Catalog). HEY Research Lab is an MCP server published by hey-research-lab. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-26. 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): 32 Pulls (Docker Hub): 36 636 Stars (Docker Hub): 1 Stars (GitHub): 79 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.3.0 Downloads/month (npm): 1 168 Downloads/week (npm): 395 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.3.2 Downloads/month (npm): 1 168 Downloads/week (npm): 395 Forks (GitHub): 0 Stars (GitHub): 0 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 | HEY Research Lab |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 79 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 36 636 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 32 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-16 |
| Where it runs (differs) | On your machine (mcp/quantconnect) | Remote server or your machine |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 64 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 0 | 2, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/quantconnect/mcp-server | github.com/hey-research-lab/hey-research-open |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 5 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.
HEY Research Lab
Evidence-backed Robinhood Chain research: builders, ships, contracts, changes, market context.
How to run each
QuantConnect As a local MCP server: Docker image
claude mcp add --transport stdio quantconnect -- docker run -i --rm mcp/quantconnect
HEY Research Lab As a remote MCP server
claude mcp add --transport http hey-research https://heyresearch.xyz/mcp
Requires: HEY_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only HEY Research Lab has a remote endpoint we check. How we check endpoints
Tools each declares
Only QuantConnect has
abort_optimizationauthorize_connectionbroadcast_live_commandcheck_initialization_errorscheck_syntaxcomplete_codecreate_backtestcreate_compilecreate_filecreate_live_algorithmcreate_live_commandcreate_optimization
Show the remaining 52
create_projectcreate_project_collaboratordelete_backtestdelete_filedelete_objectdelete_optimizationdelete_projectdelete_project_collaboratorenhance_error_messageestimate_optimization_timeliquidate_live_algorithmlist_backtestslist_live_algorithmslist_object_store_fileslist_optimizationslist_projectslock_project_with_collaboratorspatch_fileread_accountread_backtestread_backtest_chartread_backtest_insightsread_backtest_ordersread_compileread_fileread_latest_mcp_server_versionread_lean_versionsread_live_algorithmread_live_chartread_live_insightsread_live_logsread_live_ordersread_live_portfolioread_mcp_server_versionread_object_propertiesread_object_store_file_download_urlread_object_store_file_job_idread_optimizationread_projectread_project_collaboratorsread_project_nodessearch_quantconnectstop_live_algorithmupdate_backtestupdate_code_to_pep8update_file_contentsupdate_file_nameupdate_optimizationupdate_projectupdate_project_collaboratorupdate_project_nodesupload_object
Only HEY Research Lab has
ask_heychain_overviewexplain_factfind_projectsget_changesget_contractget_evidenceget_project_snapshotget_project_timelineget_token_marketget_v4_hookmarket_integrity
Show the remaining 2
project_diffresearch_answer
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (HEY Research Lab as of 2026-10-15). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
Only QuantConnect asks for
AGENT_NAMEQUANTCONNECT_API_TOKENQUANTCONNECT_USER_ID
Only HEY Research Lab asks for
HEY_API_KEY (secret)HEY_MCP_PROFILE
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: QuantConnect · What it can do: HEY Research Lab · 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. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.