Sessy — Amazon SES observability MCP Server

What the code does

We read the source, 2 h ago · rules 3dff92dd89df

Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.

  # Store uploaded files on the local file system (see config/storage.yml for options).

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

  # Store uploaded files on the local file system (see config/storage.yml for options).

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

claude mcp add sessy --transport http https://api.sessy.do/mcp

{
  "mcpServers": {
    "sessy": {
      "url": "https://api.sessy.do/mcp"
    }
  }
}

[mcp_servers.sessy]
url = "https://api.sessy.do/mcp"

{
  "mcpServers": {
    "sessy": {
      "url": "https://api.sessy.do/mcp"
    }
  }
}

{
  "mcpServers": {
    "sessy": {
      "url": "https://api.sessy.do/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but you need an API key from its owner to call it.

Endpoints