Ext Ops Panel
Open dashboard
Comparison

coding-standards-interview vs Python Code Reviewer

coding-standards-interview is a plugin bundle for AI coding tools published by likeahuman-ai. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Python Code Reviewer is an MCP server published by .duckdns.org. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
Marketplacecoding-standards-interviewPython Code Reviewer
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.27.1
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

coding-standards-interview vs Python Code Reviewer
Factcoding-standards-interviewPython Code Reviewer
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 bundleRemote server (.duckdns.org/mcp/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)4Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/likeahuman-ai/coding-standardsNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-15

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

coding-standards-interview

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

Interviews you about your coding preferences, analyzes your actual codebase, and generates personalized coding standards that Claude Code enforces automatically. Includes a pre-commit hook, on-demand lint audits, and folder restructuring — all tailored to your detected stack. Supports 25+ frameworks across TypeScript, Python, Go, Rust, Ruby, PHP, Java, Kotlin, C#, Elixir, and more.

Python Code Reviewer

In its own words, on Official MCP Registry:

Security + bug + perf + refactor audit for Python. Returns 0-10 score + MD report.

How to run each

coding-standards-interview As a Claude Code plugin

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

Python Code Reviewer As a remote MCP server

Claude Code
claude mcp add --transport http python-code-reviewer https://.duckdns.org/mcp/mcp

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

Only Python Code Reviewer 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: coding-standards-interview · What it can do: Python Code Reviewer · 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