Ext Ops Panel
Open dashboard
Comparison

Sentry (Archived) vs Verdict QA

Sentry (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). Verdict QA is an MCP server published by ArtJack. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). 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
MarketplaceSentry (Archived)Verdict QA
Docker MCP Catalog Listed
Version: sha256:f38467297a1e
Forks (GitHub): 11 787
Pulls (Docker Hub): 66 865
Stars (Docker Hub): 7
Stars (GitHub): 91 222
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.90.5
Downloads/month (PyPI): 3 838
Downloads/week (PyPI): 250
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

Sentry (Archived) vs Verdict QA
FactSentry (Archived)Verdict QA
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)91 222 (better)2 (worse)
Pulls (Docker Hub) (differs)66 865No figure on Docker Hub
Forks (GitHub) (differs)11 787 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/sentry)On your machine (verdict-qa-mcp)
Transportstdiostdio
Tools it declares (differs)1Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Hooks it runs (differs)Not published6
Parts of the bundle (differs)Not a bundle21
Licence (differs)NOASSERTIONMIT
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/artjack/verdict
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11

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

Sentry (Archived)

In its own words, on Docker MCP Catalog:

A Model Context Protocol server for retrieving and analyzing issues from Sentry.io. This server provides tools to inspect error reports, stacktraces, and other debugging information from your Sentry account.

Verdict QA

In its own words, on Official MCP Registry:

Read-only MCP server over Verdict QA state: verdicts, findings, flaky quarantine, history.

How to run each

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

Claude Code
claude mcp add --env "SENTRY_AUTH_TOKEN=<YOUR_SENTRY_AUTH_TOKEN>" --transport stdio sentry -- docker run -i --rm -e SENTRY_AUTH_TOKEN mcp/sentry

Requires: SENTRY_AUTH_TOKEN (secret)

Verdict QA As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio verdict -- uvx verdict-qa-mcp

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

Tools each declares

The marketplaces of Verdict QA publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Verdict QA publish no settings it asks for, so we do not compare settings.

What it can do: Sentry (Archived) · What it can do: Verdict QA · 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