Ext Ops Panel
Open dashboard
Comparison

dead-code vs io.github.giancarloerra/socraticode

dead-code is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.

dead-code is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. io.github.giancarloerra/socraticode is an MCP server published by giancarloerra. Marketplaces we read that list it: 3 (Official MCP Registry, Claude Code: claude-plugins-community, Community GitHub marketplaces). As of our marketplace pass on 2026-10-22. 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
Marketplacedead-codeio.github.giancarloerra/socraticode
Community marketplace barnburner121/claude-plugin-marketplace Removed on 2026-10-18
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.16.1
Downloads/month (npm): 19 713
Downloads/week (npm): 2 291
Forks (GitHub): 433
Stars (GitHub): 3 350
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 1.11.0
Forks (GitHub): 433
Stars (GitHub): 3 350
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

dead-code vs io.github.giancarloerra/socraticode
Factdead-codeno longer listed · io.github.giancarloerra/socraticode
Marketplaces that list it (differs)03
Stars (GitHub) (differs)33 350
Forks (GitHub) (differs)0433
Last release (differs)Not published2026-10-16
Where it runs (differs)On your machine (@barnburner121/plugin-hub-mcp)On your machine (socraticode)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published17, secrets among them: 6
Hooks it runs (differs)Not published1
Parts of the bundle (differs)25
Licence (differs)MITAGPL-3.0-only
Repository (differs)github.com/barnburner121/claude-plugin-marketplacegithub.com/giancarloerra/socraticode
Changes in the last 7 days22
First seen (differs)2026-10-142026-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 dead-code

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

  • unused-code-finder

    Find and remove dead code and unused imports

    by DevsForge Community · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • simplify

    Review changed code for reuse, redundancy, and over-engineering, then apply fixes.

    by Fatih C. Akyon · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • performance-optimizer

    Analyze and optimize code performance, identify bottlenecks, and suggest improvements

    by GLINCKER Team · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • code-quality

    Code-quality skills for Claude Code. Currently a read-only dead code sweep: run the project's own static analyzer, triage what it flags against the ways code stays reachable…

    by Dawid Dahl · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • bug-fix

    Analyzes and fixes bugs in your codebase

    by Community · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • deslop

    Detect and remove AI-generated slop with certainty-based findings and safe auto-fixes. AI coding tools leave behind debug `console.log`s, `print` statements, placeholder text…

    by agent-sh · Plugin bundle

    Listed on: Claude Code: claude-plugins-community, Community GitHub marketplaces · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

dead-code

In its own words, on Community GitHub marketplaces:

Find and remove unused code, functions, imports, variables

io.github.giancarloerra/socraticode

In its own words, on Official MCP Registry:

MCP server for enterprise local codebase indexing, semantic search, and code dependency graphs.

How to run each

dead-code

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

io.github.giancarloerra/socraticode As a local MCP server: npm package

Claude Code
claude mcp add --env "GOOGLE_API_KEY=<YOUR_GOOGLE_API_KEY>" --env "LITELLM_API_KEY=<YOUR_LITELLM_API_KEY>" --env "LMSTUDIO_API_KEY=<YOUR_LMSTUDIO_API_KEY>" --env "OLLAMA_API_KEY=<YOUR_OLLAMA_API_KEY>" --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --env "QDRANT_API_KEY=<YOUR_QDRANT_API_KEY>" --transport stdio socraticode -- npx -y socraticode

Requires: GOOGLE_API_KEY (secret), LITELLM_API_KEY (secret), LMSTUDIO_API_KEY (secret), OLLAMA_API_KEY (secret), OPENAI_API_KEY (secret), QDRANT_API_KEY (secret)

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

The marketplaces of dead-code publish no settings it asks for, so we do not compare settings.

What it can do: dead-code · What it can do: io.github.giancarloerra/socraticode · 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. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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