DiviMail

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 电脑或云端
• 传输方式: stdio, Streamable HTTP
• 分类: 聊天与邮件
• 你需要填写：DIVIMAIL_SERVICE_SECRET

安装

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

你需要

• 在云端运行无需安装任何东西，通过互联网连接
• npm已安装 Node.js（用于 npx 命令）

你用的是哪个应用？

https://mcp.divindi.io/mcp

{
  "mcpServers": {
    "divimail": {
      "command": "npx",
      "args": [
        "-y",
        "@divindi/divimail-mcp"
      ],
      "env": {
        "DIVIMAIL_SERVICE_SECRET": "your-value"
      }
    }
  }
}

claude mcp add --transport http divimail https://mcp.divindi.io/mcp

claude mcp add divimail --env DIVIMAIL_SERVICE_SECRET=your-value -- npx -y @divindi/divimail-mcp

{
  "mcpServers": {
    "divimail": {
      "url": "https://mcp.divindi.io/mcp"
    }
  }
}

{
  "mcpServers": {
    "divimail": {
      "command": "npx",
      "args": [
        "-y",
        "@divindi/divimail-mcp"
      ],
      "env": {
        "DIVIMAIL_SERVICE_SECRET": "your-value"
      }
    }
  }
}

{
  "servers": {
    "divimail": {
      "type": "http",
      "url": "https://mcp.divindi.io/mcp"
    }
  }
}

{
  "servers": {
    "divimail": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@divindi/divimail-mcp"
      ],
      "env": {
        "DIVIMAIL_SERVICE_SECRET": "your-value"
      }
    }
  }
}

https://mcp.divindi.io/mcp

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

• DIVIMAIL_SERVICE_SECRET 机密 env
  Optional. Only for scheduled agents that use divimail_service_token. Most agents leave it unset and use divimail_register then divimail_login.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

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

• divimail_register

  Give an AI agent its own @divindi.io email address so it can send and receive email. Call this once to create the address. Then sign in: through the app's connection sign-in if you are using one, otherwise with divimail_login (or divimail_challenge + divimail_authenticate). Use e

• divimail_send

  Send an email from your agent's @divindi.io address to any email address, human or agent. When connected through an app sign-in, no token or address is needed. If the balance is low, see divimail_balance and divimail_request_topup. Costs $0.01 USDC per email. Supports plain text,

• divimail_inbox

  Check your agent's inbox: lists received emails for its @divindi.io address. Call this first to see what arrived, then use divimail_read with a messageId for the full content, and divimail_mark_read when done. For mail the agent sent, use divimail_sent. When connected through an

• divimail_sent

  See what emails your agent has sent: lists sent messages for its @divindi.io address. Use this to confirm a divimail_send went out or to review history. For received mail use divimail_inbox. When connected through an app sign-in, no token or address is needed. Optional limit (def

• divimail_read

  Open and read one email in full (body and details) from your agent's mailbox. Call after divimail_inbox using a messageId from that list; then call divimail_mark_read if you want it marked read. When connected through an app sign-in, no token or address is needed.

• divimail_mark_read

  Mark an email in your agent's inbox as read so it is not handled twice. Use after divimail_read (or divimail_inbox) with the same messageId. When connected through an app sign-in, no token or address is needed.

• divimail_balance

  Check how much USDC a DiviMail address has for sending email or paying. Call before divimail_send or divimail_pay if unsure; if low, use divimail_request_topup. No token needed, just the @divindi.io address.

基础检查i

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

• ! 注意

  作者与仓库一致

  注册中心没有列出源代码仓库，因此无法将发布者（divindi.tech）与代码对应起来

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 247 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

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

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

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

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

替代选择

同一分类中其他作者的服务器，按星标数排序。

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

作者的 README

仓库中没有找到 README