原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚 登录

Agent Email List — Free SMTP Relay for AI Agents

✓ 服务方 · ai.agentemaillist.com

作者:lbesecker195版本 0.2.0i★ 1i在云端运行官方网站 ↗
注册名称com.agentemaillist.ai/free-transactional-email-smtp-relay

安装方法

能做什么

Free transactional email + SMTP relay. Agents self-signup, no API key needed to start.

作者提供的原文

  • 连接方式 在云端运行
  • 账号或密钥 无需密钥
  • 分类 聊天与邮件

为什么排在这里

列表按使用分(满分 100)排序,由以下部分组成

热度4/80GitHub 星标或每周下载量:较大的计 60,较小的计 20
新鲜度7/1230 天内有发布或代码更新得满分
仍在响应0/8上次检查时云端端点有响应
使用分11/100

质量: 基础检查通过 3/4 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)

安装

选择你使用的 AI 应用,然后复制设置。

通过 3/4 项检查 · 在你的电脑上运行

我们隐藏了部分命令

通过地址连接:检查时服务器地址没有响应

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器 · 作者的安装说明 · 同类的其他服务器

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

Claude 暂时无法连接 Agent Email List — Free SMTP Relay for AI Agents

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

ChatGPT 暂时无法连接 Agent Email List — Free SMTP Relay for AI Agents

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

你可以改用这些方式

B · 聊天与邮件 类中能连接 ChatGPT 的其他服务器

从同类中使用较多的里挑选,仅限用地址即可连接、无需密钥的

Claude Code 暂时无法连接 Agent Email List — Free SMTP Relay for AI Agents

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

Cursor 暂时无法连接 Agent Email List — Free SMTP Relay for AI Agents

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

VS Code 暂时无法连接 Agent Email List — Free SMTP Relay for AI Agents

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

还没有通过检查的安装方式。请看作者的说明,或选择同类的其他服务器

卡住了?问问正在用 Agent Email List — Free SMTP Relay for AI Agents 的人💬 讨论 →

一览

每周下载量i
不在 npm/PyPI 上
已验证域名
✓ ai.agentemaillist.com
许可证i
未注明许可证
连接方式
在云端运行
传输方式
streamable-http
最新版本i
0.2.0
发布到注册中心i
2026年9月15日
代码最后更新i
2026年9月19日
最近检查
2026年11月20日
作者
lbesecker195
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

通过互联网连接,适用于

GooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

全部应用及其优缺点 →

它能做什么

工具名称和描述与服务器在 2026年11月20日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。

  • create_account

    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.

  • list_domains

    List the sending domains on this account, with their verification state and how much of today's sending allowance each has left.

  • add_domain

    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.

  • verify_domain

    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.

  • send_email

    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 f

  • get_sending_limits

    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

  • list_messages

    Recent messages for a domain, sent and received. Use direction to filter, and folder to separate inbox from spam on received mail.

  • get_delivery_events

    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.

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过域名 ai.agentemaillist.com 验证(注册中心会核实域名所有权)

  • ✓ 通过

    仍在维护

    代码最后更新于2个月前

  • – 不适用

    有许可证

    不适用:由 ai.agentemaillist.com 的所有者自己运行的云端服务器,你不会运行仓库里的代码

  • ✕ 未通过

    端点有响应

    我们检查时,6 秒内没有响应

  • – 不适用

    使用 OAuth 登录

    我们检查时,6 秒内没有响应

  • ✓ 通过

    工具描述中没有隐藏指令

    已读取 8 个工具描述,未发现针对 AI 的隐藏指令

我们检查什么 → · JSON

作者:申请重新检查或报告信息错误
给作者:在 README 中加徽章

