OpenZeppelin Solidity Contracts vs com.mcparmory/alchemy-nft
OpenZeppelin Solidity Contracts is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). com.mcparmory/alchemy-nft is an MCP server published by mcparmory.com. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-25. 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 |  OpenZeppelin Solidity Contracts |  com.mcparmory/alchemy-nft |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.3 Downloads/month (PyPI): 815 Downloads/week (PyPI): 161 Forks (GitHub): 4 Stars (GitHub): 32 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 1.0.3 Downloads/month (PyPI): 815 Downloads/week (PyPI): 161 Forks (GitHub): 4 Stars (GitHub): 32 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 | com.mcparmory/alchemy-nft |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 32 |
| Forks (GitHub) (differs) | No figure on GitHub | 4 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.openzeppelin.com/contracts/solidity/mcp) | On your machine (mcparmory-alchemy-nft) |
| 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 | MIT |
| Repository (differs) | Not stated | github.com/mcparmory/registry |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 36 h ago | 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.
com.mcparmory/alchemy-nft
Retrieve NFT metadata, ownership, and contract details across blockchains
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/mcpcom.mcparmory/alchemy-nft As a local MCP server: PyPI package
claude mcp add --transport stdio alchemy-nft -- uvx mcparmory-alchemy-nftCommands 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 com.mcparmory/alchemy-nft 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: com.mcparmory/alchemy-nft · 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. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.