MCP Domain Deliverabi… vs Google Tag Manager MC… | AllMCPs
Side-by-Side Model Context Protocol Comparison
MCP Domain Deliverability Checker vs Google Tag Manager MCP Server
In-depth architectural comparison of the MCP Domain Deliverability Checker and Google Tag Manager MCP Server 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
Google Tag Manager MCP Server
Marketing · Local stdio
Quality: 60/100 (Good) | Auth: OAuth 2.0
Verdict Summary: Choose MCP Domain Deliverability Checker if you need specialized Marketing tools running via a local process. Choose Google Tag Manager MCP Server if your workspace requires Marketing integration with local subprocess execution. 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)).
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.
This server supports remote MCP connections, includes built-in Google OAuth, and provide an interface to the Google Tag Manager API.
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.
Google Tag Manager MCP Server Tools (6)
18 Google Tag Manager MCP tools
Hosted remote HTTP server
Built-in Google OAuth for hosted use
Local stdio CLI
Service account, refresh token, and access token authentication
Shared tool schemas across hosted and local modes
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 is categorized under Marketing and uses a local stdio subprocess. In contrast, Google Tag Manager MCP Server belongs to Marketing using local stdio subprocess. Select MCP Domain Deliverability Checker when you need capabilities focused on marketing and Google Tag Manager MCP Server when you require tools for marketing.