Outreach
NPM · @MINDSTONE/MCP-SERVER-OUTREACH · SCANNED AUG 3
Outreach sales engagement MCP server: prospects, sequences, accounts, tasks, and mailings
Available components
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency32
- 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
- License check failed: the license (FSL-1.1-MIT) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 76 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1373 tokens (~91/item across 15 items; 15 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @mindstone/mcp-server-outreach
claude mcp add mindstone-mcp-server-outreach -- npx -y @mindstone/mcp-server-outreach
codex mcp add mindstone-mcp-server-outreach -- npx -y @mindstone/mcp-server-outreach
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mindstone-mcp-server-outreach": {
"type": "local",
"command": [
"npx",
"-y",
"@mindstone/mcp-server-outreach"
],
"enabled": true
}
}
} openclaw mcp add mindstone-mcp-server-outreach --command npx --arg -y --arg @mindstone/mcp-server-outreach
mcp_servers:
mindstone-mcp-server-outreach:
command: "npx"
args: ["-y", "@mindstone/mcp-server-outreach"] {
"mcpServers": {
"mindstone-mcp-server-outreach": {
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-outreach"
]
}
}
} 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.
- 3 Aug 26 +3
- Stability: unverified → 0.23 ▲ functional
- 2 Aug 26 +42
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- License: unverified → fail ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: unverified → excellent ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: FSL-1.1-MIT functional
- 1 Aug 26 +16
- Tool coverage: unverified → 100 ▲ functional
- 31 Jul 26 −23
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 27 Jul 26 46
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 3 Aug 2026 · Analysed npm/@mindstone/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 95 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
outreach_add_prospect_to_sequence ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| mailbox_id | string | — | Mailbox ID to send from (optional, uses default) |
| prospect_id | string | yes | Prospect ID to enroll |
| sequence_id | string | yes | Sequence ID to enroll into |
No output schema declared.
No examples provided.
outreach_connect_account ~86
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
outreach_create_prospect ~144
Create a new prospect in Outreach. Example: { "email": "[email protected]", "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.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | — | Associated Outreach account ID |
| company | string | — | Company name |
| string | — | Email address | |
| first_name | string | — | First name |
| last_name | string | — | Last name |
| tags | array | — | Tags to apply |
| title | string | — | Job title |
No output schema declared.
No examples provided.
outreach_disconnect_account ~53
Disconnect an Outreach account. Example: { "username": "[email protected]" } Removes stored credentials. Use when switching accounts or troubleshooting.
| Name | Type | Req | Description |
|---|---|---|---|
| username | string | yes | Username/email of the account to disconnect |
No output schema declared.
No examples provided.
outreach_get_account ~53
Get full details of an Outreach account (company) by ID. Example: { "id": "789" } Returns account fields, custom fields, and associated prospects count.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Account ID |
No output schema declared.
No examples provided.
outreach_get_prospect ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Prospect ID |
No output schema declared.
No examples provided.
outreach_get_sequence ~48
Get full details of an Outreach sequence by ID. Example: { "id": "456" } Returns sequence config, steps, and performance metrics.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Sequence ID |
No output schema declared.
No examples provided.
outreach_list_accounts ~102
List Outreach accounts (companies). Example: { "name": "Acme" } or { "domain": "acme.com" } Returns company accounts with domain, industry, and owner info.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
outreach_list_connected_accounts ~45
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
outreach_list_mailings ~100
List recent mailings (sent emails). Example: { "prospect_id": "123" } or { "limit": 10 } Returns sent emails with subject, status (delivered/bounced/opened), and timestamps.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Max results (default 25, max 50) |
| page_offset | number | — | Page offset for pagination |
| prospect_id | string | — | Filter mailings for a specific prospect |
No output schema declared.
No examples provided.
outreach_list_sequences ~106
List Outreach sequences. Example: { "name": "Demo follow-up" } or {} Returns sequences with status, step count, and engagement stats. FILTERS: name (partial match), enabled status.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
outreach_list_tasks ~103
List Outreach tasks. Example: { "status": "incomplete" } or { "prospect_id": "123" } Returns tasks with status, due date, type, and assigned user.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
outreach_list_users ~45
List Outreach team members. Example: {} Returns users with name, email, and role information.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Max results (default 25, max 50) |
No output schema declared.
No examples provided.
outreach_search_prospects ~182
Search Outreach prospects. Example: { "email": "[email protected]" } 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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | — | Filter by company name |
| 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 |
No output schema declared.
No examples provided.
outreach_update_prospect ~117
Update an existing prospect. Example: { "id": "123", "title": "VP Sales" } Only provided fields are updated. Use outreach_search_prospects to find the ID.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | — | Company name |
| string | — | Email address | |
| first_name | string | — | First name |
| id | string | yes | Prospect ID (required) |
| last_name | string | — | Last name |
| tags | array | — | Tags to apply |
| title | string | — | Job title |
No output schema declared.
No examples provided.