# Warmup Inbox: MCP server status, API access gate and what it does > Email warmup and deliverability platform running a network of 30,000+ real inboxes that exchange... No MCP found, Free to start. 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) / Warmup Inbox # Warmup Inbox [No MCP found](../mcp/none-found.md) [Free to start](../gates/free.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: [warmupinbox.com](https://warmupinbox.com) · entry id 09-warmup-inbox · source 09-email-deliverability.md line 26 **What it does** 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. **AI features, separated from automation with an AI label on it** No AI-specific capability confirmed; the warmup mechanic and blacklist monitoring read as automation, not model-driven analysis - treat as plain automation absent further evidence. **RevOps role** Deliverability-maintenance layer running behind an outbound sending tool, with programmatic control over creating/connecting inboxes and pulling placement metrics. **MCP server** - **Status bucket**: No MCP found - **Auth**: n/a for MCP. The REST API uses API-key authentication per the vendor's own docs (api.warmupinbox.com/api-doc, OpenAPI 3.0 spec). - **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**: Free to start - **Can a solo operator reach it**: Yes, without talking to anyone api_gate, verbatim from the file: free - the vendor states the API is "a free feature on every plan, with no extra charge." **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** No GitHub organisation could be tied to warmupinbox.com with evidence on 2026-09-08. Recorded by the harvest: github candidates were seen but none passed the evidence rules. 1 candidate account seen and rejected by the evidence rules: norbelys-com. A name match alone is never accepted; the account has to point at the vendor domain. **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.warmupinbox.com/blog/product-updates/product-update-new-api/](https://www.warmupinbox.com/blog/product-updates/product-update-new-api/) - [https://api.warmupinbox.com/api-doc](https://api.warmupinbox.com/api-doc) - [https://documenter.getpostman.com/view/6493518/2s9YR3dFfb](https://documenter.getpostman.com/view/6493518/2s9YR3dFfb) - [https://www.warmupinbox.com/](https://www.warmupinbox.com/) 4 source URLs. Raw sources field, verbatim: 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/ **Notes, verbatim from the file** 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. **Provenance** - **Entry id**: 09-warmup-inbox - **Source file**: 09-email-deliverability.md - **Source line**: 26 - **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).