Cold Leads
NPM · @COLDLEADS/MCP-SERVER · 2 COMPONENTS
B2B outreach CRM for AI agents: contacts, verification, approved campaigns, replies, follow-ups.
Available components
Last scanned (11 hours ago)
Scores higher than 78% of npm servers
Category CRM and Sales
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to anttka4cz/mcp-server-coldleads). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 9 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 755 tokens (~188/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +4
- Stability: unverified → 0.27 ▲ functional
- 14 Oct 26 +30
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- 13 Oct 26 49
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Oct 2026 · Analysed npm/@coldleads/mcp-server@1.0.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | anttka4cz/mcp-server-coldleads |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/anttka4cz/mcp-server-coldleads/.github/workflows/publish.yml@refs/tags/v1.0.2 |
| Rekor log index | 3245359036 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:0919b1a913345c782c1c4018a9760a7672f4ed87e329c8e79c1c24ecca7497731056d89a4b3e7764cdcc84f5981c4d05a97e07b7ac70ee5bdf9a6a849 |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_provisioning_status Check the owner's payment and get the API key ~118
Checks an account created with provision_account_and_get_payment_link. Returns status pending_payment, active, expired or suspended. When active, the first call with the claim_token returns api_key exactly once: store it securely as COLDLEADS_API_KEY and send it as Authorization: Bearer <key>. Poll every 15–30 seconds while pending_payment.
| Name | Type | Req | Description |
|---|---|---|---|
| claim_token | string | yes | claim_token returned by provision_account_and_get_payment_link. |
| session_id | string | yes | session_id returned by provision_account_and_get_payment_link. |
No output schema declared.
No examples provided.
provision_account_and_get_payment_link Set up Cold Leads for the human owner ~200
Use only when no working Cold Leads API key is available (other Cold Leads tools return missing_api_key or bad_api_key) and the human wants to use Cold Leads. Creates a pending Cold Leads account for the human owner's e-mail and returns a Stripe payment link for the Business plan with API access (price in plan.price, billed monthly until cancelled). Show checkout_url to the human and let them decide; never open, pay or share the link yourself. Keep claim_token secret, then call check_provisioning_status until status is active to receive the API key once.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Name of your agent or product; shown to the human on the payment page. |
| callback_url | string | – | Optional https URL that receives a signed POST when the owner has paid (no secrets in the payload). |
| owner_email | string | yes | E-mail address of the human who will own and pay for the Cold Leads account. |
No output schema declared.
No examples provided.
search_leads Search leads by company domain ~154
Search the leads already in your Cold Leads CRM for a target company domain: contact e-mail, name, company, phone, stage, tags, verification status and a do_not_contact flag. Covers only contacts in your own workspace (Cold Leads has no third-party lead database). Free, uses no credits.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Company domain, e.g. example.com. A URL or an e-mail address is reduced to its domain. |
| limit | integer | – | Maximum number of leads to return (1–50, default 10). |
| role | string | – | Optional keyword such as sales, ceo or marketing, matched against the contact's name, e-mail local part, tags, notes and type. |
No output schema declared.
No examples provided.
verify_email Verify an e-mail address ~108
Verifies an e-mail 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 validity (valid, risky or invalid), a score and reason codes. Usually answers within a few seconds; costs 1 credit.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The e-mail address to verify, e.g. anna@example.com. |
No output schema declared.
No examples provided.
How do I install the Cold Leads MCP server?
Cold Leads runs locally as an npm package, launched with npx -y @coldleads/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @coldleads/mcp-server
claude mcp add anttka4cz-mcp-server-coldleads -- npx -y @coldleads/mcp-server
What is the Cold Leads MCP server?
Cold Leads is an MCP server listed in the public MCP registry as io.github.anttka4cz/mcp-server-coldleads. B2B outreach CRM for AI agents: contacts, verification, approved campaigns, replies, follow-ups. This page covers its npm package (@coldleads/mcp-server).
Is the Cold Leads MCP server safe to use?
Cold Leads scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Cold Leads MCP server expose?
Cold Leads exposes 4 tools: search_leads, verify_email, provision_account_and_get_payment_link, check_provisioning_status. Their descriptions and schemas cost roughly 580 tokens of context every time the server is loaded.
Is the Cold Leads MCP server still maintained?
Cold Leads is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Cold Leads MCP server under?
Cold Leads declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.