SalesBlink Cold Email
MCPB · COLD-EMAIL-SALESBLINK.MCPB · 2 COMPONENTS
Cold email sequences, leads, templates, senders, inbox, and analytics via the SalesBlink API.
Available components
Last scanned (9 hours ago)
Scores higher than 78% of MCPB servers
Category Marketing and SEO
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 Security23
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs were checked across the 92 of 92 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 11 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 635 tokens (~105/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 24 Oct 26 48
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 5 Nov 2026 · Analysed mcpb/https://github.com/open-salesblink/skill/releases/download/v1.2.0/cold-email-salesblink.mcpb@1.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| 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 →
salesblink_check_auth Verify API Key ~34
Verify the configured SalesBlink API key by calling GET /account/verify. Returns account info when the key is valid.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
salesblink_get SalesBlink API GET ~152
Make a read-only GET request to the SalesBlink public API (https://run.salesblink.io/api/public/v1.0.0). Use salesblink_get_reference_doc to look up exact endpoints, query parameters, and gotchas before calling this. Example: path=/lists, query={ limit: 100, skip: 0 }.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Relative API path starting with /, e.g. /sequences or /lists/550e8400-e29b-41d4-a716-446655440000. URL-encode messageIds in paths. |
| query | object | – | Query string parameters, e.g. { limit: 100, skip: 0 } |
No output schema declared.
No examples provided.
salesblink_get_reference_doc Read API Reference Doc ~78
Read a bundled SalesBlink API reference doc: exact endpoints, request/response shapes, and gotchas for one domain. Call salesblink_list_reference_docs to see all topics. Always read 'overview' first.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | Doc topic, e.g. overview, sequences, lists, contacts, templates, senders |
No output schema declared.
No examples provided.
salesblink_list_reference_docs List API Reference Docs ~49
List the bundled SalesBlink API reference doc topics. Read 'overview' first, then the topic for the domain you are working in, before using salesblink_get or salesblink_mutate.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
salesblink_mutate SalesBlink API Mutate ~152
Make a write request to the SalesBlink public API (https://run.salesblink.io/api/public/v1.0.0): POST, PATCH, PUT, or DELETE. Use salesblink_get_reference_doc to look up exact endpoints, payload shapes, and gotchas before calling this. Example: method=POST path=/sequences body={...}.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | JSON request body for POST/PATCH/PUT (ignored for DELETE) |
| method | string | yes | HTTP method |
| path | string | yes | Relative API path starting with /, e.g. /sequences or /lists/abc-123. URL-encode messageIds in paths. |
| query | object | – | Query string parameters |
No output schema declared.
No examples provided.
salesblink_signup SalesBlink Signup ~32
Returns the public SalesBlink sign-up link where a new user can create an account. No API key is required.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the SalesBlink Cold Email MCP server?
SalesBlink Cold Email ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 93c46136bc8469786e827fabc599aa023ae4f62a8e2d23cfe758a60c04ff44ca; the commands to do that are on this page. If it does not match, do not open it.
mcpb · cold-email-salesblink.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
93c46136bc8469786e827fabc599aa023ae4f62a8e2d23cfe758a60c04ff44ca
macOS / Linux
echo "93c46136bc8469786e827fabc599aa023ae4f62a8e2d23cfe758a60c04ff44ca cold-email-salesblink.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\cold-email-salesblink.mcpb).Hash -eq "93c46136bc8469786e827fabc599aa023ae4f62a8e2d23cfe758a60c04ff44ca"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the SalesBlink Cold Email MCP server?
SalesBlink Cold Email is an MCP server listed in the public MCP registry as io.github.open-salesblink/cold-email-salesblink. Cold email sequences, leads, templates, senders, inbox, and analytics via the SalesBlink API. This page covers its MCPB bundle (https://github.com/open-salesblink/skill/releases/download/v1.2.0/cold-email-salesblink.mcpb).
Is the SalesBlink Cold Email MCP server safe to use?
SalesBlink Cold Email scores 48 out of 100 on VerifyMCP. It declares no install or post-install scripts. 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 SalesBlink Cold Email MCP server expose?
SalesBlink Cold Email exposes 6 tools: salesblink_get, salesblink_mutate, salesblink_signup, salesblink_list_reference_docs, salesblink_get_reference_doc, salesblink_check_auth. Their descriptions and schemas cost roughly 497 tokens of context every time the server is loaded.
What licence is the SalesBlink Cold Email MCP server under?
SalesBlink Cold Email declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.