OpenZeppelin Solidity Contracts vs PineForge — offline PineScript v6 backtest MCP
OpenZeppelin Solidity Contracts is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). PineForge — offline PineScript v6 backtest MCP is an MCP server published by pineforge-4pass. 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
| Marketplace |  PineForge — offline PineScript v6 backtest MCP | |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.9.18 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 | PineForge — offline PineScript v6 backtest MCP |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| 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) | On your machine (ghcr.io/pineforge-4pass/pineforge-codegen-mcp:v0.9.18) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares (differs) | 8 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | Not stated | github.com/pineforge-4pass/pineforge-codegen-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | no 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 Solidity Contracts
Access to OpenZeppelin Solidity Contracts.
PineForge — offline PineScript v6 backtest MCP
Offline PineScript v6 → C++ backtests at deterministic TradingView parity, run locally via MCP.
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/mcpPineForge — offline PineScript v6 backtest MCP As a local MCP server: Docker image
claude mcp add --transport stdio pineforge-codegen-mcp -- docker run -i --rm ghcr.io/pineforge-4pass/pineforge-codegen-mcp:v0.9.18Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of PineForge — offline PineScript v6 backtest MCP 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: PineForge — offline PineScript v6 backtest MCP · 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.