Cold Leads vs Hub MCP
A side-by-side look at the Cold Leads and Hub MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
C
Cold LeadsDeveloper Tools · Local subprocess (stdio)B2B outreach CRM for AI agents: contacts, verification, approved campaigns, replies, follow-ups.53GoodAuth: api key requiredVerdict: choose Cold Leads for developer tools work as a local process; choose Hub MCP for developer tools over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
CChoose Cold Leads when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
COLDLEADS_API_KEY, COLDLEADS_API_BASE. - You want tools like
verify_email, search_leads, provision_account_and_get_payment_link.
Choose Hub MCP when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
HUB_PAT_TOKEN, MCP_AUTH_TOKEN. - You want tools like
search, query, architectures.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | C Cold Leads | |
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 53/100 · Good | 77/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | API key required |
| Pricing | Not declared | Free |
| Required env vars | COLDLEADS_API_KEYCOLDLEADS_API_BASE | HUB_PAT_TOKENMCP_AUTH_TOKEN |
| Verified owner | Community listing | Verified |
| GitHub stars | 0 | 170 |
| Directory activity | 0 views 0 installs 0 upvotes | 39 views 0 installs 0 upvotes |
| Tools | 4 | 35 |
| Full listing | View Cold Leads | View Hub MCP |
Tools & capabilities
Cold Leads tools 4
verify_emailVerification of one address: syntax, disposable domain, role account and MX records, plus an SMTP mailbox and catch-all check when Cold Leads can open an SMTP connection to the recipient's mail server (otherwise `reasons` contains `smtp_unreachable` and `catch_all` is `null`). Returns `valid`, `ris…search_leadsContacts already in your Cold Leads CRM for a company domain, with an optional role keyword: e-mail, name, company, stage, tags, verification status and a `do_not_contact` flag. Cold Leads has no third-party lead database.provision_account_and_get_payment_linkFor agents without a key: creates a pending account for the human owner and returns a Stripe payment link for the Business plan. The human decides and pays.check_provisioning_statusAfter the owner paid: returns the API key exactly once (with the `claim_token`). The server starts using it immediately.
Hub MCP tools 35
searchSearch repositories and content using Search V4 APIquerySearch query parameter (string, required)architecturesFilter on architectures (string, optional)badgesFilter by image content type badges (string, optional)categoriesFilter on categories (string, optional)extension_reviewedFilter on reviewed extensions (boolean, optional)fromNumber of documents to skip for pagination (number, optional)imagesFilter on image names (string, optional)operating_systemsFilter on operating systems (string, optional)orderChange the ordering of results (string, optional)sizeMaximum number of results to return (number, optional)sortSort results by search field (string, optional)- +23 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Cold Leads
{
"mcpServers": {
"cold-leads": {
"command": "npx",
"args": [
"-y",
"@coldleads/mcp-server"
],
"env": {
"COLDLEADS_API_KEY": "YOUR_COLDLEADS_API_KEY_HERE",
"COLDLEADS_API_BASE": "YOUR_COLDLEADS_API_BASE_HERE"
}
}
}
}
Hub MCP
{
"mcpServers": {
"docker-hub-mcp": {
"url": "https://docs.docker.com/ai/gordon/mcp/yaml/"
}
}
}
Frequently asked questions
Cold Leads is categorized under Developer Tools and uses a local stdio subprocess. Hub MCP belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick Cold Leads for developer tools work and Hub MCP for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Cold Leads has no declared pricing — check the project's own site. Auth: api key required. Hub MCP is listed as free. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add cold-leads and docker-hub-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Cold Leads has a quality signal of 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars. Hub MCP has 77/100 (Great) with 39 views, 0 installs and 170 GitHub stars.