Innmail for Agents MCP Server

by innmail Your server? Claim it

answering

Innmail for Agents is answering right now. Last checked 2 min ago.

Email inbox for an AI agent: threads, send, reply, drafts, verification codes, calendar.

Uptime history 47 hours of history

47 hours agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

269 ms

Response time

average over 24h

authentication required

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Innmail for Agents every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

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 Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add agents --transport http https://www.innmail.app/api/v1/mcp

Settings → Connectors → Add custom connector, then paste this address

https://www.innmail.app/api/v1/mcp

~/.codex/config.toml

[mcp_servers.agents]
url = "https://www.innmail.app/api/v1/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "agents": {
      "url": "https://www.innmail.app/api/v1/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "agents": {
      "type": "http",
      "url": "https://www.innmail.app/api/v1/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Endpoints

URL	Transport	State	Latency	Checked
https://www.innmail.app/api/v1/mcp	streamable-http	needs auth	272 ms	2 min ago

Alternatives to Innmail for Agents

same job, measured the same way

Mail for Bots

by mailforbots

Email inboxes for AI agents: send, reply, read verification codes, human-approved drafts.

answering

Agenticmail

by agenticmail

Real email and SMS for AI agents — send mail, receive verification codes, drive a real inbox.

48 installs/wk local only

Machine Inbox

by machineinbox

Task-scoped email inboxes for AI agents: read mail, extract verification codes, and reply.

11 tools answering

DevInbox

by devinbox

Real email inboxes for AI agents: create inboxes, catch verification codes, extract OTPs, reply.

answering

Temp Mail

by temp-mail

Disposable email inboxes for AI agents — read messages and verification codes.

answering

Agentboxd

by agentboxd

Real email inboxes for AI agents: create addresses, send, wait for mail and verification codes.

answering

Mailly

by mailly

A real inbox for agents: read mail, draft replies you approve, wait for verification codes.

answering

send0

by send0-dev

Email inboxes for AI agents: create an address, wait for codes and links, send and reply in threads.

18 installs/wk answering

Innmail for Agents — questions

Answers built from our own checks of this server.

Why is there no tool list for Innmail for 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 Innmail for 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 269 ms. The bar chart above shows every period we have measured.

How do I connect Innmail for Agents?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form 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 credentials: it refuses anonymous clients.

Does Innmail for Agents need an API key?

Yes. Every time we knock, Innmail for 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 Innmail for Agents?

It answers our handshake in 269 ms on average, which is faster than 62% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.