mcpbeat

Inbound Email MCP Server

dev.mailkite/inbound-email
answering

Inbound Email is answering right now. Last checked 2 min ago. Last commit 3 Aug 2026.

Turn inbound email into a webhook — verify, parse, route, and store incoming messages.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
284 ms
Response time
average over 24h
0
Stars
last commit 3 Aug 2026

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 inbound-email --transport http https://mcp.mailkite.dev/mcp?ref=inbound-email
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "inbound-email": {
      "url": "https://mcp.mailkite.dev/mcp?ref=inbound-email"
    }
  }
}
~/.codex/config.toml
[mcp_servers.inbound-email]
url = "https://mcp.mailkite.dev/mcp?ref=inbound-email"
.cursor/mcp.json
{
  "mcpServers": {
    "inbound-email": {
      "url": "https://mcp.mailkite.dev/mcp?ref=inbound-email"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "inbound-email": {
      "url": "https://mcp.mailkite.dev/mcp?ref=inbound-email"
    }
  }
}

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.mailkite.dev/mcp?ref=inbound-email streamable-http needs key 444 ms 2 min ago

Inbound Email — questions

Answers built from our own checks of this server.

Why is there no tool list for Inbound Email?
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 Inbound Email 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 284 ms. The bar chart above shows every period we have measured.
How do I connect Inbound Email?
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 Inbound Email need an API key?
Yes. Every time we knock, Inbound Email 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 Inbound Email?
It answers our handshake in 284 ms on average, which is faster than 48% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Inbound Email open source?
Yes — written in JavaScript and 0 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.