Ext Ops Panel
Open dashboard
Comparison

io.github.GuardBee/owasp-scan vs io.github.lazymac2x/mcpwatch

io.github.GuardBee/owasp-scan is an MCP server published by GuardBee. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.lazymac2x/mcpwatch is an MCP server published by lazymac2x. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
Marketplaceio.github.GuardBee/owasp-scanio.github.lazymac2x/mcpwatch
Official MCP Registry Listed
Version: 0.3.3
Downloads/month (npm): 1 562
Downloads/week (npm): 765
Forks (GitHub): 1
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 0.1.1
Downloads/month (npm): 139
Downloads/week (npm): 13
Forks (GitHub): 0
Stars (GitHub): 0
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

io.github.GuardBee/owasp-scan vs io.github.lazymac2x/mcpwatch
Factio.github.GuardBee/owasp-scanio.github.lazymac2x/mcpwatch
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub) (differs)1 (better)0 (worse)
Last release (differs)2026-10-22Not published
Where it runs (differs)On your machine (@guardbee/mcp-owasp-scan)On your machine (mcpwatch-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/guardbee/guardbee-mcpgithub.com/lazymac2x/mcpwatch
Changes in the last 7 days (differs)40
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

io.github.GuardBee/owasp-scan

In its own words, on Official MCP Registry:

Unified OWASP MCP Top 10 scan — path or live tools/list, A–F grade, SARIF

io.github.lazymac2x/mcpwatch

In its own words, on Official MCP Registry:

Audit MCP servers from inside Claude Code. 10 OWASP checks, A-F grade, live leaderboard.

How to run each

io.github.GuardBee/owasp-scan As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio owasp-scan -- npx -y @guardbee/mcp-owasp-scan

io.github.lazymac2x/mcpwatch As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio mcpwatch -- npx -y mcpwatch-mcp

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: io.github.GuardBee/owasp-scan · What it can do: io.github.lazymac2x/mcpwatch · Compare two other plugins

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