Agent Compatibility vs Exit1 Uptime Monitoring
Agent Compatibility is a plugin bundle for AI coding tools published by Cursor. Marketplaces we read that list it: 1 (Cursor: cursor/plugins). 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-13. 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 |  Exit1 Uptime Monitoring | |
|---|---|---|
| Cursor: cursor/plugins | Listed Version: 1.0.0 Forks (GitHub): 1 066 Stars (GitHub): 11 026 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.4.0 Downloads/month (npm): 281 Downloads/week (npm): 175 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 | Agent Compatibility | Exit1 Uptime Monitoring |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 11 026 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 1 066 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-12 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (app.exit1.dev/mcp/v1) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Parts of the bundle (differs) | 5 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/cursor/plugins | github.com/mopra/exit1.dev.mcp |
| Changes in the last 7 days (differs) | 0 | 3 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | not checked yet |
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
Agent Compatibility
CLI-backed repo compatibility scans plus agents that audit startup, validation, and docs against reality.
Exit1 Uptime Monitoring
Set up uptime monitoring from your editor: create checks, alerts, and query uptime. Can sign you up.
How to run each
Agent Compatibility
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
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.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of Agent Compatibility publish no settings it asks for, so we do not compare settings.
What it can do: Agent Compatibility · What it can do: Exit1 Uptime Monitoring · Compare two other plugins
Data comes from the public marketplace file https://github.com/cursor/plugins/blob/HEAD/.cursor-plugin/marketplace.json. 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.