AWS CloudTrail vs Sessy — Amazon SES observability
AWS CloudTrail is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). Sessy — Amazon SES observability is an MCP server published by marckohlbrugge. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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 |  AWS CloudTrail |  Sessy — Amazon SES observability |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:7952825f42e5 Forks (GitHub): 1 855 Pulls (Docker Hub): 16 348 Stars (Docker Hub): 0 Stars (GitHub): 9 889 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 44 Stars (GitHub): 945 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 | AWS CloudTrail | Sessy — Amazon SES observability |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 889 (better) | 945 (worse) |
| Pulls (Docker Hub) (differs) | 16 348 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 855 (better) | 44 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/cloudtrail-mcp-server) | Remote server (api.sessy.do/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 5 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/awslabs/mcp | github.com/marckohlbrugge/sessy |
| 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 | Status out of date: last check 39 h ago returned HTTP 302 |
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
AWS CloudTrail
AWS CloudTrail audit logging and monitoring.
Sessy — Amazon SES observability
Read-only Amazon SES observability: search events, inspect bounces, pull delivery stats.
How to run each
AWS CloudTrail As a local MCP server: Docker image
claude mcp add --transport stdio awslabs-cloudtrail -- docker run -i --rm mcp/cloudtrail-mcp-serverSessy — Amazon SES observability As a remote MCP server
claude mcp add --transport http sessy https://api.sessy.do/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Sessy — Amazon SES observability has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Sessy — Amazon SES observability publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Sessy — Amazon SES observability publish no settings it asks for, so we do not compare settings.
What it can do: AWS CloudTrail · What it can do: Sessy — Amazon SES observability · 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.