Effect vs OpenZeppelin Solidity Contracts
Effect is an MCP server published by tim-smart. Marketplaces we read that list it: 1 (Docker MCP Catalog). OpenZeppelin Solidity Contracts is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). As of our marketplace pass on 2026-10-12. 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 | ||
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:a0e077abc890 Forks (GitHub): 13 Pulls (Docker Hub): 12 837 Stars (Docker Hub): 0 Stars (GitHub): 239 Not marked · First seen |
Listed Version: not stated 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
| Fact | Effect | OpenZeppelin Solidity Contracts |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 239 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 12 837 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 13 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/effect-mcp) | Remote server (mcp.openzeppelin.com/contracts/solidity/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 2 | 8 |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Apache-2.0 |
| Repository (differs) | github.com/tim-smart/effect-mcp | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
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
Effect
Tools and resources for writing Effect code in Typescript.
OpenZeppelin Solidity Contracts
Access to OpenZeppelin Solidity Contracts.
How to run each
Effect As a local MCP server: Docker image
claude mcp add --transport stdio effect-mcp -- docker run -i --rm mcp/effect-mcpOpenZeppelin Solidity Contracts
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.
Tools each declares
Only Effect declares
effect_docs_searchget_effect_doc
Only OpenZeppelin Solidity Contracts declares
solidity-accountsolidity-customsolidity-erc1155solidity-erc20solidity-erc721solidity-governorsolidity-rwasolidity-stablecoin
Both declare
None
Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Effect · What it can do: OpenZeppelin Solidity Contracts · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.