upgrade-agent vs APCS PyPI Package Verification
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). APCS PyPI Package Verification is an MCP server published by ligafew. 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
| Marketplace | ||
|---|---|---|
| Copilot CLI: github/awesome-copilot | Listed Version: 1.1.685 Forks (GitHub): 10 Stars (GitHub): 41 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed, marked deprecated 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
| Fact | upgrade-agent | APCS PyPI Package Verification |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 41 | No figure on GitHub |
| Forks (GitHub) (differs) | 10 | No figure on GitHub |
| Last release (differs) | 2026-10-14 | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (apcs-public-mcp-gateway.itsnotevenbutter03.workers.dev/mcp/python-package-verification) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/microsoft/upgrade-agent-plugins | Not stated |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-17 |
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
AI-powered upgrade assistant for upgrading and migrating applications. Helps modernize legacy code and upgrade .NET applications to current frameworks.
APCS PyPI Package Verification
Fresh PyPI install/import evidence on Linux x86_64 / CPython 3.13.
How to run each
upgrade-agent
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
APCS PyPI Package Verification As a remote MCP server
claude mcp add --transport http apcs-pypi-package-verification https://apcs-public-mcp-gateway.itsnotevenbutter03.workers.dev/mcp/python-package-verification
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only APCS PyPI Package Verification 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: upgrade-agent · What it can do: APCS PyPI Package Verification · 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.