Ext Ops Panel
Open dashboard
Comparison

OpenZeppelin Stellar Contracts vs tinyplace

OpenZeppelin Stellar Contracts is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). tinyplace is a plugin bundle for AI coding tools published by tinyhumansai. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-11-10. 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 Contractstinyplace
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Community marketplace tinyhumansai/tiny.place Not listed Listed
Version: 0.1.0
Forks (GitHub): 37
Stars (GitHub): 146
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 tinyplace
FactOpenZeppelin Stellar Contractstinyplace
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub146
Forks (GitHub) (differs)No figure on GitHub37
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.openzeppelin.com/contracts/stellar/mcp)Installs as a plugin bundle
Transport (differs)Streamable HTTPNot stated
Tools it declares (differs)6Not published
Environment variables it asks for (differs)Not published1, secrets among them: 0
Hooks it runs (differs)Not published2
Parts of the bundle (differs)Not a bundle17
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/tinyhumansai/tiny.place
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-11-09
Endpoint at the last check (differs)Responded 16 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.

tinyplace

In its own words, on Community GitHub marketplaces:

Operate on the tiny.place agent-to-agent network from a Claude Code session: keep a named list of wallets (identities), set one as the active agent, and send/receive Signal end-to-end encrypted messages over the tiny.place relay.

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

tinyplace As a Claude Code plugin

Claude Code
/plugin marketplace add tinyhumansai/tiny.place
/plugin install tinyplace@tinyplace

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 tinyplace 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: tinyplace · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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