Ext Ops Panel
Open dashboard
Comparison

raven-guard vs LeakRank Guard

raven-guard is a plugin bundle for AI coding tools published by giggsoinc. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). LeakRank Guard is an MCP server published by ProtoTeemo. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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
Marketplaceraven-guardLeakRank Guard
Claude Code: claude-plugins-community Listed
Version: 2.9.1
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.3
Downloads/month (npm): 190
Downloads/week (npm): 84
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

raven-guard vs LeakRank Guard
Factraven-guardLeakRank Guard
Marketplaces that list it11
Stars (GitHub) (differs)1No 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 (leakrank-guard)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)8Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/giggsoinc/raven-guardNot stated
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

raven-guard

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

Production protection layer for Claude Code. Hard-blocks destructive operations (force push, DROP TABLE, TRUNCATE, Terraform state edits). P1/P2/P3 incident SLAs with escalation ladder. Requires raven.

LeakRank Guard

In its own words, on Official MCP Registry:

Scans code changes for leaked secrets and insecure config, with actionable fixes for AI agents.

How to run each

raven-guard As a Claude Code plugin

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

LeakRank Guard As a local MCP server: npm package

Claude Code
claude mcp add --env "LEAKRANK_API_KEY=<YOUR_LEAKRANK_API_KEY>" --transport stdio leakrank-guard -- npx -y leakrank-guard mcp

Requires: LEAKRANK_API_KEY (secret)

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 raven-guard publish no settings it asks for, so we do not compare settings.

What it can do: raven-guard · What it can do: LeakRank Guard · 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