ToolsMCP
emperor-mail
Listed in the official MCP Registry with an installable cargo package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- yarenty (GitHub)
- Prerequisites
- Install emperor-mail from cargo (stdio transport). Declares 2 secret inputs. Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 0.1.3 · updated
- Official links
Publisher’s description
Email over IMAP and SMTP: search and read messages and attachments; draft and send when switched on
Evidence
Each record keeps its own date and scope. Labels are independent: documentation does not imply a checked connection, and a connection does not imply a passed task.
-
Listed in the official MCP Registry
Version 0.1.3, registry status active. 1 package (cargo)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- yarenty (GitHub)
- Version observed
- 0.1.3
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.yarenty%2Femperor-mail/versions/0.1.3
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Read, draft and send email | Publisher description mentions “email”, “imap”, “read”, “draft”, “send”. | No connection check or task run. Capability is as described by the publisher. | Rule email matched: “email”, “imap”, “read”, “draft”, “send”. Rule email. |
Published pricing
No published price recordedCost per completed task is only shown on a task page when a comparable run recorded metered spend and verified completions.
Registry record
- Packages
emperor-mail(cargo, stdio, 2 secret inputs)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.yarenty/emperor-mail
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.