uptime-sentinel vs SolidPing
uptime-sentinel is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
uptime-sentinel is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. 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-29. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  SolidPing | |
|---|---|---|
| Community marketplace barnburner121/claude-plugin-marketplace | Removed on 2026-10-18 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.42.0 Forks (GitHub): 2 Stars (GitHub): 26 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 | uptime-sentinelno longer listed · | SolidPing |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 3 | 26 |
| Forks (GitHub) (differs) | 0 | 2 |
| Last release (differs) | Not published | 2026-10-26 |
| Where it runs (differs) | On your machine (@barnburner121/plugin-hub-mcp) | Remote server (solidping.io/api/v1/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/barnburner121/claude-plugin-marketplace | github.com/fclairamb/solidping |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 302 (3 days ago) |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of uptime-sentinel
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Every Better Stack Uptime feature, plus an offline SQLite mirror and cross-resource fleet analytics
-
Use this agent when monitoring system health, optimizing performance, managing scaling, or ensuring infrastructure reliability. This agent excels at keeping studio applications…
-
Set up uptime monitoring from your editor: create checks, alerts, and query uptime. Can sign you up.
-
Monitor websites, APIs, and servers: create monitors, triage incidents, and query uptime stats.
-
mcp com.uptimemonitoring/mcp
Agent-native uptime monitoring. Create, inspect, and assert monitor health. Free 50-monitor tier.
-
Uptime, page speed, app errors and user-flow runs for your sites, plus fix tasks for coding agents.
What each says it does
uptime-sentinel
Create health check endpoints, set up uptime monitoring, generate status pages, and create incident runbooks
SolidPing
Self-hostable uptime monitoring: create checks, read incidents, manage status pages.
How to run each
uptime-sentinel
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
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
Neither one's marketplaces publish the settings it asks for.
What it can do: uptime-sentinel · What it can do: SolidPing · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.