aliasmail-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| aliasmail_create_inboxA | Generate an instant, zero-log disposable temporary email inbox on AliasMail (https://aliasmail.space/). No registration required. Ready immediately to receive verification emails, OTP codes, or test messages. |
| aliasmail_get_messagesA | Fetch emails from an AliasMail temporary inbox (https://aliasmail.space/temporary/). Returns list of received messages with subject, sender, timestamp, and snippet. |
| aliasmail_get_messageA | Retrieve full content of a specific email received in an AliasMail temporary inbox, including body text, sanitized HTML, headers, and extracted links/codes. |
| aliasmail_wait_for_codeB | Autonomous AI Agent helper: Polls an AliasMail inbox until a verification/signup email arrives and automatically parses the 4-8 digit OTP code or confirmation link. Eliminates manual polling and regex parsing. |
| aliasmail_wait_for_emailB | Wait for any new incoming email on an AliasMail temporary inbox with optional sender or subject filtering. |
| aliasmail_validate_emailA | Deep email address validation via AliasMail (https://aliasmail.space/tools/email-validator/). Checks RFC 5322 syntax, domain MX resolution, typo detection (e.g. gmial.com), and disposable mailbox flagging. |
| aliasmail_check_disposableA | Check whether an email address or domain belongs to a disposable/temporary burner provider or legitimate corporate mail infrastructure. |
| aliasmail_check_spam_scoreA | Evaluate email copy against spam heuristic triggers, capitalization ratios, link density, and deliverability risk via AliasMail Spam Checker. |
| aliasmail_analyze_headersB | Deep RFC 822 email header analyzer: inspects SPF, DKIM, DMARC verdicts, hop relay transit timeline, and security grading. |
| aliasmail_clean_trackingB | Scan and defuse invisible 1x1 tracking pixels, read receipt beacons, and surveillance redirect links in email HTML. |
| aliasmail_check_dnsB | Real-time DNS audit of domain Mail Exchange (MX) records, SPF syntax, DMARC policy enforcement, and DKIM public keys. |
| aliasmail_health_checkA | Check health and operational status of the AliasMail infrastructure and API services. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| signup-and-verify |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Most tools target clearly distinct operations: inbox creation, message listing/retrieval, waiting, and validation/security checks. There is mild overlap between wait_for_code and wait_for_email, and between validate_email/check_disposable and analyze_headers/check_dns, but descriptions provide enough distinction for an agent to choose correctly.
All tools follow a consistent aliasmail_verb_noun pattern in snake_case, such as create_inbox, get_messages, wait_for_code, and check_dns. The convention is predictable across the entire set.
Twelve tools sit comfortably in the well-scoped range and cover both temporary inbox workflows and email validation/security utilities. Each tool appears to earn its place without excessive surface area.
The surface covers the core lifecycle of creating an inbox, reading messages, waiting for codes/emails, and running validation and security checks. Minor gaps exist around inbox deletion/expiration management and attachment handling, but agents can work around these for typical verification workflows.