Ext Ops Panel
Open dashboard
Comparison

QuantConnect vs Financial Evidence

QuantConnect is an MCP server published by QuantConnect. Marketplaces we read that list it: 1 (Docker MCP Catalog). Financial Evidence is an MCP server published by beepboop2025. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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
MarketplaceQuantConnectFinancial Evidence
Docker MCP Catalog Listed
Version: sha256:f96cc99e83a0
Forks (GitHub): 33
Pulls (Docker Hub): 36 239
Stars (Docker Hub): 1
Stars (GitHub): 79
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.13
Forks (GitHub): 0
Stars (GitHub): 1
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 Financial Evidence
FactQuantConnectFinancial Evidence
Marketplaces that list it11
Stars (GitHub) (differs)79 (better)1 (worse)
Pulls (Docker Hub) (differs)36 239No figure on Docker Hub
Forks (GitHub) (differs)33 (better)0 (worse)
Last release (differs)Not published2026-10-17
Where it runs (differs)On your machine (mcp/quantconnect)Remote server (liquilens.in/mcp/financial-evidence)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)64Not published
Environment variables it asks for (differs)3, secrets among them: 0Not published
Licence (differs)Apache-2.0MIT
Repository (differs)github.com/quantconnect/mcp-servergithub.com/beepboop2025/financial-evidence-skills
Changes in the last 7 days (differs)015
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.

Financial Evidence

In its own words, on Official MCP Registry:

Read-only public financial evidence from LiquiLens, Undertow, Seiche and Palimpsest.

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

Financial Evidence As a remote MCP server

Claude Code
claude mcp add --transport http financial-evidence https://liquilens.in/mcp/financial-evidence

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Financial Evidence 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 Financial Evidence has

  • financial_evidence_fetch
  • financial_evidence_route
  • financial_evidence_topics

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (Financial Evidence as of 2026-10-17). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

The marketplaces of Financial Evidence publish no settings it asks for, so we do not compare settings.

What it can do: QuantConnect · What it can do: Financial Evidence · 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. Data comes from public marketplace files in GitHub repositories of their authors. 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