OpenZeppelin Solidity Contracts vs forge
forge is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑22.
OpenZeppelin Solidity Contracts is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). forge is a plugin bundle for AI coding tools published by Floka AS. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-27. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  OpenZeppelin Solidity Contracts | |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Community marketplace floka-as/floka-marketplace | Not listed | Removed on 2026-10-22 Version: 1.0.0 Forks (GitHub): 1 Stars (GitHub): 7 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
| Fact | OpenZeppelin Solidity Contracts | forgeno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Stars (GitHub) (differs) | No figure on GitHub | 7 |
| Forks (GitHub) (differs) | No figure on GitHub | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.openzeppelin.com/contracts/solidity/mcp) | Installs as a plugin bundle |
| Transport (differs) | Streamable HTTP | Not stated |
| Tools it declares (differs) | 8 | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | Not a bundle | 8 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | Not stated | github.com/floka-as/floka-marketplace |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-18 |
| Endpoint at the last check (differs) | Responded 4 days ago | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of forge
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Full-lifecycle SDLC orchestrator: a 12-stage pipeline (SRS, architecture, spec, plan, build, eval, deploy, monitor, release) driven by specialized agents, persistent cross-session…
-
Adversarial multi-agent pipeline for Claude Code. Generators produce artifacts, discriminators validate them, and adversarial feedback loops drive convergence.
-
Description: Adversarial code hardening for Claude Code. Forge spawns two agents — a Builder and a Breaker — that iterate against each other until the code is unbreakable. The…
-
Autonomous full-stack application factory for AI coding assistants. Clone this repo into your workspace and your AI assistant — Copilot, Claude, Cursor, Codex, or any…
-
Forge-focused skills and MCP configuration for Atlassian Forge: scaffold and deploy apps (forge create, templates, dev spaces), build Teamwork Graph connectors for Rovo…
-
Core development tools including quality pipeline, TDD implementation, code review, and refactoring capabilities
What each says it does
OpenZeppelin Solidity Contracts
Access to OpenZeppelin Solidity Contracts.
forge
Spec-driven autonomous development workflow. /forge:contract writes a thorough spec via code exploration, library research, and gray-area discussion. /forge:auto loops build→evaluate→fix until ACCEPT. Includes /forge:build, /forge:evaluate, /forge:parallel, /forge:pulse, /forge:status. Evidence-before-checkbox discipline and skeptical fresh-context evaluation built in.
How to run each
OpenZeppelin Solidity Contracts As a remote MCP server
claude mcp add --transport http openzeppelin-solidity https://mcp.openzeppelin.com/contracts/solidity/mcpforge
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only OpenZeppelin Solidity Contracts has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of forge 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 Solidity Contracts · What it can do: forge · 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.