OpenZeppelin Stylus Contracts vs PayPerScreen
OpenZeppelin Stylus Contracts is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). PayPerScreen is an MCP server published by TonytheTiger22. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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 Stylus Contracts |  PayPerScreen |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.1 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
| Fact | OpenZeppelin Stylus Contracts | PayPerScreen |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | Not published | 2026-10-14 |
| Where it runs (differs) | Remote server (mcp.openzeppelin.com/contracts/stylus/mcp) | On your machine (payperscreen-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares (differs) | 3 | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | Not stated | github.com/tonythetiger22/payperscreen |
| Changes in the last 7 days (differs) | 0 | 3 |
| First seen (differs) | 2026-10-11 | 2026-10-14 |
| Endpoint at the last check (differs) | Responded 31 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 Stylus Contracts
Access to OpenZeppelin Stylus Contracts.
PayPerScreen
Sanctions, crypto wallet, email and IP screening for agents. Pay per check in USDC via x402.
How to run each
OpenZeppelin Stylus Contracts As a remote MCP server
claude mcp add --transport http openzeppelin-stylus https://mcp.openzeppelin.com/contracts/stylus/mcpPayPerScreen As a local MCP server: npm package
claude mcp add --env "PAYPERSCREEN_PRIVATE_KEY=<YOUR_PAYPERSCREEN_PRIVATE_KEY>" --transport stdio payperscreen -- npx -y payperscreen-mcpRequires: PAYPERSCREEN_PRIVATE_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only OpenZeppelin Stylus Contracts has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of PayPerScreen publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of OpenZeppelin Stylus Contracts publish no settings it asks for, so we do not compare settings.
What it can do: OpenZeppelin Stylus Contracts · What it can do: PayPerScreen · 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.