Ext Ops Panel
Open dashboard
Comparison

OpenZeppelin Stellar Contracts vs KLinePic

OpenZeppelin Stellar Contracts is an MCP server published by docker. 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-16. 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
MarketplaceOpenZeppelin Stellar ContractsKLinePic
Docker MCP Catalog Listed
Version: not stated
No figure published
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

OpenZeppelin Stellar Contracts vs KLinePic
FactOpenZeppelin Stellar ContractsKLinePic
Marketplaces that list it11
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.openzeppelin.com/contracts/stellar/mcp)On your machine (ghcr.io/sher1096/klinepic-mcp-server:0.1.0)
Transport (differs)Streamable HTTPstdio
Tools it declares (differs)6Not published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/sher1096/klinepic-agent-api-examples
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 13 h agono remote endpoint we check

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

OpenZeppelin Stellar Contracts

In its own words, on Docker MCP Catalog:

Access to OpenZeppelin Stellar Contracts.

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

OpenZeppelin Stellar Contracts As a remote MCP server

Claude Code
claude mcp add --transport http openzeppelin-stellar https://mcp.openzeppelin.com/contracts/stellar/mcp

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.

Only OpenZeppelin Stellar Contracts has a remote endpoint we check. How we check endpoints

Tools each declares

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

Settings each asks for

The marketplaces of OpenZeppelin Stellar Contracts publish no settings it asks for, so we do not compare settings.

What it can do: OpenZeppelin Stellar Contracts · 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