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

Email warmup and deliverability platform running a network of 30,000+ real inboxes that exchange natural-looking email (opens, replies, stars) with a customer's connected accounts to build sender reputation.

## MCP links

## Sources
- https://www.warmupinbox.com/blog/product-updates/product-update-new-api/
- https://api.warmupinbox.com/api-doc
- https://documenter.getpostman.com/view/6493518/2s9YR3dFfb
- https://www.warmupinbox.com/

## Research notes
The vendor's own product-update blog post states Warmup Inbox is "SOC 2 compliant, with an API, MCP server, and CLI for automating warm-up across hundreds of domains" - a first-party claim on the vendor's own domain. However, a direct fetch of that page timed out and no dedicated MCP docs page, repo, or registry listing was independently reachable to confirm the claim, so this is left as unknown rather than official per the schema's "no URL, no claim" law - worth a follow-up hand-check. 2026-09-02: mcp_status unknown -> none-found. The hand-check happened: https://www.warmupinbox.com/blog/product-updates/product-update-new-api/ loaded today and the string MCP does not appear anywhere in its HTML (raw grep, zero matches); the post now describes only the REST API. The homepage has no MCP mention either, and the official MCP registry returns zero hits for warmup inbox. The earlier first-party MCP sentence is no longer on the vendor's page, so the claim is unsupported and the status is none-found. The blog URL is kept in sources as the record of what was once claimed.

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