Ext Ops Panel
Open dashboard
Comparison

import-optimizer vs CleanCode AI

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

import-optimizer is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. CleanCode AI is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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
Marketplaceimport-optimizerCleanCode AI
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.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

import-optimizer vs CleanCode AI
Factimport-optimizerno longer listed · CleanCode AI
Marketplaces that list it (differs)01
Stars (GitHub) (differs)3No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@barnburner121/plugin-hub-mcp)Remote server (cleancode-ai-mcp.vercel.app/api/mcp)
Transport (differs)Not statedSSE
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/barnburner121/claude-plugin-marketplaceNot stated
Changes in the last 7 days00
First seen (differs)2026-10-142026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-24

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 import-optimizer

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

  • import-organizer

    Sort and organize import statements automatically

    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

  • code-refactoring

    Code cleanup, refactoring automation, and technical debt management with context restoration

    by Seth Hobson · 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

  • codebase-cleanup

    Technical debt reduction, dependency updates, and code refactoring automation

    by Seth Hobson · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes a similar job

Its card, with similar plugins by marketplace

What each says it does

import-optimizer

In its own words, on Community GitHub marketplaces:

Clean up and organize imports, remove unused

CleanCode AI

In its own words, on Official MCP Registry:

Automated codebase refactoring and type safety validator.

How to run each

import-optimizer

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

CleanCode AI As a remote MCP server

Claude Code
claude mcp add --transport sse cleancode-ai https://cleancode-ai-mcp.vercel.app/api/mcp --header "payment-signature: <YOUR_PAYMENT_SIGNATURE>"

Requires: payment-signature header

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

Only CleanCode AI 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: import-optimizer · What it can do: CleanCode AI · 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. 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