Ext Ops Panel
Open dashboard
Comparison

OpenZeppelin Stylus Contracts vs fireblocks-webhooks

OpenZeppelin Stylus Contracts is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). fireblocks-webhooks is a plugin bundle for AI coding tools published by Hookdeck. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-21. 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 Contractsfireblocks-webhooks
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Community marketplace hookdeck/webhook-skills Not listed Listed
Version: not stated
Forks (GitHub): 16
Stars (GitHub): 92
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 fireblocks-webhooks
FactOpenZeppelin Stylus Contractsfireblocks-webhooks
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub92
Forks (GitHub) (differs)No figure on GitHub16
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
Licence (differs)Apache-2.0MIT
Repository (differs)Not statedgithub.com/hookdeck/webhook-skills
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-21
Endpoint at the last check (differs)Responded 2 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.

fireblocks-webhooks

In its own words, on Community GitHub marketplaces:

Receive and verify Fireblocks webhooks. Use when setting up Fireblocks webhook handlers, debugging Fireblocks-Webhook-Signature verification (detached JWS / RS512 / JWKS), or handling digital-asset events like transaction.created, transaction.status.updated, or transaction.approval_status.updated.

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

fireblocks-webhooks As a Claude Code plugin

Claude Code
/plugin marketplace add hookdeck/webhook-skills
/plugin install fireblocks-webhooks@webhook-skills

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 fireblocks-webhooks 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: fireblocks-webhooks · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. 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