Agent Email List — Free SMTP Relay for AI Agents MCP server
com.agentemaillist.ai/free-transactional-email-smtp-relayai.agentemaillist.comstreamable-httpv0.2.0Scanned
Free transactional email + SMTP relay. Agents self-signup, no API key needed to start.
8 tools: 1 do something that can't be undone, 3 change things and 4 only read.
- Reads private data · 2
- Reads text others write · 2
- Can send data out · 1
- 1 finding
The remote endpoint did not answer the last look. Remote posture
Anlyon alternative
4 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the Agent Email List — Free SMTP Relay for AI Agents MCP server can do
The Agent Email List — Free SMTP Relay for AI Agents MCP server is published by ai.agentemaillist.com, a domain the MCP Registry verified. It has 8 tools. It can do things that cannot be undone, such as sending, paying or publishing (send_email) and create or change data (3 tools: create_account, add_domain and verify_domain), but cannot delete data. 4 tools only read.
2 tools read private data (list_messages and get_delivery_events); 2 tools bring in text other people can write (list_messages and get_delivery_events); 1 tool can send data out of your system (send_email). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.
Last scanned Nov 10, 2026, version 0.2.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
8 tools
Can't be undone 1Claude Code: ask
send_emailSend a message.Can send data outNo findings
Why it is in this group
- The name "send_email" says "send": a word for sending, and what is sent cannot be taken back.
- The input addresses people (input.to): what it sends cannot be taken back.
What it can reach
- outboundThe name "send_email" says "send": it sends or publishes something to other people.
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Description, as the server wrote it 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.
Changes things 3Claude Code: ask
add_domainRegister a domain to send from, and get the DNS records that must be published before it will work.No findings
Why it is in this group
- The name "add_domain" says "add": a word for a change.
Description, as the server wrote it 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.
create_accountCreate an account on this email service and get an API key back.1 finding
Why it is in this group
- The name "create_account" says "create": a word for a change.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...get an API key back. Needs no existing credentials, so an agent with nothing can call this..."
Description, as the server wrote it 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.
verify_domainRe-read DNS now and mark the domain active if its SPF and DKIM records are visible.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Only reads 4Show 4 read-only tools
get_delivery_eventsWhat happened to messages on this domain: accepted, delivered, failed, and so on.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_delivery_events" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "message": it reads messages.
- untrusted-inputThe description's first sentence says "message": it reads messages, which other people can write.
Description, as the server wrote it 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.
get_sending_limitsHow 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.No findings
Why it is in this group
- The name "get_sending_limits" says "get": a word for reading.
Description, as the server wrote it 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.
list_domainsList the sending domains on this account, with their verification state and how much of today's sending allowance each has left.No findings
Why it is in this group
- The name "list_domains" says "list": a word for reading.
Description, as the server wrote it List the sending domains on this account, with their verification state and how much of today's sending allowance each has left.
list_messagesRecent messages for a domain, sent and received.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "list_messages" says "list": a word for reading.
What it can reach
- private-dataThe name "list_messages" says "list" and "message": it reads messages.
- private-dataThe description's first sentence says "message": it reads messages.
- private-dataThe input names a folder (input.folder), and the tool reads: it reads files.
- untrusted-inputThe name "list_messages" says "list" and "message": it reads messages, which other people can write.
- untrusted-inputThe description's first sentence says "message": it reads messages, which other people can write.
Description, as the server wrote it Recent messages for a domain, sent and received. Use direction to filter, and folder to separate inbox from spam on received mail.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
4 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.
- Reads private data2
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__free-transactional-email-smtp-relay__send_email"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:33 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- no
- HTTP status of an anonymous initialize
- not observed
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
The probe stopped: The operation was aborted due to timeout
Posture changes
- Nov 20, 2026
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 4 to 0
- Protocol version: 2025-06-18 to none
Findings
Matches of fixed checks, with the text they matched.
- Infocreate_account
The description mentions "credentials".
What this check looks forMatched text
description: "...get an API key back. Needs no existing credentials, so an agent with nothing can call this..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 2 more).View diff
- Reachable: yes to no
- HTTP status of an anonymous initialize: 200 to none
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 4 to 0
- Protocol version: 2025-06-18 to none
Install
Pinned to version 0.2.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http free-transactional-email-smtp-relay https://ai.agentemaillist.com/mcpclaude mcp add --transport http free-transactional-email-smtp-relay https://ai.agentemaillist.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__free-transactional-email-smtp-relay__list_domains",
"mcp__free-transactional-email-smtp-relay__get_sending_limits",
"mcp__free-transactional-email-smtp-relay__list_messages",
"mcp__free-transactional-email-smtp-relay__get_delivery_events"
],
"ask": [
"mcp__free-transactional-email-smtp-relay__create_account",
"mcp__free-transactional-email-smtp-relay__add_domain",
"mcp__free-transactional-email-smtp-relay__verify_domain",
"mcp__free-transactional-email-smtp-relay__send_email"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as free-transactional-email-smtp-relay. Review it before you use it.
Capability tags behind 3 rules
- mcp__free-transactional-email-smtp-relay__send_email outbound
- mcp__free-transactional-email-smtp-relay__list_messages private-data, untrusted-input
- mcp__free-transactional-email-smtp-relay__get_delivery_events private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.agentemaillist.ai/free-transactional-email-smtp-relay/verify?hash=c9aabca44d217796d659a946afcd652e026cd4a421642a664410eff5dd55ecce" | jq -e '.changed == false'Pinned hash c9aabca44d21, from Nov 10, 2026, 09:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.agentemaillist.ai/free-transactional-email-smtp-relay/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.agentemaillist.ai/free-transactional-email-smtp-relay)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:48 UTC.
Agent Email List — Free SMTP Relay for AI Agents MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Agent Email List — Free SMTP Relay for AI Agents MCP server safe?
- No scan can promise that. What its definitions show: 8 tools, 4 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Agent Email List — Free SMTP Relay for AI Agents MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Agent Email List — Free SMTP Relay for AI Agents MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: send_email.
What tools does the Agent Email List — Free SMTP Relay for AI Agents MCP server have?
- 8 tools: 1 irreversible, 3 write, 4 read. send_email, create_account, add_domain, verify_domain, list_domains, get_sending_limits, list_messages and get_delivery_events.
Does the Agent Email List — Free SMTP Relay for AI Agents MCP server need sign-in or OAuth?
- Its remote endpoint did not answer the last anonymous look.
Does the Agent Email List — Free SMTP Relay for AI Agents MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): send_email.
Has the Agent Email List — Free SMTP Relay for AI Agents MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.