Exit1 Uptime Monitoring vs SolidPing
Exit1 Uptime Monitoring is an MCP server published by exit1.dev. Marketplaces we read that list it: 1 (Official MCP Registry). SolidPing is an MCP server published by fclairamb. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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 |  SolidPing |
|---|---|---|
| Official MCP Registry | Listed Version: 0.4.0 Downloads/month (npm): 281 Downloads/week (npm): 175 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.38.5 Forks (GitHub): 2 Stars (GitHub): 19 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 | Exit1 Uptime Monitoring | SolidPing |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 19 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 2 (better) |
| Last release (differs) | 2026-10-12 (worse) | 2026-10-14 (better) |
| Where it runs (differs) | Remote server (app.exit1.dev/mcp/v1) | Remote server (solidping.io/api/v1/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/mopra/exit1.dev.mcp | github.com/fclairamb/solidping |
| Changes in the last 7 days | 3 | 3 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | Answered with HTTP 302 (36 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
Exit1 Uptime Monitoring
Set up uptime monitoring from your editor: create checks, alerts, and query uptime. Can sign you up.
SolidPing
Self-hostable uptime monitoring: create checks, read incidents, manage status pages.
How to run each
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)
SolidPing As a remote MCP server
claude mcp add --transport http solidping https://solidping.io/api/v1/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only SolidPing has a remote endpoint we check. How we check endpoints
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 SolidPing publish no settings it asks for, so we do not compare settings.
What it can do: Exit1 Uptime Monitoring · What it can do: SolidPing · Compare two other plugins
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.