Suzieq vs Exit1 Uptime Monitoring
Suzieq is an MCP server published by PovedaAqui. Marketplaces we read that list it: 1 (Docker MCP Catalog). Exit1 Uptime Monitoring is an MCP server published by exit1.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
| Marketplace |   Suzieq |   Exit1 Uptime Monitoring |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:ea9f7d06053d Forks (GitHub): 1 Pulls (Docker Hub): 33 787 Stars (Docker Hub): 1 Stars (GitHub): 4 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.4.0 Downloads/month (npm): 425 Downloads/week (npm): 182 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
| Fact | Suzieq | Exit1 Uptime Monitoring |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 4 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 33 787 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-12 |
| Where it runs (differs) | On your machine (mcp/suzieq-mcp) | Remote server (app.exit1.dev/mcp/v1) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 2 | Not published |
| Environment variables it asks for | 2, secrets among them: 1 | 2, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/povedaaqui/suzieq-mcp | github.com/mopra/exit1.dev.mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 days 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
Suzieq
MCP Server to interact with a SuzieQ network observability instance via its REST API.
Exit1 Uptime Monitoring
Set up uptime monitoring from your editor: create checks, alerts, and query uptime. Can sign you up.
How to run each
Suzieq As a local MCP server: Docker image
claude mcp add --env "SUZIEQ_API_KEY=<YOUR_SUZIEQ_API_KEY>" --transport stdio suzieq -- docker run -i --rm -e SUZIEQ_API_KEY mcp/suzieq-mcpRequires: SUZIEQ_API_KEY (secret)
Exit1 Uptime Monitoring As a remote MCP server
claude mcp add --transport http exit1-mcp https://app.exit1.dev/mcp/v1Requires: EXIT1_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Exit1 Uptime Monitoring has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Exit1 Uptime Monitoring publish no list of tools, so we do not compare tools.
Settings each asks for
Only Suzieq asks for
SUZIEQ_API_ENDPOINTSUZIEQ_API_KEY (secret)
Only Exit1 Uptime Monitoring asks for
EXIT1_API_KEY (secret)EXIT1_API_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Suzieq · What it can do: Exit1 Uptime Monitoring · 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.