Ext Ops Panel
Open dashboard
Comparison

WARDEN — MCP firewall vs io.github.4hmetuyar/security-proxy

WARDEN — MCP firewall is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.

WARDEN — MCP firewall is a plugin bundle for AI coding tools published by AICOM (alexar76). No marketplace we read lists it any more. io.github.4hmetuyar/security-proxy is an MCP server published by 4hmetuyar. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceWARDEN — MCP firewallio.github.4hmetuyar/security-proxy
Community marketplace alexar76/warden Removed on 2026-10-15
Version: 0.14.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.4.0
Downloads/month (npm): 3 852
Downloads/week (npm): 1 694
Forks (GitHub): 1
Stars (GitHub): 1
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

WARDEN — MCP firewall vs io.github.4hmetuyar/security-proxy
FactWARDEN — MCP firewallno longer listed · io.github.4hmetuyar/security-proxy
Marketplaces that list it (differs)01
Stars (GitHub) (differs)01
Forks (GitHub) (differs)01
Last release (differs)Not published2026-10-16
Where it runs (differs)Installs as a plugin bundleOn your machine (@guardbee/mcp-security-proxy)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)2Not published
Parts of the bundle (differs)3Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/alexar76/wardengithub.com/guardbee/guardbee-mcp
Changes in the last 7 days (differs)48
First seen (differs)2026-10-132026-10-11

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of WARDEN — MCP firewall

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • WARDEN — MCP Security Firewall

    MCP security firewall: stdio wrap proxy or inspection tools; zero runtime dependencies.

    by alexar76 · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • MCP Safety Warden

    MCP proxy adding security scanning, behavioral profiling, risk gating, and safe tool call execution.

    by gautamvarmadatla · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • protect-mcp

    MCP security gateway that wraps any MCP server with per-tool policies, Ed25519-signed decision receipts, and human approval gates. Shadow mode (default) logs every tool call…

    by tomjwxf · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • IntentFence Agent Action Firewall

    Fail-closed action authorization, MCP risk scanning, x402 checks, and signed receipts.

    by razel369 · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • assay io.github.Rul1an/assay

    The firewall for MCP tool calls. Block, audit, replay with evidence bundles.

    by Rul1an · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • MCPower Security Proxy

    Security proxy that automatically wraps MCP servers with real-time monitoring and policy enforcement

    by MCPower-Security · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

WARDEN — MCP firewall

In its own words, on Community GitHub marketplaces:

Vets the MCP servers this project starts before the model sees their tools, and denies calls to blocked ones.

io.github.4hmetuyar/security-proxy

In its own words, on Official MCP Registry:

MCP gateway: many servers, one policy, lethal-trifecta blocking, PII masking, audit log

How to run each

WARDEN — MCP firewall

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

io.github.4hmetuyar/security-proxy As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio security-proxy -- npx -y @guardbee/mcp-security-proxy

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

Neither one's marketplaces publish the settings it asks for.

What it can do: WARDEN — MCP firewall · What it can do: io.github.4hmetuyar/security-proxy · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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