In-depth architectural comparison of the Deliveriq MCP and Precleared Contact Check 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
Deliveriq MCP
Communication · Local stdio
Quality: 41/100 (Fair) | Auth: API Key required
Precleared Contact Check
Communication · Remote HTTP/SSE
Quality: 51/100 (Good) | Auth: No auth required
Verdict Summary: Choose Deliveriq MCP if you need specialized Communication tools running via a local process. Choose Precleared Contact Check if your workspace requires Communication integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Deliveriq MCP when:
You need dedicated capabilities in the Communication domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
You have access to required keys: DELIVERIQ_API_KEY.
Takes a recipient email or domain, your sender country (GB or US), the pitch and where the address came from. Returns `verdict` (ok_to_email, consent_needed, blocked or unknown), `confidence`, the rule quoted with its source, `footer_text` (what the email's footer must include, not wording to paste…
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).
Deliveriq MCP is categorized under Communication and uses a local stdio subprocess. In contrast, Precleared Contact Check belongs to Communication using remote streaming HTTP/SSE transport. Select Deliveriq MCP when you need capabilities focused on communication and Precleared Contact Check when you require tools for communication.