# Outreach (npm · @mindstone/mcp-server-outreach)

Outreach sales engagement MCP server: prospects, sequences, accounts, tasks, and mailings

- Trust score: 66/100 (medium)
- Change this week: +20
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `@mindstone/mcp-server-outreach`: 66/100 (this document), [markdown](https://verifymcp.io/servers/mindstone-mcp-server-outreach/mindstone-mcp-server-outreach.md), [page](https://verifymcp.io/servers/mindstone-mcp-server-outreach/mindstone-mcp-server-outreach)

## Channel facts

- Registry: `npm`
- Package: `@mindstone/mcp-server-outreach`
- Version: `0.1.3`
- Transport: `stdio`

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

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (FSL-1.1-MIT) isn't a recognized OSI-approved license.
  - Actively maintained (last published 76 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1373 tokens (~91/item across 15 items; 15 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add mindstone-mcp-server-outreach -- npx -y @mindstone/mcp-server-outreach
```

### Codex

```bash
codex mcp add mindstone-mcp-server-outreach -- npx -y @mindstone/mcp-server-outreach
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mindstone-mcp-server-outreach": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@mindstone/mcp-server-outreach"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mindstone-mcp-server-outreach --command npx --arg -y --arg @mindstone/mcp-server-outreach
```

### Hermes

```yaml
mcp_servers:
  mindstone-mcp-server-outreach:
    command: "npx"
    args: ["-y", "@mindstone/mcp-server-outreach"]
```

### Other

```json
{
  "mcpServers": {
    "mindstone-mcp-server-outreach": {
      "command": "npx",
      "args": [
        "-y",
        "@mindstone/mcp-server-outreach"
      ]
    }
  }
}
```

## 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-08-03 (score 66, +3)

- [functional improvement] Stability: unverified → 0.23

### 2026-08-02 (score 63, +42)

- [security regression] Provenance: unverified → fail
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Install scripts: unverified → pass
- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional regression] License: unverified → fail
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional] Licence: FSL-1.1-MIT

### 2026-08-01 (score 21, +16)

- [functional improvement] Tool coverage: unverified → 100

### 2026-07-31 (score 5, −23)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 28, −18)

- [security regression] Malware scan: pass → unverified

### 2026-07-27 (score 46)

First indexed and scored.

## MCP tools (15)

### `outreach_connect_account` (~86 tokens)

Connect an Outreach account via OAuth. Takes no parameters — call with {}.

Initiates OAuth flow — in standalone mode, opens a browser URL for sign-in. In bridge mode, delegates to the host app.

WHEN TO USE:
\- No Outreach account is connected
\- Authentication errors from other tools
\- User asks to connect Outreach

After connecting, verify with outreach_list_connected_accounts.

### `outreach_list_connected_accounts` (~45 tokens)

List connected Outreach accounts. Takes no parameters — call with {}.

Call this FIRST before any Outreach operations to verify authentication.
Returns auth mode, connection status, and account details.

### `outreach_disconnect_account` (~53 tokens)

Disconnect an Outreach account. Example: { "username": "user@company.com" }

Removes stored credentials. Use when switching accounts or troubleshooting.

Input parameters:

- `username` (string, required): Username/email of the account to disconnect

### `outreach_search_prospects` (~182 tokens)

Search Outreach prospects. Example: { "email": "jane@acme.com" } or { "name": "Jane", "limit": 10 }

WORKFLOW: Search first, then use outreach_get_prospect for full details.
FILTERS: name, email, company, tags. All optional — omit all for recent prospects.
PAGINATION: Default 25, max 50. Use page_offset for next page.

Input parameters:

- `company` (string): Filter by company name
- `email` (string): Filter by email address (exact match)
- `limit` (number): Max results (default 25, max 50)
- `name` (string): Filter by first or last name (partial match)
- `page_offset` (number): Page offset for pagination (0-based)
- `tags` (array): Filter by tags

### `outreach_get_prospect` (~66 tokens)

Get full details of an Outreach prospect by ID. Example: { "id": "123" }

Returns all prospect fields including custom fields, tags, engagement data.
RELATED TOOLS: outreach_search_prospects to find IDs first.

Input parameters:

- `id` (string, required): Prospect ID

### `outreach_create_prospect` (~144 tokens)

Create a new prospect in Outreach. Example: { "email": "jane@acme.com", "first_name": "Jane", "last_name": "Doe" }

REQUIRED: At least email or last_name.
COMMON MISTAKES: Don't forget to associate with an account via account_id if known.

Input parameters:

- `account_id` (string): Associated Outreach account ID
- `company` (string): Company name
- `email` (string): Email address
- `first_name` (string): First name
- `last_name` (string): Last name
- `tags` (array): Tags to apply
- `title` (string): Job title

### `outreach_update_prospect` (~117 tokens)

Update an existing prospect. Example: { "id": "123", "title": "VP Sales" }

Only provided fields are updated. Use outreach_search_prospects to find the ID.

Input parameters:

- `company` (string): Company name
- `email` (string): Email address
- `first_name` (string): First name
- `id` (string, required): Prospect ID (required)
- `last_name` (string): Last name
- `tags` (array): Tags to apply
- `title` (string): Job title

### `outreach_list_sequences` (~106 tokens)

List Outreach sequences. Example: { "name": "Demo follow-up" } or {}

Returns sequences with status, step count, and engagement stats.
FILTERS: name (partial match), enabled status.

Input parameters:

- `enabled` (boolean): Filter by enabled/disabled status
- `limit` (number): Max results (default 25, max 50)
- `name` (string): Filter by sequence name (partial match)
- `page_offset` (number): Page offset for pagination

### `outreach_get_sequence` (~48 tokens)

Get full details of an Outreach sequence by ID. Example: { "id": "456" }

Returns sequence config, steps, and performance metrics.

Input parameters:

- `id` (string, required): Sequence ID

### `outreach_add_prospect_to_sequence` (~123 tokens)

Add a prospect to a sequence. Example: { "prospect_id": "123", "sequence_id": "456" }

WORKFLOW: Find the prospect (outreach_search_prospects) and sequence (outreach_list_sequences) first.
COMMON MISTAKES: Prospect must not already be active in the same sequence.

Input parameters:

- `mailbox_id` (string): Mailbox ID to send from (optional, uses default)
- `prospect_id` (string, required): Prospect ID to enroll
- `sequence_id` (string, required): Sequence ID to enroll into

### `outreach_list_accounts` (~102 tokens)

List Outreach accounts (companies). Example: { "name": "Acme" } or { "domain": "acme.com" }

Returns company accounts with domain, industry, and owner info.

Input parameters:

- `domain` (string): Filter by domain
- `limit` (number): Max results (default 25, max 50)
- `name` (string): Filter by account name (partial match)
- `page_offset` (number): Page offset for pagination

### `outreach_get_account` (~53 tokens)

Get full details of an Outreach account (company) by ID. Example: { "id": "789" }

Returns account fields, custom fields, and associated prospects count.

Input parameters:

- `id` (string, required): Account ID

### `outreach_list_tasks` (~103 tokens)

List Outreach tasks. Example: { "status": "incomplete" } or { "prospect_id": "123" }

Returns tasks with status, due date, type, and assigned user.

Input parameters:

- `limit` (number): Max results (default 25, max 50)
- `page_offset` (number): Page offset for pagination
- `prospect_id` (string): Filter tasks for a specific prospect
- `status` (string): Filter by completion status

### `outreach_list_mailings` (~100 tokens)

List recent mailings (sent emails). Example: { "prospect_id": "123" } or { "limit": 10 }

Returns sent emails with subject, status (delivered/bounced/opened), and timestamps.

Input parameters:

- `limit` (number): Max results (default 25, max 50)
- `page_offset` (number): Page offset for pagination
- `prospect_id` (string): Filter mailings for a specific prospect

### `outreach_list_users` (~45 tokens)

List Outreach team members. Example: {}

Returns users with name, email, and role information.

Input parameters:

- `limit` (number): Max results (default 25, max 50)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/mindstone-mcp-server-outreach/mindstone-mcp-server-outreach#diagnostics

## Score history

- 2026-08-03: 66
- 2026-08-02: 63
- 2026-08-01: 21
- 2026-07-31: 5
- 2026-07-30: 28
- 2026-07-28: 46
- 2026-07-27: 46

## Links

- npm package: https://www.npmjs.com/package/@mindstone/mcp-server-outreach
- Socket report: https://socket.dev/npm/package/@mindstone/mcp-server-outreach
- Repository: https://github.com/mindstone/mcp-servers
- Changelog RSS feed: https://verifymcp.io/servers/mindstone-mcp-server-outreach/mindstone-mcp-server-outreach/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/mindstone-mcp-server-outreach/mindstone-mcp-server-outreach/changelog.json
- HTML version of this page: https://verifymcp.io/servers/mindstone-mcp-server-outreach/mindstone-mcp-server-outreach