Ext Ops Panel
Open dashboard
Comparison

Sentry (Archived) vs OneUptime

Sentry (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). OneUptime is a plugin bundle for AI coding tools published by OneUptime. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-11-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)OneUptime
Docker MCP Catalog Listed
Version: sha256:f38467297a1e
Forks (GitHub): 11 961
Pulls (Docker Hub): 67 784
Stars (Docker Hub): 7
Stars (GitHub): 91 970
Not marked · First seen
Not listed
Community marketplace using-system/otelyssey Not listed Listed
Version: 14.0.103
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

Sentry (Archived) vs OneUptime
FactSentry (Archived)OneUptime
Marketplaces that list it11
Stars (GitHub) (differs)91 970 (better)0 (worse)
Pulls (Docker Hub) (differs)67 784No figure on Docker Hub
Forks (GitHub) (differs)11 961 (better)0 (worse)
Last release (differs)Not published2026-11-11
Where it runs (differs)On your machine (mcp/sentry)Remote server (oneuptime.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)1Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Parts of the bundle (differs)Not a bundle5
Licence (differs)NOASSERTIONApache-2.0
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/oneuptime/oneuptime-agent-plugin
Changes in the last 7 days (differs)08
First seen (differs)2026-10-112026-11-09
Endpoint at the last check (differs)no remote endpoint we checkResponded 12 h ago

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.

OneUptime

In its own words, on Community GitHub marketplaces:

Work with your OneUptime project from your coding agent: investigate and respond to incidents and alerts, check monitors and status pages, and query logs, metrics and traces.

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)

OneUptime As a Claude Code plugin

Claude Code
/plugin marketplace add using-system/otelyssey
/plugin install oneuptime@otelyssey

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

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

Tools each declares

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

Settings each asks for

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

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