@1tempmail/mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| 1TEMPMAIL_API_KEY | Yes | Your 1TempMail API key | |
| 1TEMPMAIL_API_BASE | No | API base URL | https://www.1tempmail.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_emailA | Generate a new temporary email address. The email remains active for 60 minutes and can receive messages during that time. |
| check_inboxA | Retrieve all messages currently in the inbox for a given temporary email address. |
| get_messageA | Retrieve the full content of a specific message, including the HTML body and attachments metadata. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clear, distinct purpose: generate_email creates addresses, check_inbox lists messages, get_message retrieves details. No overlapping functionality.
All tools follow a consistent verb_noun pattern (generate_email, check_inbox, get_message), making them predictable and easy to understand.
Three tools are appropriate for a temporary email service, covering the essential operations (create, list, read) without unnecessary bloat.
The set covers core create and read operations but lacks a delete or refresh tool, which could be useful but is not critical given auto-expiry.