mcpbeat

e2a — email for AI agents MCP Server

io.github.Mnexa-AI/mcp-server
answering

e2a — email for AI agents is answering right now. Last checked 2 min ago. 54 installs a week from npm.

Authenticated email gateway for AI agents — per-agent inboxes, HITL approval, SPF/DKIM verified.

The linked repository no longer exists on GitHub — it was deleted or made private.

Installs per day peak 25 · avg 8 · -13% w/w
a month agotoday
Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
659 ms
Response time
average over 24h
54
Installs / week
npm and PyPI

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.

run in your terminal
claude mcp add mcp-server --transport http https://mcp.e2a.dev/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "mcp-server": {
      "url": "https://mcp.e2a.dev/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.mcp-server]
url = "https://mcp.e2a.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp-server": {
      "url": "https://mcp.e2a.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "mcp-server": {
      "url": "https://mcp.e2a.dev/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://mcp.e2a.dev/mcp streamable-http needs key 656 ms 2 min ago

e2a — email for AI agents — questions

Answers built from our own checks of this server.

Why is there no tool list for e2a — email for AI agents?
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 e2a — email for AI agents working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 659 ms. The bar chart above shows every period we have measured.
Is e2a — email for AI agents still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect e2a — email for AI agents?
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 e2a — email for AI agents need an API key?
Yes. Every time we knock, e2a — email for AI agents 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 e2a — email for AI agents?
It answers our handshake in 659 ms on average, which is faster than 13% 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.
How many people use e2a — email for AI agents?
The npm package @e2a/mcp-server was installed 54 times in the last week. Week over week that is -13%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.