What is the key difference between MCP Domain Deliverability Checker and Opus Growth?

MCP Domain Deliverability Checker belongs to the Marketing category with local stdio execution, while Opus Growth belongs to the Marketing category with cloud HTTP/SSE execution.

How do I install MCP Domain Deliverability Checker or Opus Growth in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are MCP Domain Deliverability Checker and Opus Growth free or paid?

MCP Domain Deliverability Checker operates under a BYOK (Pay Provider Direct) model (API Key required). Opus Growth operates under a Freemium model (OAuth 2.0).

Which MCP server has more tools and community activity?

MCP Domain Deliverability Checker lists 1 tools with 1 views and 1 GitHub stars. Opus Growth lists 6 tools with 4 views and 0 GitHub stars.

Can I use both MCP Domain Deliverability Checker and Opus Growth together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

MCP Domain Deliverability Checker vs Opus Growth

In-depth architectural comparison of the MCP Domain Deliverability Checker and Opus Growth MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

MCP Domain Deliverability Checker

Marketing · Local stdio

Quality: 63/100 (Good) | Auth: API Key required

Opus Growth

Marketing · Remote HTTP/SSE

Quality: 75/100 (Great) | Auth: OAuth 2.0

Verdict Summary: Choose MCP Domain Deliverability Checker if you need specialized Marketing tools running via a local process. Choose Opus Growth if your workspace requires Marketing integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose MCP Domain Deliverability Checker when:

You need dedicated capabilities in the Marketing domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: APIFY_TOKEN.
Primary tools included: check_domain_deliverability.

Explore MCP Domain Deliverability Checker Details

Choose Opus Growth when:

You need dedicated capabilities in the Marketing domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: OAuth 2.0 (Freemium).
Primary tools included: Hosted MCP endpoint, Google OAuth sign-in, Five supported advertising platforms.

Feature & Specification Comparison

Specification	MCP Domain Deliverability Checker mambalabsdev Marketing	Opus Growth VerifiedMarketing
Summary	Audits a domain email deliverability: SPF, DKIM, DMARC, MX, mail provider, DNS blacklist, catch-all, and domain age, returning a 0-100 health score via an Apify actor.	Hosted, OAuth-protected MCP server for advertising operations. One connector covers Google Ads, Meta Ads, Microsoft Advertising, TikTok Ads and LinkedIn Ads, plus Search Console, GA4, YouTube, Tag Manager and Google Business Profile. Every write returns a dry-run preview and is applied only after explicit confirmation.

Tools & Capabilities Breakdown

MCP Domain Deliverability Checker Tools (1)

check_domain_deliverability

Audit a domain's email deliverability and DNS health. Returns SPF, DKIM, and DMARC authentication with policy, MX records and mail provider, DNS blacklist status, catch-all detection, domain age, and a 0 to 100 health score as a flat, Clay-ready JSON row. Read-only; requires an APIFY_TOKEN and consumes Apify credits per call.

Opus Growth Tools (6)

Hosted MCP endpoint

Google OAuth sign-in

Five supported advertising platforms

Connected Google marketing data sources

Dry-run previews for every write

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

MCP Domain Deliverability Checker Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "mambalabsdev-mcp-domain-deliverability-checker": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-domain-deliverability-checker"
      ],
      "env": {
        "APIFY_TOKEN": "YOUR_APIFY_TOKEN_HERE"
      }
    }
  }
}

Opus Growth Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "opus-growth": {
      "url": "https://mcp.opus-growth.com/mcp"
    }
  }
}

Frequently Asked Questions

MCP Domain Deliverability Checker is categorized under Marketing and uses a local stdio subprocess. In contrast, Opus Growth belongs to Marketing using remote streaming HTTP/SSE transport. Select MCP Domain Deliverability Checker when you need capabilities focused on marketing and Opus Growth when you require tools for marketing.

More alternatives to MCP Domain Deliverability Checker More alternatives to Opus Growth Marketing category hub