Ext Ops Panel
Open dashboard
Comparison

OpenZeppelin Stellar Contracts vs Verify SCITT receipts from Forestrie transparency logs, offline

OpenZeppelin Stellar Contracts is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). Verify SCITT receipts from Forestrie transparency logs, offline is an MCP server published by forestrie.dev. 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
MarketplaceOpenZeppelin Stellar ContractsVerify SCITT receipts from Forestrie transparency logs, offline
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.5.2
Downloads/month (npm): 2 450
Downloads/week (npm): 240
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

OpenZeppelin Stellar Contracts vs Verify SCITT receipts from Forestrie transparency logs, offline
FactOpenZeppelin Stellar ContractsVerify SCITT receipts from Forestrie transparency logs, offline
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.openzeppelin.com/contracts/stellar/mcp)On your machine (@forestrie/mcp-verify)
Transport (differs)Streamable HTTPstdio
Tools it declares (differs)6Not published
Environment variables it asks forNot publishedNot published
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/forestrie/mcp-verify
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)not checked yetno 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.

Verify SCITT receipts from Forestrie transparency logs, offline

In its own words, on Official MCP Registry:

Verify a SCITT receipt under a trust root you hold — offline, no backend, no key, no network

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

Verify SCITT receipts from Forestrie transparency logs, offline As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio verify -- npx -y @forestrie/mcp-verify

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

Tools each declares

The marketplaces of Verify SCITT receipts from Forestrie transparency logs, offline publish no list of tools, so we do not compare tools.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: OpenZeppelin Stellar Contracts · What it can do: Verify SCITT receipts from Forestrie transparency logs, offline · 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