Receiver.email
email.receiver/mcp
Real inboxes for AI agents: create an address, then wait for and read sign-up codes and magic links.
Connect this server
One click to install, or copy the config below. Suits: Claude Desktop · Cursor.
Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"@receiverdotemail/mcp@0.1.1"
],
"env": {
"RECEIVER_API_KEY": "<your RECEIVER_API_KEY>"
}
}
}
}claude mcp add --env RECEIVER_API_KEY='<your RECEIVER_API_KEY>' --transport stdio mcp -- npx -y @receiverdotemail/mcp@0.1.1codex mcp add mcp --env RECEIVER_API_KEY='<your RECEIVER_API_KEY>' -- npx -y @receiverdotemail/mcp@0.1.1code --add-mcp '{"name":"mcp","type":"stdio","command":"npx","args":["-y","@receiverdotemail/mcp@0.1.1"],"env":{"RECEIVER_API_KEY":"<your RECEIVER_API_KEY>"}}'Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in.
- RECEIVER_API_KEYrequiredsecretProject API key from the Receiver.email dashboard (recv_live_...)
A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.
- Category
- Search & Web
- Version
- 0.1.1
- Registry
- active
- Published
- 11/20/2026
Is it safe? Is it maintained?
Serverdex check: Nov 22, 2026Mostly fine: Receiver.email is hosted endpoint behind a sign-in.
- Maintained
- No commit data
- The repository has not been read yet, so the last-commit date is unknown.
- Official registry
- Active
- Published as email.receiver/mcp in the official MCP registry, version 0.1.1.
- Source
- No licence found
- Public repository, but GitHub reports no recognised licence. Check the README before shipping it in a product.
- Runs
- Local package or hosted
- Ships as a local package (npm) that runs on your machine, and as a hosted endpoint at mcp.receiver.email that receives what your client sends it.
- Credentials
- Sign-in required
- The hosted endpoint answered 401/403 to a credential-free call (checked Nov 22, 2026): it wants an API key or an OAuth login first.
- Owner
- Unclaimed
- Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.
Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself and see the status history.
Live check
checked Nov 22, 2026, 07:07 UTCStatus history & uptime →The endpoint is up but wants a key or an OAuth sign-in before the handshake, so its tools can only be read with an account.
Checked by Serverdex with a plain initialize + tools/list call to mcp.receiver.email/mcp, no credentials, about once a day. A failed check is never a removal.
Remotes
- streamable-http
https://mcp.receiver.email/mcp
Alternatives to Receiver.email
All Receiver.email alternatives →Best Search & Web servers →The most-starred Search & Web servers in the index, with their live-check result.
| Server | Stars | Last push | Live check |
|---|---|---|---|
| Browser Use | 121,623 | Nov 2026 | Working |
| Scrapling MCP Server | 104,822 | Nov 2026 | Local / not checked |
| Chrome DevTools MCP | 58,028 | Nov 2026 | Local / not checked |
| Chrome DevTools MCP | 58,014 | Nov 2026 | Local / not checked |
| com.puter MCP Server | 44,182 | Nov 2026 | Needs sign-in |
Receiver.email: questions people ask
- Is Receiver.email a remote or a local MCP server?
- According to its entry in the official MCP registry, Receiver.email ships as a hosted endpoint (streamable-http) that your client connects to by URL and as a local package (npm) that your client starts on your machine. Use the hosted endpoint when your client supports Streamable HTTP; use the package when you want it to run locally.
- Does Receiver.email need an API key or a sign-in?
- Yes. Its hosted endpoint answered the credential-free Serverdex live check with HTTP 401/403 on Nov 22, 2026: it expects an API key in a header or an OAuth login before it lists its tools.
- Is Receiver.email safe to use?
- Mostly fine: Receiver.email is hosted endpoint behind a sign-in. In detail — maintained: No commit data; official registry: Active; source: No licence found; runs: Local package or hosted; credentials: Sign-in required. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
- How do I add Receiver.email to Claude, Cursor or VS Code?
- Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
More Search & Web servers
Browse all Search & Web →MachineWitness
martinschenk
EU archive of the machine-readable web: check a domain, order a time-stamped record or extract.
Modulit Pro AV Finder
id-collab
Search Modulit EU and Polish pro AV equipment and guides, size cable runs and configure AV hardware.
Témoin public
temoinpublic
Prove a web page or document existed on a date: public SHA-256 registry anchored in Bitcoin. Free.
ClearMarket
JDSource
Reference data for prediction markets: graded resolution clarity, cross-venue links, provenance.
LFG
lfg-gm
A social alarm clock and research agent: links that research or watch what you care about, and ring.
Tiiny Host
Tiiny-Host
Publish web pages as live websites on Tiiny Host, and list, update or delete your sites.
Add the badge to your site
Show visitors that Receiver.email is listed here — it’s also the link we check for a free listing.
HTML — for your website
<a href="https://serverdex.io/server/email-receiver-mcp?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="Receiver.email — listed on Serverdex" width="123" height="40" loading="lazy"></a>Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.
Markdown — for your README
[](https://serverdex.io/server/email-receiver-mcp?utm_source=badge)Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.
Install buttons — for your README
[](https://serverdex.io/install/cursor/email-receiver-mcp) [](https://serverdex.io/install/vscode/email-receiver-mcp) [](https://serverdex.io/install/claude-code/email-receiver-mcp)One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.
Install buttons — HTML for your docs
<a href="https://serverdex.io/install/cursor/email-receiver-mcp"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/email-receiver-mcp"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/email-receiver-mcp"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>Same buttons as plain links for a docs page or website.
Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).