# Warmy.io
ID: 09-warmy-io
Page: https://gtmmcps.com/tools/09-warmy-io
JSON: https://gtmmcps.com/data/tools/09-warmy-io.json
Documentation references: https://gtmmcps.com/docs/09-warmy-io/
Category: Email Deliverability
MCP support: none-found
Testing: RESEARCHED
API access: paid
Last checked: 2026-09-02
Endpoint check: not-applicable; date: Not recorded

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.

## MCP links

## Sources
- 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/

## Research notes
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.

## Named capabilities
Tool names below are reported by sources. Their presence is not a successful call.

## CLI evidence
Status: none-found

Read current vendor documentation before configuring or running commands.