mcpbeat

Sessy — Amazon SES observability MCP Server

io.github.marckohlbrugge/sessy
answering

Sessy — Amazon SES observability is answering right now. Last checked 11 min ago. Last commit 1 Aug 2026.

Read-only Amazon SES observability: search events, inspect bounces, pull delivery stats.

Uptime history 41 hours of history
41 hours agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
502 ms
Response time
average over 24h
909
Stars
last commit 1 Aug 2026

Connect this server

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

run in your terminal
claude mcp add sessy --transport http https://api.sessy.do/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "sessy": {
      "url": "https://api.sessy.do/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.sessy]
url = "https://api.sessy.do/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "sessy": {
      "url": "https://api.sessy.do/mcp"
    }
  }
}
.vscode/mcp.json
{
  "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 or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://api.sessy.do/mcp streamable-http needs key 417 ms 11 min ago

Sessy — Amazon SES observability — questions

Answers built from our own checks of this server.

Why is there no tool list for Sessy — Amazon SES observability?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Sessy — Amazon SES observability working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 502 ms. The bar chart above shows every period we have measured.
How do I connect Sessy — Amazon SES observability?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key or an OAuth login: it refuses anonymous clients.
Does Sessy — Amazon SES observability need an API key?
Yes. Every time we knock, Sessy — Amazon SES observability answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Sessy — Amazon SES observability?
It answers our handshake in 502 ms on average, which is faster than 22% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Sessy — Amazon SES observability open source?
Yes — it is published under the NOASSERTION licence, written in Ruby and 909 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.