vaemail
OfficialRelated Servers
Alternatives to vaemail
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to send transactional emails and manage email infrastructure through the AgentiSend API, including domain verification, budgeted keys, and message logs.34 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to autonomously create email accounts, verify domains, send and receive emails, and monitor delivery events without requiring human sign-up or payment.1-
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to query and manage email deliverability data — bounces, complaints, suppressions, delivery stats, and campaigns — across multiple providers like AWS SES, SendGrid, Mailgun, and Postmark.10 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients and coding agents to send transactional emails, retrieve a message by ID, and list sent emails through the Postlane API using an API key and verified sender domain.28 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to register domains, manage DNS, create mailboxes, and send/receive email through typed tools.197 npm2MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to programmatically manage email outreach campaigns, leads, domains, senders, and webhook events, as well as send emails, through the Model Context Protocol over HTTP.-
TDQS
Scored across 13 tools
Most tools target a distinct resource and action: send, validate, get message, list messages, bounces, usage, audit, domains. The only mild overlap is between vaemail_dns_requirements and vaemail_create_domain, since both return DNS records, but they are separated by stage: one is a general reference and the other acts on a specific newly declared domain.
All tools share the vaemail_ prefix and most follow a clear verb_noun pattern such as list_domains, send_email, get_message, create_domain. Two tools, vaemail_capabilities and vaemail_dns_requirements, are noun-only rather than verb_noun, which is a minor deviation but does not create confusion.
13 tools is well within the ideal range and appropriate for a transactional email service. Each tool covers a meaningful part of the workflow: capabilities, domain setup, sending, delivery tracking, bounce management, validation, usage, and diagnostics.
The tool surface covers the main transactional email lifecycle: send, validate, track, list, diagnose deliverability, manage domain verification, and review bounces. Minor gaps exist such as no domain removal or bounce management beyond listing, but agents can complete core workflows without dead ends.