ToolsMCP
mcp-server-imap
Listed in the official MCP Registry with an installable npm package. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- aiwerk (GitHub)
- Prerequisites
- Install @aiwerk/mcp-server-imap from npm (stdio transport). Declares 2 secret inputs. Inspect it before installing; AgentsByTask never installs discovered packages.
- Current version
- 1.2.1 · updated
- Official links
Publisher’s description
Email tools for any IMAP/SMTP provider: list, read, search, send, and manage messages.
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 1.2.1, registry status active. 1 package (npm)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- aiwerk (GitHub)
- Version observed
- 1.2.1
- Source
- registry.modelcontextprotocol.io/v0.1/servers/io.github.AIWerk%2Fmcp-server-imap/versions/1.2.1
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Read, draft and send email | Publisher description mentions “imap”, “email”, “read”, “send”. | No connection check or task run. Capability is as described by the publisher. | Rule email matched: “imap”, “email”, “read”, “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
@aiwerk/mcp-server-imap(npm, stdio, 2 secret inputs)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
io.github.AIWerk/mcp-server-imap
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.