GitMCP vs legacy-modernizer
legacy-modernizer is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
GitMCP is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). legacy-modernizer is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. As of our marketplace pass on 2026-10-19. 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
| Marketplace |  GitMCP | |
|---|---|---|
| Docker MCP Catalog | Listed Version: not stated No figure published Not marked · First seen |
Not listed |
| Community marketplace barnburner121/claude-plugin-marketplace | Not listed | Removed on 2026-10-18 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 3 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
| Fact | GitMCP | legacy-modernizerno longer listed · |
|---|---|---|
| Marketplaces that list it (differs) | 1 | 0 |
| Stars (GitHub) (differs) | No figure on GitHub | 3 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (gitmcp.io/docs) | On your machine (@barnburner121/plugin-hub-mcp) |
| Transport (differs) | Streamable HTTP | Not stated |
| Tools it declares (differs) | 5 | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | Not a bundle | 2 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | Not stated | github.com/barnburner121/claude-plugin-marketplace |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-11 | 2026-10-14 |
| Endpoint at the last check (differs) | Responded 4 days ago | no remote endpoint we check |
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 legacy-modernizer
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Refactor code following best practices and design patterns
-
Plugin description Code quality review plugin based on Frontend Fundamentals 4 principles (readability, predictability, cohesion, coupling). Supports React and Angular with…
-
Legacy modernization patterns and spec mining of legacy systems
-
Visualize and guide the GitHub Copilot Modernize CLI Assess, Plan, and Execute workflow for .NET, Java, and C++ application repositories.
-
Keep your coding agent up to date with the latest web best practices
-
AI-powered upgrade assistant for upgrading and migrating applications. Helps modernize legacy code and upgrade .NET applications to current frameworks.
What each says it does
GitMCP
Tools for interacting with Git repositories.
legacy-modernizer
Identify legacy patterns and suggest modern replacements
How to run each
GitMCP As a remote MCP server
claude mcp add --transport http gitmcp https://gitmcp.io/docslegacy-modernizer
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only GitMCP has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of legacy-modernizer publish no list of tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: GitMCP · What it can do: legacy-modernizer · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.