The GTM MCP Directory
Directory / Email Deliverability / InboxAlly

InboxAlly

No MCP found Paid, self-serve Email Deliverability RESEARCHED Checked 2026-09-02 CLI: inboxally
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: 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-09-02.

mcp_status, verbatim from the file:

none-found

mcp_url, verbatim from the file:

n/a

Command line
Binary
inboxally
Status
official CLI, first party
Strongest evidence
npm
Harvested
2026-09-27

Install, as the source shows it:

npm install -g @inboxally/cli

quoted from https://www.npmjs.com/package/@inboxally/cli on 2026-09-27, via npm

Packages seen, with the version on 2026-09-27:

A CLI being listed means the harvest found an install command or a package on a stated date. Nobody has run it. Every command is quoted verbatim from the URL beneath it. Harvest date 2026-09-27.

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 (a fully documented REST API is available on every plan, but there is no free tier - the cheapest self-serve entry is Starter at $149/mo)

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/InboxAlly tied to the vendor by rule 3, account website www.inboxally.com 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-06-03

The five most recently pushed, on 2026-09-08:

RepositoryKindDescriptionStarsPushedLatest release
ia-static-assetsotherpublic repo of misc static assets02026-06-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

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

4 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, https://www.inboxally.com/pricing

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. [api_gate 2026-08-25] Reclassified unknown -> paid from the vendor's own page (https://www.inboxally.com/pricing): a fully documented REST API is available on every plan, but there is no free tier - the cheapest self-serve entry is Starter at $149/mo. 2026-09-02: re-checked inboxally.com/llms.txt (served a product page, no MCP mention) and web search; no MCP server found.
Provenance
Entry id
09-inboxally
Source file
09-email-deliverability.md
Source line
64
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.