# Warmy.io: MCP server status, API access gate and what it does > Email warmup and deliverability platform with an "AI-driven engagement engine" - customizable warm-up... No MCP found, Paid, self-serve. Checked 2026-09-02. *Markdown twin of the HTML page at the same path. Same content, no navigation, no styling, no scripts. Links below point at other twins. Site map for machines: [llms.txt](../llms.txt). The whole dataset: [directory.json](../data/directory.json).* *Maintained by Andrew McGuire (https://andrewcmcguire.com), who also publishes https://gtmsignals.co and https://justsaid.ai.* --- [Directory](../index.md) / [Email Deliverability](../categories/email-deliverability.md) / Warmy.io # Warmy.io [No MCP found](../mcp/none-found.md) [Paid, self-serve](../gates/paid.md) [Email Deliverability](../categories/email-deliverability.md) RESEARCHED Checked 2026-09-02 > **RESEARCHED** Facts from public sources with URLs. No usage claims. Nobody has run this tool. The other tier is BENCH-TESTED, which means Andrew personally ran the tool on a stated date and cannot be bought at any price. Across the whole directory that count is 1. Vendor: [warmy.io](https://warmy.io) · entry id 09-warmy-io · source 09-email-deliverability.md line 235 **What it does** Email warmup and deliverability platform with an "AI-driven engagement engine" - customizable warm-up topic/language selection, works across Gmail, Outlook, Zoho, and Amazon SES, with a real-time webhook/Slack-connected API for adjusting warm-up speed, volume, and timing programmatically. **AI features, separated from automation with an AI label on it** Vendor markets the engagement engine as "AI-driven" and the warmup content as "fully personalized" per message - no independent breakdown of what is model-generated versus templated was found; treat as vendor-stated. **RevOps role** Deliverability-maintenance layer comparable to Mailreach/Warmup Inbox, differentiated on enterprise-sender topic/language customization and webhook-driven programmatic control. **MCP server** - **Status bucket**: No MCP found - **Auth**: n/a - **Parsed URLs**: 0 found in the mcp_url field No server was found at the time of the check. That is a statement about the search, not a promise that none exists. The status was established on 2026-09-02. mcp_status, verbatim from the file: none-found mcp_url, verbatim from the file: n/a **Command line** No CLI found by the 2026-09-27 harvest across vendor docs, npm, PyPI, Homebrew and GitHub. That is a probe result, not proof of absence. **Access gate** - **Gate bucket**: Paid, self-serve - **Can a solo operator reach it**: Yes, by paying, no sales call api_gate, verbatim from the file: paid - API is a distinct product tier ("Warmy API") rather than bundled into every plan by default, per the vendor's own product page. **API documentation** No documentation URL recorded. 727 of 1252 entries are in the same position. Blank is legal and it is published as blank. **GitHub health** Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build. The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale. **On GitHub** [github.com/Warmy-io](https://github.com/Warmy-io) tied to the vendor by rule 3, account website www.warmy.io has the vendor's domain, confidence strong - **Public repositories**: 1, forks excluded, as read on 2026-09-08 - **Mention MCP**: 0 of them - **Look like CLIs**: 0 of them - **Latest push**: 2026-07-03 The five most recently pushed, on 2026-09-08: | Repository | Kind | Description | Stars | Pushed | Latest release | |---|---|---|---|---|---| | [CSM-dashboard](https://github.com/Warmy-io/CSM-dashboard) | app | | 0 | 2026-07-03 | | Kind is a heuristic guessed from the repository name, topics and description, not a fact the vendor stated. A repository count is activity, not a verdict. Read 2026-09-08. **Jobs it can do** - [Warm up an inbox](../jobs/warm-up-inbox.md) A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records. Tagged by machine-pass on 2026-08-25 against the closed 56 job vocabulary. 271 of 1,252 entries carry at least one tag; 849 tags are assigned in total. **Sources** - [https://www.warmy.io/product/api/](https://www.warmy.io/product/api/) - [https://www.warmy.io/product/warm-up-email/](https://www.warmy.io/product/warm-up-email/) - [https://www.warmy.io/blog/best-email-warmup-deliverability-tools-alternatives/](https://www.warmy.io/blog/best-email-warmup-deliverability-tools-alternatives/) - [https://warmysender.com/mcp](https://warmysender.com/mcp) - [https://warmysender.com/](https://warmysender.com/) 5 source URLs. Raw sources field, verbatim: https://www.warmy.io/product/api/, https://www.warmy.io/product/warm-up-email/, https://www.warmy.io/blog/best-email-warmup-deliverability-tools-alternatives/, https://warmysender.com/mcp, https://warmysender.com/ **Notes, verbatim from the file** A search result mentioned a separate, apparently unrelated tool called "mailX" (a free SPF/DKIM/DMARC/blacklist checker) as having "API and MCP access" - that is a different product from Warmy.io and was not pursued further here since it fell outside this file's named seed list; flagged only to avoid future conflation. No MCP server found for Warmy.io itself. 2026-09-02: re-checked, mcp_status stays none-found. A second conflation risk is now documented: the official MCP registry entry com.warmysender/mcp (https://warmysender.com/mcp, 77 tools, streamable HTTP, Bearer ws_ API key or OAuth) belongs to WarmySender, whose own homepage states "WarmySender and Warmy.io are completely separate and unaffiliated companies" that "share no code, data, or ownership". https://www.warmy.io/product/api/ still has no MCP mention. Do not cite WarmySender for Warmy.io. **Provenance** - **Entry id**: 09-warmy-io - **Source file**: 09-email-deliverability.md - **Source line**: 235 - **Tier**: RESEARCHED - **last_checked**: 2026-09-02 - **Data baked**: 2026-09-27 Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the [methodology page](../methodology.md).