Ext Ops Panel
Open dashboard
Comparison

vibe-coding vs prodlint

vibe-coding is a plugin bundle for AI coding tools published by jordanbeardedmgmt. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). prodlint is an MCP server published by prodlint. 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
Marketplacevibe-codingprodlint
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.10.0
Downloads/month (npm): 154
Downloads/week (npm): 31
Forks (GitHub): 1
Stars (GitHub): 15
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

vibe-coding vs prodlint
Factvibe-codingprodlint
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)15 (better)
Forks (GitHub) (differs)0 (worse)1 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (prodlint-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/jordanbeardedmgmt/vibe-coding-plugingithub.com/prodlint/prodlint
Changes in the last 7 days00
First seen (differs)2026-10-122026-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

vibe-coding

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

Schema-first architecture discipline for AI-assisted development. Enforces tables → RLS → features ordering, generates paste-ready Claude Code prompts, and manages build queue batches. Built from the methodology behind a 511-table production app with 1,016 security policies.

prodlint

In its own words, on Official MCP Registry:

Production readiness for vibe-coded apps. 52 checks for security, reliability, and performance.

How to run each

vibe-coding As a Claude Code plugin

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

prodlint As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio prodlint -- npx -y prodlint-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: vibe-coding · What it can do: prodlint · 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