SolidPing vs io.github.mrfentmen/uptimerobot-mcp
SolidPing is an MCP server published by fclairamb. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.mrfentmen/uptimerobot-mcp is an MCP server published by mrfentmen. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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 |  SolidPing | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.40.1 Forks (GitHub): 2 Stars (GitHub): 22 Not marked · First seen |
Listed Version: 1.0.0 Downloads/month (npm): 647 Downloads/week (npm): 50 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 | SolidPing | io.github.mrfentmen/uptimerobot-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 22 | No figure on GitHub |
| Forks (GitHub) (differs) | 2 | No figure on GitHub |
| Last release (differs) | 2026-10-19 | Not published |
| Where it runs (differs) | Remote server (solidping.io/api/v1/mcp) | On your machine (uptimerobot-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/fclairamb/solidping | github.com/mrfentmen/premium-mcps |
| Changes in the last 7 days (differs) | 6 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Answered with HTTP 302 (18 h ago) | no remote endpoint we check |
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
SolidPing
Self-hostable uptime monitoring: create checks, read incidents, manage status pages.
io.github.mrfentmen/uptimerobot-mcp
Uptime, port, TLS and DNS checks for any site - no API key.
How to run each
SolidPing As a remote MCP server
claude mcp add --transport http solidping https://solidping.io/api/v1/mcpio.github.mrfentmen/uptimerobot-mcp As a local MCP server: npm package
claude mcp add --transport stdio uptimerobot-mcp -- npx -y uptimerobot-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: SolidPing · What it can do: io.github.mrfentmen/uptimerobot-mcp · 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.