Amazon CloudWatch Application Signals vs OneUptime
Amazon CloudWatch Application Signals is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). OneUptime is a plugin bundle for AI coding tools published by OneUptime. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-11-14. 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 |  Amazon CloudWatch Application Signals |  OneUptime |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:873bf1023b30 Forks (GitHub): 1 870 Pulls (Docker Hub): 14 649 Stars (Docker Hub): 1 Stars (GitHub): 9 913 Not marked · First seen |
Not listed |
| Community marketplace using-system/otelyssey | Not listed | Listed Version: 14.0.103 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 | Amazon CloudWatch Application Signals | OneUptime |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 913 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 14 649 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 870 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-11-11 |
| Where it runs (differs) | On your machine (mcp/cloudwatch-appsignals-mcp-server) | Remote server (oneuptime.com/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 13 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 0 | Not published |
| Parts of the bundle (differs) | Not a bundle | 5 |
| Licence | Apache-2.0 | Apache-2.0 |
| Repository (differs) | github.com/awslabs/mcp | github.com/oneuptime/oneuptime-agent-plugin |
| Changes in the last 7 days (differs) | 0 | 8 |
| First seen (differs) | 2026-10-11 | 2026-11-09 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 12 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
Amazon CloudWatch Application Signals
Application performance monitoring and insights.
OneUptime
Work with your OneUptime project from your coding agent: investigate and respond to incidents and alerts, check monitors and status pages, and query logs, metrics and traces.
How to run each
Amazon CloudWatch Application Signals As a local MCP server: Docker image
claude mcp add --transport stdio awslabs-cloudwatch-appsignals -- docker run -i --rm mcp/cloudwatch-appsignals-mcp-serverOneUptime As a Claude Code plugin
/plugin marketplace add using-system/otelyssey
/plugin install oneuptime@otelysseyCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only OneUptime has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of OneUptime publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of OneUptime publish no settings it asks for, so we do not compare settings.
What it can do: Amazon CloudWatch Application Signals · What it can do: OneUptime · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.