Ext Ops Panel
Open dashboard
Comparison

upgrade-agent vs io.github.theluckystrike/change-order

upgrade-agent is a plugin bundle for AI coding tools published by microsoft. Marketplaces we read that list it: 1 (Copilot CLI: github/awesome-copilot). io.github.theluckystrike/change-order is an MCP server published by theluckystrike. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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
Marketplaceupgrade-agentio.github.theluckystrike/change-order
Copilot CLI: github/awesome-copilot Listed
Version: 1.1.685
Forks (GitHub): 9
Stars (GitHub): 41
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.22.6
Forks (GitHub): 0
Stars (GitHub): 1
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

upgrade-agent vs io.github.theluckystrike/change-order
Factupgrade-agentio.github.theluckystrike/change-order
Marketplaces that list it11
Stars (GitHub) (differs)41 (better)1 (worse)
Forks (GitHub) (differs)9 (better)0 (worse)
Last release (differs)2026-10-14 (worse)2026-10-14 (better)
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedStreamable HTTP, stdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/microsoft/upgrade-agent-pluginsgithub.com/theluckystrike/mcp-servers
Changes in the last 7 days (differs)212
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 11 h ago

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

upgrade-agent

In its own words, on Copilot CLI: github/awesome-copilot:

AI-powered upgrade assistant for upgrading and migrating applications. Helps modernize legacy code and upgrade .NET applications to current frameworks.

io.github.theluckystrike/change-order

In its own words, on Official MCP Registry:

Change orders against a quote or work order: deltas, approval, running contract value.

How to run each

upgrade-agent

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

io.github.theluckystrike/change-order As a remote MCP server

Claude Code
claude mcp add --transport http change-order https://mcp.zovo.one/mcp/change-order --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: MCP_LICENSE_KEY (secret), Authorization header

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

Only io.github.theluckystrike/change-order 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

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

What it can do: upgrade-agent · What it can do: io.github.theluckystrike/change-order · Compare two other plugins

Data comes from the public marketplace file https://github.com/github/awesome-copilot/blob/HEAD/.github/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