# Allegrow: MCP server status, API access gate and what it does > B2B email verification and deliverability platform - resolves catch-all/secure-email-gateway addresses that... Official MCP, Paid, self-serve. 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) / Allegrow # Allegrow [Official MCP](../mcp/official.md) [Paid, self-serve](../gates/paid.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: [allegrow.co](https://allegrow.co) · entry id 09-allegrow · source 09-email-deliverability.md line 102 **What it does** B2B email verification and deliverability platform - resolves catch-all/secure-email-gateway addresses that legacy verifiers mark "unknown," sends warm-up email to real B2B accounts, and runs hourly SPF/DKIM/DMARC checks with a "Safety Net" that auto-pauses sends to addresses likely to mark mail as spam. **AI features, separated from automation with an AI label on it** No AI-specific model capability confirmed in sourced pages; the differentiator (resolving catch-all/SEG addresses, hourly authentication monitoring, automatic send-pausing) is rules-based verification and monitoring logic, not disclosed as model-driven. **RevOps role** Email-verification-plus-deliverability layer aimed at list hygiene before and during outbound sends, with warm-up as a secondary feature rather than its primary product. **MCP server** - **Status bucket**: Official MCP - **Auth**: OAuth - connects through Claude's standard connector authorization flow; user logs into their Allegrow account and grants access explicitly (no manual API key copying). - **Parsed URLs**: 1 found in the mcp_url field The vendor ships and maintains the server itself. A wrapper built by Zapier, Composio or a similar third party does not count as official. The status was established on 2026-08-24 and has not been re-fetched since. mcp_status, verbatim from the file: official mcp_url, verbatim from the file: https://www.allegrow.co/knowledge-base/claude-email-mcp - [https://www.allegrow.co/knowledge-base/claude-email-mcp](https://www.allegrow.co/knowledge-base/claude-email-mcp) **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 - credit-based model (one credit per unique address verified); a 14-day free trial covers up to 1,000 contacts, full pricing not published. **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** - [Verify an email is deliverable](../jobs/verify-email-deliverable.md) - [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.allegrow.co/knowledge-base/claude-email-mcp](https://www.allegrow.co/knowledge-base/claude-email-mcp) - [https://www.allegrow.co/knowledge-base/complete-guide-to-email-warm-up-tools-which-increase-sender-reputation](https://www.allegrow.co/knowledge-base/complete-guide-to-email-warm-up-tools-which-increase-sender-reputation) - [https://emailwarmup.com/blog/email-deliverability-tools/allegrow-review/](https://emailwarmup.com/blog/email-deliverability-tools/allegrow-review/) 3 source URLs. Raw sources field, verbatim: https://www.allegrow.co/knowledge-base/claude-email-mcp, https://www.allegrow.co/knowledge-base/complete-guide-to-email-warm-up-tools-which-increase-sender-reputation, https://emailwarmup.com/blog/email-deliverability-tools/allegrow-review/ **Notes, verbatim from the file** Vendor-published on Allegrow's own domain and listed in Claude's connector directory (claude.ai/directory/allegrow) - clears this schema's bar for "official" since Allegrow built and documents it themselves. Worth noting Claude's own directory UI labels it a "community connector" (meaning it passed Anthropic's automated review but isn't Anthropic-verified) - a different axis than this schema's official/community distinction, which tracks who built the server, not who verified it. **Provenance** - **Entry id**: 09-allegrow - **Source file**: 09-email-deliverability.md - **Source line**: 102 - **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).