Agent Email List — Free SMTP Relay for AI Agents
REMOTE · AI.AGENTEMAILLIST.COM · SCANNED SEP 20
Free transactional email + SMTP relay. Agents self-signup, no API key needed to start.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 775 tokens (~96/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 62% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_email" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the Agent Email List — Free SMTP Relay for AI Agents MCP server?
Agent Email List — Free SMTP Relay for AI Agents is a hosted endpoint at https://ai.agentemaillist.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · ai.agentemaillist.com
claude mcp add --transport http com-agentemaillist-ai-free-transactional-email-s 'https://ai.agentemaillist.com/mcp'
{
"mcpServers": {
"com-agentemaillist-ai-free-transactional-email-s": {
"url": "https://ai.agentemaillist.com/mcp"
}
}
} {
"servers": {
"com-agentemaillist-ai-free-transactional-email-s": {
"type": "http",
"url": "https://ai.agentemaillist.com/mcp"
}
}
} [mcp_servers.com-agentemaillist-ai-free-transactional-email-s] url = "https://ai.agentemaillist.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-agentemaillist-ai-free-transactional-email-s": {
"type": "remote",
"url": "https://ai.agentemaillist.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-agentemaillist-ai-free-transactional-email-s --url 'https://ai.agentemaillist.com/mcp' --transport streamable-http
mcp_servers:
com-agentemaillist-ai-free-transactional-email-s:
url: "https://ai.agentemaillist.com/mcp" {
"McpServers": {
"com-agentemaillist-ai-free-transactional-email-s": {
"Transport": "http",
"Url": "https://ai.agentemaillist.com/mcp"
}
}
} assistant mcp add com-agentemaillist-ai-free-transactional-email-s -t streamable-http -u 'https://ai.agentemaillist.com/mcp'
{
"mcpServers": {
"com-agentemaillist-ai-free-transactional-email-s": {
"type": "http",
"url": "https://ai.agentemaillist.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 15 Sept 26 63
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://ai.agentemaillist.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=ai.agentemaillist.com | CN=YE2,O=Let's Encrypt,C=US | 14 Sept 2026 | 13 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6de9ae25945352107e5cc866a25f8b971b9 |
| SANs: ai.agentemaillist.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of ai.agentemaillist.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| agentemaillist.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://ai.agentemaillist.com/mcp | Verified | 200 | |
| http (plaintext) | http://ai.agentemaillist.com/mcp | HTTPS enforced | 301 | https://ai.agentemaillist.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_domain ~79
Register a domain to send from, and get the DNS records that must be published before it will work. Publishing DNS usually needs a human with registrar access, so start this early. The domain cannot send until verify_domain succeeds.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | A bare domain such as mail.yourcompany.com. A subdomain is better than the root. |
No output schema declared.
No examples provided.
create_account ~101
Create an account on this email service and get an API key back. Needs no existing credentials, so an agent with nothing can call this first. The key is returned once and never again. Free, with no card and no trial clock.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | A contact address for the account. | |
| name | string | – | Optional display name. |
| password | string | yes | At least 12 characters. Needed only to sign in to the web console. |
No output schema declared.
No examples provided.
get_delivery_events ~84
What happened to messages on this domain: accepted, delivered, failed, and so on. A send returning success means queued, not delivered; this is where the delivery outcome actually appears.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| event | string | – | Filter to one type, such as delivered or failed. |
| limit | integer | – | – |
| recipient | string | – | – |
No output schema declared.
No examples provided.
get_sending_limits ~105
How much this domain may send today and what graduates it to the next rung, plus this account's standing: how many domains it may hold and whether sending is paused. New domains start at a low daily cap and climb as they prove themselves, so check this before planning a bulk send rather than discovering it part-way. Call it with no domain for the account-level answer alone.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | – | Optional. Omit for account limits without a domain's allowance. |
No output schema declared.
No examples provided.
list_domains ~31
List the sending domains on this account, with their verification state and how much of today's sending allowance each has left.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_messages ~71
Recent messages for a domain, sent and received. Use direction to filter, and folder to separate inbox from spam on received mail.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | – |
| domain | string | yes | – |
| folder | string | – | – |
| limit | integer | – | Up to 100. Defaults to 25. |
No output schema declared.
No examples provided.
send_email ~150
Send a message. The domain must be verified and the from address must belong to it. Counts one against the daily allowance per recipient. Set test_mode true to run the whole pipeline, including content screening, without sending anything and without spending allowance — do that first when building.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The verified domain to send from. |
| from | string | yes | An address at that domain. |
| html | string | – | Optional HTML body. |
| subject | string | – | – |
| test_mode | boolean | – | Accept and screen the message but send nothing. Defaults to false. |
| text | string | – | Plain text body. |
| to | string | yes | One address, or several separated by commas. |
No output schema declared.
No examples provided.
verify_domain ~53
Re-read DNS now and mark the domain active if its SPF and DKIM records are visible. DNS takes minutes to hours to propagate; poll this every few minutes, not every few seconds.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
What is the Agent Email List — Free SMTP Relay for AI Agents MCP server?
Agent Email List — Free SMTP Relay for AI Agents is an MCP server listed in the public MCP registry as com.agentemaillist.ai/free-transactional-email-smtp-relay. Free transactional email + SMTP relay. Agents self-signup, no API key needed to start. This page covers its hosted endpoint (https://ai.agentemaillist.com/mcp).
Is the Agent Email List — Free SMTP Relay for AI Agents MCP server safe to use?
Agent Email List — Free SMTP Relay for AI Agents scores 65 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Agent Email List — Free SMTP Relay for AI Agents MCP server expose?
Agent Email List — Free SMTP Relay for AI Agents exposes 8 tools: create_account, list_domains, add_domain, verify_domain, send_email, and 3 more. Their descriptions and schemas cost roughly 674 tokens of context every time the server is loaded.
Does the Agent Email List — Free SMTP Relay for AI Agents MCP server require authentication?
No. We connected to Agent Email List — Free SMTP Relay for AI Agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Agent Email List — Free SMTP Relay for AI Agents MCP server still maintained?
Agent Email List — Free SMTP Relay for AI Agents is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.