Developer · Remote MCP server
Sessy - Amazon SES observability
Read-only Amazon SES observability: search events, inspect bounces, pull delivery stats.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.marckohlbrugge/sessy- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-07-31
- Updated
- 2026-07-31
- Publisher
- marckohlbrugge (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/marckohlbrugge) · how
- Listed under
- Amazon MCP servers
- Website
- sessy.do/blog/amazon-ses-mcp
- Repository
- github.com/marckohlbrugge/sessy
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.sessy.do/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; a Bearer token is asked for
- Checked on
- 2026-10-05
How to connect Sessy - Amazon SES observability
Sessy - Amazon SES observability is a remote MCP server: there is nothing to install. Its endpoint is https://api.sessy.do/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| ServonautManage AWS, Hetzner, OVH and SSH servers: status, logs, CloudWatch, IP bans, safe command exec. | Local · stdio |
| Seshat MCPStructural code intelligence for AI agents: real call graphs, blast radius, and change history. | Local · stdio |
| Session ForgePersistent memory and session intelligence for AI coding assistants. Zero config. | Local · stdio |
| Session StewardReview and safely clean local Codex and Claude Code sessions. | Local · stdio |
| SetForkRunnable, versioned lists for agents: tools, prompts and lists as resources. Git under the hood. | Remote · HTTPLive check: ✗ no handshake |
| SettledCheck x402 endpoints before your agent pays: payTo, paid test purchases, payee and buyer reports. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Setup DoctorScore and improve your AI coding agent setup. Local-only, open source. | Local · stdio |
| SeturosShared work memory for Claude Code, Codex, Cursor and chat, scoped to each repository. | Remote · HTTPLive check: sign-in required |