Ext Ops Panel
Open dashboard
Comparison

QuantConnect vs KLinePic

QuantConnect is an MCP server published by QuantConnect. Marketplaces we read that list it: 1 (Docker MCP Catalog). KLinePic is an MCP server published by sher1096. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
MarketplaceQuantConnectKLinePic
Docker MCP Catalog Listed
Version: sha256:f96cc99e83a0
Forks (GitHub): 33
Pulls (Docker Hub): 36 158
Stars (Docker Hub): 1
Stars (GitHub): 79
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
No figure published
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 KLinePic
FactQuantConnectKLinePic
Marketplaces that list it11
Stars (GitHub) (differs)79No figure on GitHub
Pulls (Docker Hub) (differs)36 158No figure on Docker Hub
Forks (GitHub) (differs)33No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/quantconnect)On your machine (ghcr.io/sher1096/klinepic-mcp-server:0.1.0)
Transportstdiostdio
Tools it declares (differs)64Not published
Environment variables it asks for (differs)3, secrets among them: 01, secrets among them: 1
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/quantconnect/mcp-servergithub.com/sher1096/klinepic-agent-api-examples
Changes in the last 7 days00
First seen2026-10-112026-10-11

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.

KLinePic

In its own words, on Official MCP Registry:

Create annotated candlestick charts from broker or exchange fills for post-trade review.

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

KLinePic As a local MCP server: Docker image

Claude Code
claude mcp add --env "KLINE_AGENT_API_KEY=<YOUR_KLINE_AGENT_API_KEY>" --transport stdio klinepic -- docker run -i --rm -e KLINE_AGENT_API_KEY ghcr.io/sher1096/klinepic-mcp-server:0.1.0

Requires: KLINE_AGENT_API_KEY (secret)

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

Tools each declares

The marketplaces of KLinePic publish no list of tools, so we do not compare tools.

Settings each asks for

Only QuantConnect asks for

  • AGENT_NAME
  • QUANTCONNECT_API_TOKEN
  • QUANTCONNECT_USER_ID

Only KLinePic asks for

  • KLINE_AGENT_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: QuantConnect · What it can do: KLinePic · 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.

Where the data comes from: how the catalog is built