Ext Ops Panel
Open dashboard
Comparison

Azure vs azure-event-grid-webhooks

Azure is an MCP server published by microsoft. Marketplaces we read that list it: 1 (Docker MCP Catalog). azure-event-grid-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
MarketplaceAzureazure-event-grid-webhooks
Docker MCP Catalog Listed
Version: sha256:f8f4386fa2e8
Forks (GitHub): 658
Stars (GitHub): 3 789
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

Azure vs azure-event-grid-webhooks
FactAzureazure-event-grid-webhooks
Marketplaces that list it11
Stars (GitHub) (differs)3 789 (better)92 (worse)
Forks (GitHub) (differs)658 (better)16 (worse)
Last release (differs)2026-10-21Not published
Where it runs (differs)On your machine (mcr.microsoft.com/azure-sdk/azure-mcp)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)55Not published
Environment variables it asks forNot publishedNot published
LicenceMITMIT
Repository (differs)github.com/microsoft/mcpgithub.com/hookdeck/webhook-skills
Changes in the last 7 days22
First seen (differs)2026-10-112026-10-21

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

Azure

In its own words, on Docker MCP Catalog:

Catalog of official Microsoft MCP (Model Context Protocol) server implementations for AI-powered data access and tool integration.

azure-event-grid-webhooks

In its own words, on Community GitHub marketplaces:

Receive and validate Azure Event Grid webhook deliveries. Use when setting up an Event Grid WebHook event handler, implementing the Microsoft.EventGrid.SubscriptionValidationEvent handshake (echo data.validationCode as validationResponse with HTTP 200), implementing the CloudEvents v1.0 HTTP OPTIONS abuse-protection preflight (WebHook-Request-Origin / WebHook-Allowed-Origin), checking the aeg-subscription-name / aeg-event-type / aeg-delivery-count headers, authenticating deliveries with a static delivery-property header or a Microsoft Entra ID bearer token, parsing Event Grid schema arrays vs CloudEvents objects, or handling events like Microsoft.Storage.BlobCreated. Event Grid does NOT sign the request body — there is no HMAC signature.

How to run each

Azure As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio azure -- docker run -i --rm mcr.microsoft.com/azure-sdk/azure-mcp

azure-event-grid-webhooks As a Claude Code plugin

Claude Code
/plugin marketplace add hookdeck/webhook-skills
/plugin install azure-event-grid-webhooks@webhook-skills

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of azure-event-grid-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: Azure · What it can do: azure-event-grid-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