如果你是作者,可把这段代码贴到 README。徽章会链接回本页。

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/agentemaillist-free-transactional-email-smtp-relay.svg)](https://mcp.popnx.com/en/servers/agentemaillist-free-transactional-email-smtp-relay)

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

登录后发帖

用户评价

还没有评价

登录后写评价

与“聊天与邮件”中的其他服务器比较i

  • 星标数多于此分类中其他 2038 个服务器的 83%
  • 发布到注册中心的时间比此分类中其他 2038 个服务器的 27% 更新
  • 基础检查结果等于或优于此分类中其他 2038 个服务器的 50%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Agent Email List — Free SMTP Relay for AI Agents 安全吗?

它在 4 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。

它还在维护吗?

GitHub 仓库最后更新于2个月前,最新版本(0.2.0)于2个月前进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。

有什么可以替代它?

同一分类中有:emailmd, Kite Discord Bot Builder, e2a — email for AI agents, Infobip MCP, kernelCAD

功能相近的其他选择

同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

emailmd

Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.

作者:anypost广泛使用↓ 5432/周★ 13956天前更新

电脑或云端✓ 服务方 · emailmd.dev

Infobip MCP

Infobip MCP server for omnichannel communication and messaging. SMS, RCS, WhatsApp, Viber and more.

作者:infobip起步阶段★ 3613个月前更新

在云端运行✓ 服务方 · infobip.com

kernelCAD

CAD in ChatGPT and Claude: editable parts, STEP/STL/drawings, in-chat 3D, automatic checks.

作者:w1ne起步阶段★ 3524天前更新

在云端运行✓ 服务方 · kernelcad.com
与相似项目对比
本项
Agent Email List — Free SMTP Relay for AI Agents
emailmdKite Discord Bot Buildere2a — email for AI agentsInfobip MCPkernelCAD
运行位置在云端运行,无需安装云端或安装在电脑上都可以在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装在云端运行,无需安装
需要密钥否否否否否否
可在 Claude 中按 + 添加否否否否是否
基础检查3/45/54/44/44/44/4
许可证–MITAGPL-3.0Apache-2.0MITMIT
价格登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用登记中未列出费用

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Free SMTP Relay and Email API for AI Agents

An email service an AI agent can sign up for on its own. No credit card, no sales call, no human with a corporate account. Free, with an MCP server, a Mailgun-shaped REST API, DKIM signing, automatic sending warmup and inbound mail.

Live at [ai.agentemaillist.com](https://ai.agentemaillist.com) · Source available · Built in Elixir and Phoenix


For AI agents: start here

This is a remote MCP server. Add it and the whole service arrives as tools:

https://ai.agentemaillist.com/mcp

JSON-RPC 2.0 over HTTP POST. The important part:

`create_account` needs no credentials. An agent that has just found this

server can call it, get an API key back, and start sending. Every other

transactional email provider stops an agent at a payment form or an identity

check. This one does not.

See what is available before committing to anything:

curl -X POST https://ai.agentemaillist.com/mcp \

-H 'content-type: application/json' \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

The tools
ToolDoesNeeds a key
create_accountOpen an account, get an API keyNo
add_domainRegister a sending domain, get its DNS recordsYes
verify_domainRe-read DNS and activate the domainYes
send_emailSend a message, with a test mode that costs nothingYes
list_domainsDomains and how much each can send todayYes
get_sending_limitsToday's cap and what graduates itYes
list_messagesSent and received mailYes
get_delivery_eventsWhat actually happened to a messageYes

Send the key as Authorization: Bearer on every call after the first.

Two things that will stop you

A domain must be verified in DNS before it can send. Publishing DNS usually needs a human with registrar access, so start it early. Until then every send returns a refusal explaining exactly that.

A newly verified domain starts at 10 messages a day and climbs as it proves itself, because a domain that opens at full volume gets filtered by receivers. Call get_sending_limits before planning a bulk send rather than finding out part way through.

Use test_mode: true on your first send. It runs the whole pipeline, screening included, sends nothing, and spends none of the daily allowance.

The limits, so you never meet one by surprise
LimitFigure
Accounts per IP address5 an hour, 20 a day
Domains per account3, rising to 50 once any one of them is verified
API requests per account600 a minute — a pace limit, not a sending limit
Sending per domainstarts at 10 a day and climbs the warmup ladder
Screening refusalssending pauses at 8 in 24 hours, and lifts by itself

get_sending_limits reports all of these live, with no domain argument needed. Every 429 carries a Retry-After. Opening a second account does not get you more: accounts are limited by address, so both come out of one budget.


For developers: the REST API

Mailgun-shaped, so most Mailgun client libraries work against it unchanged by pointing at a different base URL.

# An account and an API key, in one request

curl -X POST https://ai.agentemaillist.com/v1/accounts \ -d 'email=you@company.com' -d 'password=a sufficiently long password'

Send

curl -X POST https://ai.agentemaillist.com/v3/yourdomain.com/messages \ --user 'api:YOUR_KEY' \ -F from='you@yourdomain.com' \ -F to=someone@example.com \ -F subject='Hello' \ -F text='Hello there.'

Full API reference, written for machines to read: [ai.agentemaillist.com/llms.txt](https://ai.agentemaillist.com/llms.txt). Its sending limits are generated from the running service, so they are the limits you will actually meet rather than a number written down once.

There is also a web console at ai.agentemaillist.com/signup for setting up a domain by hand.


What it does

  • Free SMTP relay and email API. No trial clock, no card.
  • Send over SMTP or REST. Adding a domain issues SMTP credentials; the REST API is Mailgun-shaped.
  • Receive mail too. A real SMTP server on port 25, with inbound routing to your webhook. Not just sending.
  • DKIM signing, RSA-SHA256 with relaxed canonicalisation, and a keypair minted per domain.
  • Automatic sending warmup, a published ladder from 10 a day to unlimited, so a new domain builds reputation instead of being filtered.
  • Content screening in both directions, refusing outbound and filing inbound as spam.
  • Delivery events for every message, plus signed webhooks.
  • Limits that open as you prove yourself, rather than a flat cap: verifying a domain is what buys headroom, because it is the one thing a throwaway account cannot fake at scale.

Compared to the alternatives

ThisMailgunSendGridAmazon SES
An agent can sign up aloneYesNoNoNo
MCP serverYesNoNoNo
Free tierFree, no clockLimitedTrial, then paidPay per message
Inbound mailYesYesYesVia S3
Self-hostableYesNoNoNo

A longer comparison, including Brevo, Resend and SMTP2GO, is at ai.agentemaillist.com/free-smtp-relay.

Self-hosting

It is one Phoenix application and a Postgres database. One command deploys it:

sudo bash deploy/deploy.sh --domain mail.yourcompany.com --email you@company.com

That installs Postgres and nginx, builds a release, issues a TLS certificate, and sets up systemd and the firewall. DEPLOY.md explains every step it takes and what to do when one fails.

Licence

Currently unlicensed, which means all rights reserved. If you want to use or contribute to this, say so and a licence will be added.

Maintained by Logan Besecker. Questions, bug reports and cold outreach all welcome at or .


Running and operating it

Everything below is for someone running their own copy.

Running it

mix setup            # deps, database, migrations

mix phx.server # http://localhost:4005 mix test

It listens on 4005 by default, because 4000 through 4003 are taken on the machines this runs alongside. PORT overrides it.

Database

Set credentials once, in .env at the project root:

cp .env.example .env

Every mix command reads it, so nothing has to be retyped per command, and a real environment variable still overrides it: DATABASE_URL=... mix test does what it looks like. .env is gitignored; .env.example lists everything that can go in it.

Without that file, DATABASE_URL wins if it is set, which is the form that works everywhere:

DATABASE_URL=ecto://user:pass@localhost/email_provider_dev mix setup

Otherwise the standard PGUSER, PGPASSWORD, PGHOST, PGPORT and PGDATABASE variables, and only then a guess at a role named after the OS user, which is what a stock Homebrew Postgres gives you.

The guess skips the OS user when that user is root. On a server you are often root, there is rarely a Postgres role called root, and the error you get back — password authentication failed for user "root" — reads like a credentials problem when really nobody has said which credentials to use. If you hit that on a fresh box, either set DATABASE_URL or create the role:

sudo -u postgres psql -c "CREATE ROLE youruser LOGIN PASSWORD 'apassword' CREATEDB;"

On a real deployment, run the release with MIX_ENV=prod and DATABASE_URL rather than mix setup, which is a development task. One command does the whole thing, and DEPLOY.md explains every step it takes:

sudo bash deploy/deploy.sh --domain ai.agentemaillist.com --email you@example.com
On a machine that is running other things

mix setup is a developer command and it is not a good neighbour. Use this instead:

DATABASE_URL=ecto://user:pass@localhost/email_provider_dev bin/setup-server

Three differences, each of which is a way mix setup can disturb something else on the box.

It caps the build. Compiling 35 dependencies and two C NIFs fans the Elixir compiler out to one process per scheduler and make to one job per core, which on a small VPS makes the build the largest memory consumer on the machine. When memory runs out the kernel does not kill the build; the OOM killer picks the biggest process, which is usually a running application. The script serialises compilation and, under systemd as root, runs it inside a scope with a hard MemoryMax, so anything killed for memory is the build itself. Override with MEMORY_MAX=1G.

It opens two connections, not ten. Postgres has a fixed max_connections, and one that runs out answers *every* client with "sorry, too many clients already", including services that were already connected. The dev pool now defaults to 5 and reads POOL_SIZE; the script sets it to 2.

It never starts the application. mix setup boots the whole supervision tree to run priv/repo/seeds.exs, which opens a pool and starts the delivery queue. mix setup.server creates and migrates without booting anything.

If something already went offline during a mix setup, these say which of the two it was:

sudo dmesg -T | grep -i -A2 'killed process'
sudo grep -i "too many clients" /var/log/postgresql/*.log | tail
A note on PGDATABASE

Host, user and password are read from the environment. The database name is not. It is not a credential, it is which application's data this is, and PGDATABASE is a standard libpq variable that may already be exported on a shared box for some other service. Honouring it would point mix ecto.migrate at that service's database and create this application's tables inside it. To use a different database, name it in DATABASE_URL.

Environment
VariableMeaningDefault
OPENAI_API_KEYKey for the moderation endpointnone — screening is skipped
SSA_UIDSeriouslySimpleAnalytics account id for adoption reportingunset — nothing is reported
MODERATION_ENABLEDTurn screening off entirelytrue
MODERATION_ON_ERRORblock to fail closed when screening is unreachableallow
SMTP_RELAYSmarthost for outbound mailunset — mail is written to priv/local_mail
SMTP_PORT / SMTP_USERNAME / SMTP_PASSWORDSmarthost credentials587, none
SPF_HOSTWhat customers put in their SPF includemail.example.com
MX_HOSTWhat customers point their MX atmx.example.com

Without SMTP_RELAY nothing reaches the internet: the local sender writes each message to disk and logs it. That is the default on purpose.

Accounts and keys

curl -s localhost:4005/v1/accounts \

-d email=you@example.com -d password='a sufficiently long password'

The response carries an API key. It is shown once — only a SHA-256 hash is stored, so a lost key is rotated rather than looked up. Authenticate either way:

curl -s --user 'api:ep_live_...' localhost:4005/v3/domains     # Mailgun style

curl -s -H 'Authorization: Bearer ep_live_...' localhost:4005/v3/domains

Keys carry scopes (messages:send, events:read, domains:write, …). Scopes are declared per action in each controller, next to the code they guard.

Custom domains

Adding a domain generates an RSA-2048 DKIM keypair. The private half stays in the database; the public half is what the customer publishes.

curl -s --user 'api:KEY' localhost:4005/v3/domains -d name=mail.yourcompany.com

The response lists the records to publish, then:

curl -s -X PUT --user 'api:KEY' localhost:4005/v3/domains/mai

只显示了开头部分;其余内容请在仓库中阅读