ToolsMCP
FlareMail
Listed in the official MCP Registry with a hosted streamable-http endpoint. Capabilities below are the publisher’s own description.
- Type
- MCP server
- Publisher
- sendwithflare.com
- Prerequisites
- An MCP client that supports streamable-http. No credential header is declared in the registry record.
- Current version
- 1.0.0 · updated
- Official links
Publisher’s description
Read, search, draft, and send email from a FlareMail inbox.
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.0.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
- sendwithflare.com
- Version observed
- 1.0.0
- Source
- registry.modelcontextprotocol.io/v0.1/servers/com.sendwithflare%2Fflaremail/versions/1.0.0
Listed for these tasks
| Task | Documented for this task | Unknowns | Why it is listed |
|---|---|---|---|
| Read, draft and send email | Publisher description mentions “email”, “inbox”, “read”, “draft”, “send”. | No connection check or task run. Capability is as described by the publisher. | Rule email matched: “email”, “inbox”, “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
- Remote endpoints
https://flaremail-api.tcrxx0.workers.dev/mcp(streamable-http)- Registry entry
- Official MCP Registry record (JSON)
- Namespace
com.sendwithflare/flaremail
AgentsByTask never installs discovered packages or connects to discovered endpoints during discovery. An endpoint string in a registry record is not a checked connection.