Ext Ops Panel
Open dashboard
Comparison

Python Refactoring Assistant vs ExactGround

Python Refactoring Assistant is an MCP server published by slamer59. Marketplaces we read that list it: 1 (Docker MCP Catalog). ExactGround is an MCP server published by alidaram99. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-13. 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
MarketplacePython Refactoring AssistantExactGround
Docker MCP Catalog Listed
Version: sha256:4cd4303da424
Forks (GitHub): 6
Pulls (Docker Hub): 36 861
Stars (Docker Hub): 2
Stars (GitHub): 13
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.5
Forks (GitHub): 0
Stars (GitHub): 0
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

Python Refactoring Assistant vs ExactGround
FactPython Refactoring AssistantExactGround
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)13 (better)0 (worse)
Pulls (Docker Hub) (differs)36 861No figure on Docker Hub
Forks (GitHub) (differs)6 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/mcp-python-refactoring)Remote server (dropin-apis--exactground-api.apify.actor/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)9Not published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)Not published2
Parts of the bundle (differs)Not a bundle2
LicenceMITMIT
Repository (differs)github.com/slamer59/mcp-python-refactoringgithub.com/alidaram99/exactground
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 5 h ago, requires a key

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

Python Refactoring Assistant

In its own words, on Docker MCP Catalog:

Educational Python refactoring assistant that provides guided suggestions for AI assistants.

ExactGround

In its own words, on Official MCP Registry:

Check npm/PyPI packages exist and that a function or method exists in an exact package version.

How to run each

Python Refactoring Assistant As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio mcp-python-refactoring -- docker run -i --rm mcp/mcp-python-refactoring

ExactGround As a remote MCP server

Claude Code
claude mcp add --transport http exactground https://dropin-apis--exactground-api.apify.actor/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only ExactGround has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of ExactGround 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: Python Refactoring Assistant · What it can do: ExactGround · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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.

Where the data comes from: how the catalog is built