Ext Ops Panel
Open dashboard
Comparison

GitHub (Archived) vs io.github.mac146/issuewatcher

GitHub (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.mac146/issuewatcher is an MCP server published by mac146. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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
MarketplaceGitHub (Archived)io.github.mac146/issuewatcher
Docker MCP Catalog Listed
Version: sha256:89fd71b6f2dd
Forks (GitHub): 11 931
Pulls (Docker Hub): 157 721
Stars (Docker Hub): 20
Stars (GitHub): 91 873
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.5
Forks (GitHub): 0
Stars (GitHub): 2
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

GitHub (Archived) vs io.github.mac146/issuewatcher
FactGitHub (Archived)io.github.mac146/issuewatcher
Marketplaces that list it11
Stars (GitHub) (differs)91 873 (better)2 (worse)
Pulls (Docker Hub) (differs)157 721No figure on Docker Hub
Forks (GitHub) (differs)11 931 (better)0 (worse)
Last release (differs)Not published2026-11-01
Where it runs (differs)On your machine (mcp/github)On your machine (issuewatcher-mcp)
Transportstdiostdio
Tools it declares (differs)26Not published
Environment variables it asks for (differs)1, secrets among them: 12, secrets among them: 1
Licence (differs)NOASSERTIONNot stated
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/mac146/issuewatcher
Changes in the last 7 days00
First seen (differs)2026-10-112026-11-01

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

GitHub (Archived)

In its own words, on Docker MCP Catalog:

Tools for interacting with the GitHub API, enabling file operations, repository management, search functionality, and more.

io.github.mac146/issuewatcher

In its own words, on Official MCP Registry:

Ranks new GitHub issues for your AI assistant: what to pick up, what may break your projects.

How to run each

GitHub (Archived) As a local MCP server: Docker image

Claude Code
claude mcp add --env "GITHUB_PERSONAL_ACCESS_TOKEN=<YOUR_GITHUB_PERSONAL_ACCESS_TOKEN>" --transport stdio github -- docker run -i --rm -e GITHUB_PERSONAL_ACCESS_TOKEN mcp/github

Requires: GITHUB_PERSONAL_ACCESS_TOKEN (secret)

io.github.mac146/issuewatcher As a local MCP server: npm package

Claude Code
claude mcp add --env "GITHUB_TOKEN=<YOUR_GITHUB_TOKEN>" --transport stdio issuewatcher -- npx -y issuewatcher-mcp

Requires: GITHUB_TOKEN (secret)

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

Tools each declares

The marketplaces of io.github.mac146/issuewatcher publish no list of tools, so we do not compare tools.

Settings each asks for

Only GitHub (Archived) asks for

  • GITHUB_PERSONAL_ACCESS_TOKEN (secret)

Only io.github.mac146/issuewatcher asks for

  • GITHUB_TOKEN (secret)
  • SCORING_MODE

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: GitHub (Archived) · What it can do: io.github.mac146/issuewatcher · 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. 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