MinuteMail

https://server.smithery.ai/minutemailco/minutemail/mcp

● healthy

Disposable email infrastructure for AI agents and end-to-end tests. MinuteMail gives your agent 39 tools for testing anything that touches email or OAuth: ephemeral mailboxes, inbound mail simulation, attachments, custom domains, team management, and a mock OAuth IdP. Test signup flows, email verification, password resets, and OAuth logins — without real inboxes or real identity providers. Create a mailbox, trigger your flow, read the mail, extract the code, done. Everything expires automatically, so CI runs start clean. **Requires a free MinuteMail API key** — create one at [minutemail.co](https://minutemail.co). The MCP server is a stateless proxy: it holds no credentials or local data of its own — your key is forwarded to the MinuteMail API, and all state (mailboxes, mails, identities) lives there.

Transport

streamable-http

Auth

smithery_api_key

Cost

—

Protocol revision

2025-06-18

negotiated, not declared

MCP readiness

B · 80/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	24/25	Endpoint answers the MCP initialize handshake (4381 ms); slow response -1.
Protocol revision	6/10	Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	30/30 probes succeeded over 30 days (100%).
Tool declaration	10/10	Lists 40 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	0/5	not seen in a source for over 30 days.
Auth declaration	2/5	Declares credential scheme: smithery_api_key.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Slow (4381 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 45% of peers; This listing 80 · peer median 81
Latency: Faster than 23% of peers; This listing 593 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags −5 — Keep the listing current in the registry or source it comes from.
Now: not seen in a source for over 30 days.
Protocol revision −4 — Support the current protocol revision.
Now: Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-08-24 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/minutemailco/minutemail/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/minutemailco/minutemail/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://minutemail.co

Listed at (smithery)

https://minutemail.co