coldsend-mcp
https://mcp.coldsend.pro/mcp ↗
Description
AI-native cold email campaign management via Model Context Protocol. ## What You Can Do - **Campaigns** — Create, launch, pause, resume, and delete email campaigns with full lifecycle control - **Leads** — Upload leads from CSV, list, filter, and manage recipients per campaign - **Sender Accounts** — Configure ColdSend native, SMTP, Google Workspace, and Outlook 365 inboxes - **Domains** — Add custom sending domains with automated DNS verification and activation tracking - **Analytics** — Track delivery rates, open/click engagement, reply rates, and compare campaigns side-by-side - **Inbox Health** — Monitor sender reputation, bounce rates, and deliverability scores ## Authentication Pass your ColdSend API key via the `X-API-Key` header. Get your key from [cloud.coldsend.pro](https://cloud.coldsend.pro). ## Transports - Streamable HTTP (`/mcp`)
What our measurements say
coldsend-mcp is a remote MCP server published at mcp.coldsend.pro. It has been probed 7 times since 9/10/2026. It answered in 7 of them (100.0%), a near-uninterrupted record. Median response time is 673 ms, a delay an agent will notice. It exposes a broad tool surface of 65 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Agent readability score
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
Agent readability score
Strengths
- Tool names follow a consistent naming convention (resource.action) that clearly indicates purpose
- Some descriptions include detailed usage scenarios and implementation steps
Weaknesses
- Descriptions frequently cut off mid-sentence or lack complete parameter definitions
- Parameter types and requirements are inconsistently documented
- Some tools with similar names (e.g., 'contacts.add_to_campaign' vs 'leads.add_manual') may cause selection ambiguity
campaigns.list— Description cut off mid-sentence without explaining full functionalityleads.upload— CSV format requirements mentioned but parameters lack explicit required/optional indicatorsdomains.add— Verification process described but no error handling details for failed DNS setupcampaigns.update— Parameter 'updates' described as a dict but lacks specific key definitionssender.bulk_create_smtp— Args description lacks clear validation rules for SMTP/IMAP credentials
Verdict
Event narrative
Risk: medium
- 2026-09-10T21:16:35.016Z — Era changed from 'auth-gated' to 'legacy' · Indicates a transition to a legacy system with full compliance
- 2026-09-11T01:59:45.474Z — Compliance score set to 100 · Confirms full compliance with regulations
Advice
Schema compliance
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
- tools/list schema valid
- inputSchema is valid JSON Schema
- Smoke test failed · last run:
- Cold-start: cold 183ms → warm 181ms (penalty 2ms)
Availability history
Event log
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
- Server build: — → 1.29.1
- Supported versions: — → 2025-11-25
- Era changed: Auth-gated → Legacy
- Added to watch — era: Auth-gated
Get your badge
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/pipelinescientists-coldsend-mcp)<a href="https://mcpmetrics.io/servers/pipelinescientists-coldsend-mcp"><img src="https://mcpmetrics.io/badge/pipelinescientists/coldsend-mcp/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see