Ext Ops Panel
Open dashboard
Comparison

vibeguard vs com.edgethirteen.www/vercelpycheck

vibeguard is a plugin bundle for AI coding tools published by geraldang702. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). com.edgethirteen.www/vercelpycheck is an MCP server published by www.edgethirteen.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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
Marketplacevibeguardcom.edgethirteen.www/vercelpycheck
Claude Code: claude-plugins-community Listed
Version: 2.0.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
No figure published
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

vibeguard vs com.edgethirteen.www/vercelpycheck
Factvibeguardcom.edgethirteen.www/vercelpycheck
Marketplaces that list it11
Stars (GitHub) (differs)0No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (www.edgethirteen.com/api/mcp/vercelpycheck)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)4Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/geraldang702/vibeguardNot stated
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)no remote endpoint we checkAnswered with HTTP 404 (5 days ago)

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

vibeguard

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

Security auditor and hardener for vibe-coded projects. 170+ vulnerability checks across 24 categories including injection, XSS, auth bypass, IDOR, Supabase RLS, prompt injection, exposed secrets, rate limiting, CORS, and auth provider misconfigs. Three commands: /vibeguard:audit (scan and report), /vibeguard:fix (patch findings), /vibeguard:harden (add security infrastructure). Includes a pre-commit hook that blocks git commits containing hardcoded secrets.

com.edgethirteen.www/vercelpycheck

In its own words, on Official MCP Registry:

Scan a public GitHub repo for known Vercel Python-runtime deploy footguns.

How to run each

vibeguard As a Claude Code plugin

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

com.edgethirteen.www/vercelpycheck As a remote MCP server

Claude Code
claude mcp add --transport http vercelpycheck https://www.edgethirteen.com/api/mcp/vercelpycheck

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

Only com.edgethirteen.www/vercelpycheck has a remote endpoint we check. How we check endpoints

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: vibeguard · What it can do: com.edgethirteen.www/vercelpycheck · 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