Ext Ops Panel
Open dashboard
Comparison

OpenZeppelin Stylus Contracts vs acuris

OpenZeppelin Stylus Contracts is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). acuris is a plugin bundle for AI coding tools published by Acuris-GmbH. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-23. 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

Where each is published
MarketplaceOpenZeppelin Stylus Contractsacuris
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Not listed Listed
Version: 5fb6ebe
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

OpenZeppelin Stylus Contracts vs acuris
FactOpenZeppelin Stylus Contractsacuris
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.openzeppelin.com/contracts/stylus/mcp)Installs as a plugin bundle
Transport (differs)Streamable HTTPNot stated
Tools it declares (differs)3Not published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle2
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/acuris-gmbh/acuris-agent-context
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 3 days agono 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

In its own words, on Docker MCP Catalog:

Access to OpenZeppelin Stylus Contracts.

acuris

In its own words, on Claude Code: claude-plugins-community:

Two model-invoked skills for the Acuris APIs. `acuris-address` teaches the Acuris Address Validation & Geocoding SDK (`@acuris-geo/av-sdk`) — validate, geocode, reverse, autocomplete — plus React component recipes for Next.js, Centra, commercetools, and SCAYLE storefronts, plus migration recipes from libAddressDoctor (Informatica), Loqate, Experian QAS, Melissa, and Smarty. `acuris-eudi` teaches relying-party integration with the Acuris EUDI Wallet Verifier (OID4VP / SD-JWT VC at eudi.acuris-geo.com), covering session lifecycle, polling, and trust validation across EU 27 member-state TSLs. Each skill auto-activates only when your task mentions its area, so installing both costs almost no context.

How to run each

OpenZeppelin Stylus Contracts As a remote MCP server

Claude Code
claude mcp add --transport http openzeppelin-stylus https://mcp.openzeppelin.com/contracts/stylus/mcp

acuris As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install acuris@claude-community

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 acuris 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 Stylus Contracts · What it can do: acuris · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built