Ext Ops Panel
Open dashboard
Comparison

Git (Reference) vs pr-status

Git (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). pr-status is a plugin bundle for AI coding tools published by fcsouza. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-21. 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
MarketplaceGit (Reference)pr-status
Docker MCP Catalog Listed
Version: sha256:ad6af958e794
Forks (GitHub): 11 830
Pulls (Docker Hub): 175 506
Stars (Docker Hub): 30
Stars (GitHub): 91 419
Not marked · First seen
Not listed
Community marketplace fcsouza/agent-skills Not listed Listed
Version: 0.1.0
Forks (GitHub): 1
Stars (GitHub): 21
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

Git (Reference) vs pr-status
FactGit (Reference)pr-status
Marketplaces that list it11
Stars (GitHub) (differs)91 419 (better)21 (worse)
Pulls (Docker Hub) (differs)175 506No figure on Docker Hub
Forks (GitHub) (differs)11 830 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/git)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)12Not published
Environment variables it asks forNot publishedNot published
Licence (differs)NOASSERTIONGPL-3.0
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/fcsouza/agent-skills
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-19

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

Git (Reference)

In its own words, on Docker MCP Catalog:

Git repository interaction and automation.

pr-status

In its own words, on Community GitHub marketplaces:

A band above the prompt with the pull request of the current branch: CI checks passed, failed and running, and the review decision. Reads gh, refreshes every minute and after each turn.

How to run each

Git (Reference) As a local MCP server: Docker image

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

pr-status As a Claude Code plugin

Claude Code
/plugin marketplace add fcsouza/agent-skills
/plugin install pr-status@fcsouza-agent-skills

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

Tools each declares

The marketplaces of pr-status 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: Git (Reference) · What it can do: pr-status · 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.

Where the data comes from: how the catalog is built