Amazon CloudWatch Application Signals vs BetterStack Status Page Scraper & API Tool
Amazon CloudWatch Application Signals is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). BetterStack Status Page Scraper & API Tool is an MCP server published by ranovam.com. Marketplaces we read that list it: 1 (Official MCP Registry). 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 |  Amazon CloudWatch Application Signals |  BetterStack Status Page Scraper & API Tool |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:873bf1023b30 Forks (GitHub): 1 827 Pulls (Docker Hub): 14 288 Stars (Docker Hub): 1 Stars (GitHub): 9 830 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.1 No figure published 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 | BetterStack Status Page Scraper & API Tool |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 830 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 14 288 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 827 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/cloudwatch-appsignals-mcp-server) | Remote server (mcp.apify.com) |
| 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 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/awslabs/mcp | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-24 |
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.
BetterStack Status Page Scraper & API Tool
Get any company's BetterStack (Better Uptime) status page as clean JSON — components, incidents…
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-serverBetterStack Status Page Scraper & API Tool
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only BetterStack Status Page Scraper & API Tool has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of BetterStack Status Page Scraper & API Tool publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of BetterStack Status Page Scraper & API Tool publish no settings it asks for, so we do not compare settings.
What it can do: Amazon CloudWatch Application Signals · What it can do: BetterStack Status Page Scraper & API Tool · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.