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