# SalesBlink Cold Email (mcpb · cold-email-salesblink.mcpb)

Cold email sequences, leads, templates, senders, inbox, and analytics via the SalesBlink API.

- Trust score: 48/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.salesblink.io`: 83/100, [markdown](https://verifymcp.io/servers/open-salesblink-cold-email-salesblink/mcp.md), [page](https://verifymcp.io/servers/open-salesblink-cold-email-salesblink/mcp)
- mcpb · `cold-email-salesblink.mcpb`: 48/100 (this document), [markdown](https://verifymcp.io/servers/open-salesblink-cold-email-salesblink/cold-email-salesblink.md), [page](https://verifymcp.io/servers/open-salesblink-cold-email-salesblink/cold-email-salesblink)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/open-salesblink/skill/releases/download/v1.2.0/cold-email-salesblink.mcpb`
- Version: `1.2.0`
- Transport: `stdio`
- SHA-256: `93c46136bc8469786e827fabc599aa023ae4f62a8e2d23cfe758a60c04ff44ca`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 23/100
  - 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.
  - Known CVEs were checked across the 92 of 92 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - 30 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 11 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 635 tokens (~105/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### 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.

- Download bundle: `https://github.com/open-salesblink/skill/releases/download/v1.2.0/cold-email-salesblink.mcpb`
- SHA-256: `93c46136bc8469786e827fabc599aa023ae4f62a8e2d23cfe758a60c04ff44ca`

### Verify on macOS / Linux

```bash
echo "93c46136bc8469786e827fabc599aa023ae4f62a8e2d23cfe758a60c04ff44ca  cold-email-salesblink.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\cold-email-salesblink.mcpb).Hash -eq "93c46136bc8469786e827fabc599aa023ae4f62a8e2d23cfe758a60c04ff44ca"
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-24 (score 48)

First indexed and scored.

## MCP tools (6)

### `salesblink_get` (~152 tokens)

SalesBlink API GET

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 }.

Input parameters:

- `path` (string, required): 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 }

### `salesblink_mutate` (~152 tokens)

SalesBlink API Mutate

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={...}.

Input parameters:

- `body`: JSON request body for POST/PATCH/PUT (ignored for DELETE)
- `method` (string, required): HTTP method
- `path` (string, required): Relative API path starting with /, e.g. /sequences or /lists/abc-123. URL-encode messageIds in paths.
- `query` (object): Query string parameters

### `salesblink_signup` (~32 tokens)

SalesBlink Signup

Returns the public SalesBlink sign-up link where a new user can create an account. No API key is required.

### `salesblink_list_reference_docs` (~49 tokens)

List API Reference Docs

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.

### `salesblink_get_reference_doc` (~78 tokens)

Read API Reference Doc

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.

Input parameters:

- `topic` (string, required): Doc topic, e.g. overview, sequences, lists, contacts, templates, senders

### `salesblink_check_auth` (~34 tokens)

Verify API Key

Verify the configured SalesBlink API key by calling GET /account/verify. Returns account info when the key is valid.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/open-salesblink-cold-email-salesblink/cold-email-salesblink#diagnostics

## Score history

- 2026-11-05: 48
- 2026-11-04: 48
- 2026-11-03: 48
- 2026-11-02: 48
- 2026-11-01: 48
- 2026-10-31: 48
- 2026-10-30: 48
- 2026-10-29: 48
- 2026-10-28: 48
- 2026-10-27: 48
- 2026-10-26: 48
- 2026-10-25: 48
- 2026-10-24: 48

## Common questions

### 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.

## Links

- Repository: https://github.com/open-salesblink/skill
- Website: https://salesblink.io/
- Changelog RSS feed: https://verifymcp.io/servers/open-salesblink-cold-email-salesblink/cold-email-salesblink.xml
- Changelog JSON feed: https://verifymcp.io/servers/open-salesblink-cold-email-salesblink/cold-email-salesblink.json
- HTML version of this page: https://verifymcp.io/servers/open-salesblink-cold-email-salesblink/cold-email-salesblink
