# InboxAlly: MCP server status, API access gate and what it does > Email warmup and reputation-repair service that adds real seed inboxes into a customer's actual campaigns;... No MCP found, Gate unknown. Checked 2026-08-24. *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).* --- [Directory](../index.md) / [Email Deliverability](../categories/email-deliverability.md) / InboxAlly # InboxAlly [No MCP found](../mcp/none-found.md) [Gate unknown](../gates/unknown.md) [Email Deliverability](../categories/email-deliverability.md) RESEARCHED Checked 2026-08-24 > **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 0. Vendor: [inboxally.com](https://inboxally.com) · entry id 09-inboxally · source 09-email-deliverability.md line 64 **What it does** Email warmup and reputation-repair service that adds real seed inboxes into a customer's actual campaigns; those seed accounts perform browser-level engagement (open, read, reply, mark important, move out of spam) rather than simulated network activity. **AI features, separated from automation with an AI label on it** No AI-specific capability confirmed; the differentiator is human/browser-level interaction versus bot-simulated engagement, which is a design choice, not an AI feature - treat as plain automation. **RevOps role** Deliverability/reputation-repair layer marketed specifically as the safer alternative to network-based automated warmup, positioned against the ToS risk this category carries. **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-08-24 and has not been re-fetched since. mcp_status, verbatim from the file: none-found mcp_url, verbatim from the file: n/a **Access gate** - **Gate bucket**: Gate unknown - **Can a solo operator reach it**: Not established api_gate, verbatim from the file: unknown 83 of 293 entries carry an unknown gate. Unknown is a legal answer and it ships as unknown rather than as a guess. **API documentation** No documentation URL recorded. 263 of 293 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. **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 55 job vocabulary. 271 of 293 entries carry at least one tag; 827 tags are assigned in total. **Sources** - [https://www.inboxally.com/email-warmup-tool](https://www.inboxally.com/email-warmup-tool) - [https://docs.inboxally.com/warm-up-sending-strategy/the-dangers-of-using-an-automated-email-warmup-service/](https://docs.inboxally.com/warm-up-sending-strategy/the-dangers-of-using-an-automated-email-warmup-service/) - [https://www.inboxally.com/blog/gmass-email-warm-up](https://www.inboxally.com/blog/gmass-email-warm-up) 3 source URLs. Raw sources field, verbatim: https://www.inboxally.com/email-warmup-tool, https://docs.inboxally.com/warm-up-sending-strategy/the-dangers-of-using-an-automated-email-warmup-service/, https://www.inboxally.com/blog/gmass-email-warm-up **Notes, verbatim from the file** InboxAlly's own knowledge base publishes "Why are automated email warmup services risky?" - explicitly naming ToS violation/account-suspension risk and citing Google's January 2023 ban on automated warmup for Gmail as the reason GMass shut its warmup feature down. This is the source behind this file's intro-level ToS flag; InboxAlly positions its own real-seed-account approach as the workaround. No MCP server or API developer portal was found for InboxAlly itself. **Provenance** - **Entry id**: 09-inboxally - **Source file**: 09-email-deliverability.md - **Source line**: 64 - **Tier**: RESEARCHED - **last_checked**: 2026-08-24 - **Data baked**: 2026-08-25 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).