Ext Ops Panel
Open dashboard
Comparison

drift-guard vs Queue Pilot

drift-guard is a plugin bundle for AI coding tools published by pgomes13. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Queue Pilot is an MCP server published by LarsCowe. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
Marketplacedrift-guardQueue Pilot
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.5.1
Downloads/month (npm): 188
Downloads/week (npm): 38
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

drift-guard vs Queue Pilot
Factdrift-guardQueue Pilot
Marketplaces that list it11
Stars (GitHub) (differs)3No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (queue-pilot)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published8, secrets among them: 4
Licence (differs)MITNot stated
Repository (differs)github.com/pgomes13/drift-guard-enginegithub.com/larscowe/queue-pilot
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

drift-guard

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

Detect breaking and non-breaking API schema changes across OpenAPI, GraphQL, and gRPC

Queue Pilot

In its own words, on Official MCP Registry:

MCP server for RabbitMQ and Kafka message inspection with JSON Schema validation

How to run each

drift-guard As a Claude Code plugin

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

Queue Pilot As a local MCP server: npm package

Claude Code
claude mcp add --env "KAFKA_SASL_PASSWORD=<YOUR_KAFKA_SASL_PASSWORD>" --env "KAFKA_SASL_USERNAME=<YOUR_KAFKA_SASL_USERNAME>" --env "RABBITMQ_PASS=<YOUR_RABBITMQ_PASS>" --env "RABBITMQ_USER=<YOUR_RABBITMQ_USER>" --transport stdio queue-pilot -- npx -y queue-pilot --schemas "<YOUR_SCHEMAS>"

Requires: KAFKA_SASL_PASSWORD (secret), KAFKA_SASL_USERNAME (secret), RABBITMQ_PASS (secret), RABBITMQ_USER (secret), --schemas

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of drift-guard publish no settings it asks for, so we do not compare settings.

What it can do: drift-guard · What it can do: Queue Pilot · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.

Where the data comes from: how the catalog is built