Free Temporary Email MCP server
Which servers in the official MCP registry are Free Temporary Email's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-20
- Registry namecom.mailtempo/mailtempoverified in the MCP registry
The registry name sits under mailtempo.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-20
- Tools3
- Server calls itselfmailtempo
- Server version0.1.0
- Protocol version2025-06-18
On 2026-10-20 the server answered initialize and tools/list without a sign-in. First answer in 228 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 1 of the 7 days it takes to judge reliability.
Once connected
- Parameters are untyped or undescribed in 2 of 3 tools: check arguments before calling.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
- Answeredmeasuring1 of the 7 daily checks it takes to print a share
- Median first answer274 ms
- Space in an agent's context≈ 293 tokensthe definitions of all its tools (3), which an agent carries on every turn
- Tool definitionsC · 72 of 100
- Parameters without a description: in 2 of 3
- Not saying whether it only reads or can destroy: 3 of 3
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
list_domainsList all active MailTempo catchall domains. Returns { domains: [{ domain, displayName }] }. Takes no arguments.
list_messagesList the most recent non-hidden messages for a MailTempo address. Input: { address: string } (e.g. 'foo@yourdomain.com'). Returns up to 100 messages newest first, each with id, fromAddr, fromName, subject, snippet, receivedAt, otp.
get_messageGet a single MailTempo message by its public id. Input: { id: string } (8-32 chars, alphanumerics + '-' + '_'). Returns id, fromAddr, fromName, toAddr, subject, receivedAt, text, html (sanitized, remote refs stripped), otp, headers…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"mailtempo": {
"type": "http",
"url": "https://mailtempo.com/api/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http mailtempo https://mailtempo.com/api/mcpclaude.ai, ChatGPT and other clients: add https://mailtempo.com/api/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.