ToolsMCP
email-outreach
Listed in the official MCP Registry with a hosted streamable-http endpoint. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- openhelm.ai
- Prerequisites
- An MCP client that supports streamable-http. No credential header is declared in the registry record.
- Current version
- 0.1.0 · updated
- Official links
Publisher’s description
Goal-directed email outreach: research, draft, send, triage replies. Real data, never fabricated.
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.0, registry status active. 1 remote endpoint (streamable-http)
Publisher-supplied registry metadata. Not a checked connection, a safe package or a completed task.
- Source publisher
- openhelm.ai
- Version observed
- 0.1.0
- Source
- registry.modelcontextprotocol.io/v0.1/servers/ai.openhelm%2Femail-outreach/versions/0.1.0
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Read, draft and send email | Publisher description mentions “email”, “draft”, “send”, “triage”, “replies”. | No connection check or task run. Capability is as described by the publisher. | Rule email matched: “email”, “draft”, “send”, “triage”, “replies”. 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
- Remote endpoints
https://mcp.openhelm.ai/email/mcp(streamable-http)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
ai.openhelm/email-outreach
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.