UptimeRobot vs io.github.4DA-Systems/4da-mcp-server
UptimeRobot is an MCP server published by uptimerobot.com. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). io.github.4DA-Systems/4da-mcp-server is an MCP server published by 4DA-Systems. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). 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 |   UptimeRobot |  io.github.4DA-Systems/4da-mcp-server |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 24 Not marked · First seen |
Listed Version: 6.2.4 Downloads/month (npm): 2 241 Downloads/week (npm): 156 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 6.2.4 Downloads/month (npm): 2 241 Downloads/week (npm): 156 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 | UptimeRobot | io.github.4DA-Systems/4da-mcp-server |
|---|---|---|
| Marketplaces that list it | 2 | 2 |
| Stars (GitHub) (differs) | 24 (better) | 2 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-12 |
| Where it runs (differs) | Remote server (mcp.uptimerobot.com/mcp) | On your machine (@4da/mcp-server) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 25 | Not a bundle |
| Licence (differs) | MIT | Apache-2.0 |
| Repository (differs) | github.com/uptimerobot/ai | github.com/4da-systems/4da-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 35 h ago, requires a key | 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
UptimeRobot
Monitor websites, APIs, and servers: create monitors, triage incidents, and query uptime stats.
io.github.4DA-Systems/4da-mcp-server
Upgrade intelligence for AI agents: what an upgrade changes, where it touches your code, CVE scans.
How to run each
UptimeRobot As a remote MCP server
claude mcp add --transport http uptimerobot https://mcp.uptimerobot.com/mcpio.github.4DA-Systems/4da-mcp-server As a local MCP server: npm package
claude mcp add --transport stdio 4da-mcp-server -- npx -y @4da/mcp-serverCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only UptimeRobot 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: UptimeRobot · What it can do: io.github.4DA-Systems/4da-mcp-server · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.