Ext Ops Panel
Open dashboard
Comparison

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

Where each is published
MarketplaceQuantConnectHEY Research Lab
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

QuantConnect vs HEY Research Lab
FactQuantConnectHEY Research Lab
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)79 (better)0 (worse)
Pulls (Docker Hub) (differs)36 636No figure on Docker Hub
Forks (GitHub) (differs)32 (better)0 (worse)
Last release (differs)Not published2026-10-16
Where it runs (differs)On your machine (mcp/quantconnect)Remote server or your machine
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)64Not published
Environment variables it asks for (differs)3, secrets among them: 02, secrets among them: 1
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/quantconnect/mcp-servergithub.com/hey-research-lab/hey-research-open
Changes in the last 7 days (differs)01
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 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

In its own words, on Docker MCP Catalog:

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

In its own words, on Official MCP Registry:

Evidence-backed Robinhood Chain research: builders, ships, contracts, changes, market context.

How to run each

QuantConnect As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio quantconnect -- docker run -i --rm mcp/quantconnect

HEY Research Lab As a remote MCP server

Claude Code
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_optimization
  • authorize_connection
  • broadcast_live_command
  • check_initialization_errors
  • check_syntax
  • complete_code
  • create_backtest
  • create_compile
  • create_file
  • create_live_algorithm
  • create_live_command
  • create_optimization
Show the remaining 52
  • create_project
  • create_project_collaborator
  • delete_backtest
  • delete_file
  • delete_object
  • delete_optimization
  • delete_project
  • delete_project_collaborator
  • enhance_error_message
  • estimate_optimization_time
  • liquidate_live_algorithm
  • list_backtests
  • list_live_algorithms
  • list_object_store_files
  • list_optimizations
  • list_projects
  • lock_project_with_collaborators
  • patch_file
  • read_account
  • read_backtest
  • read_backtest_chart
  • read_backtest_insights
  • read_backtest_orders
  • read_compile
  • read_file
  • read_latest_mcp_server_version
  • read_lean_versions
  • read_live_algorithm
  • read_live_chart
  • read_live_insights
  • read_live_logs
  • read_live_orders
  • read_live_portfolio
  • read_mcp_server_version
  • read_object_properties
  • read_object_store_file_download_url
  • read_object_store_file_job_id
  • read_optimization
  • read_project
  • read_project_collaborators
  • read_project_nodes
  • search_quantconnect
  • stop_live_algorithm
  • update_backtest
  • update_code_to_pep8
  • update_file_contents
  • update_file_name
  • update_optimization
  • update_project
  • update_project_collaborator
  • update_project_nodes
  • upload_object

Only HEY Research Lab has

  • ask_hey
  • chain_overview
  • explain_fact
  • find_projects
  • get_changes
  • get_contract
  • get_evidence
  • get_project_snapshot
  • get_project_timeline
  • get_token_market
  • get_v4_hook
  • market_integrity
Show the remaining 2
  • project_diff
  • research_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_NAME
  • QUANTCONNECT_API_TOKEN
  • QUANTCONNECT_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.

Where the data comes from: how the catalog is built