Outreach
NPM · @MINDSTONE/MCP-SERVER-OUTREACH · SCANNED SEP 21
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 → 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 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency87
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to mindstone/mcp-servers). View diagnostics → Pass
- 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 42 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2524 tokens (~114/item across 22 items; 22 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 Management97
- Stability observed for 29 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 22 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
How do I install the Outreach MCP server?
Outreach runs locally as an npm package, launched with npx -y @mindstone/mcp-server-outreach. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @mindstone/mcp-server-outreach
claude mcp add mindstone-mcp-server-outreach -- npx -y @mindstone/mcp-server-outreach
{
"mcpServers": {
"mindstone-mcp-server-outreach": {
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-outreach"
]
}
}
} {
"servers": {
"mindstone-mcp-server-outreach": {
"command": "npx",
"args": [
"-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": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@mindstone/mcp-server-outreach"
]
}
}
} assistant mcp add mindstone-mcp-server-outreach -t stdio -c npx -a -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.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −2
- Stability: pass → 0.83 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
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 21 Sept 2026 · Analysed npm/@mindstone/mcp-server-outreach@0.2.1
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 | mindstone/mcp-servers |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/mindstone/mcp-servers/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 2404542246 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:7b7f484a6b3903d69b6c450d9d39d97dc491cfc0de902e383e1401872976e3cc16c3a5a1ae1c5a2cc656f3cdab772b3c961770e540503275eda43a295 |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| 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 →
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_complete_task ~56
Mark an Outreach task as completed. Example: { "id": "401" } WORKFLOW: Use outreach_list_tasks with status "incomplete" to find open task IDs.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Task ID (required) |
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 ~175
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.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | – | Associated Outreach account ID |
| company | string | – | Company name |
| custom_fields | object | – | Outreach custom field values, keyed custom1 through custom35 (e.g. { "custom1": "enterprise" }) |
| 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_create_task ~187
Create a task in Outreach, e.g. a follow-up reminder for a prospect. Example: { "note": "Follow up on pricing question", "prospect_id": "123", "due_at": "2026-05-01T17:00:00Z" } WORKFLOW: Use outreach_search_prospects to find the prospect ID first.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | Type of action the task requires (default: generic action item) |
| due_at | string | – | Due date as an ISO 8601 datetime string (e.g. "2026-05-01T17:00:00Z") |
| note | string | yes | Task note — what needs to be done (required) |
| owner_id | – | – | Outreach user ID who owns the task (uses default when omitted) |
| prospect_id | string | – | Prospect ID the task relates to |
No output schema declared.
No examples provided.
outreach_disconnect_account ~53
Disconnect an Outreach account. Example: { "username": "user@company.com" } 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_get_sequence_template ~93
Get a sequence template, including the actual email subject and body. Example: { "id": "901" } A sequence template links a sequence step to its content template. The response includes the sequence template record plus the resolved template's subject and bodyHtml under "template". WORKFLOW: outreach_list_sequence_steps returns the sequenceTemplates IDs for a sequence.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Sequence template ID |
No output schema declared.
No examples provided.
outreach_list_accounts ~128
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 | – | Record offset into the result list for pagination (maps to the API's page[offset]; e.g. 25 for the second page with limit 25) |
No output schema declared.
No examples provided.
outreach_list_calls ~176
List Outreach calls with direction, outcome, notes, and linked call disposition. Example: { "prospect_id": "123" } or { "user_id": "601" } Returns calls with state, direction (inbound/outbound), outcome (completed/no_answer), answered/completed timestamps, notes, and the callDisposition_id linking to the logged call outcome. Useful for meeting prep and reviewing recent activity.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default 25, max 50) |
| page_offset | number | – | Record offset into the result list for pagination (maps to the API's page[offset]; e.g. 25 for the second page with limit 25) |
| prospect_id | string | – | Filter calls for a specific prospect |
| user_id | – | – | Filter calls made by a specific Outreach user |
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_mailboxes ~135
List Outreach mailboxes (connected sender email accounts). Example: {} Returns mailboxes with email address, send/sync status, and owning user. WORKFLOW: Use the returned IDs as mailbox_id when enrolling a prospect with outreach_add_prospect_to_sequence.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default 25, max 50) |
| page_offset | number | – | Record offset into the result list for pagination (maps to the API's page[offset]; e.g. 25 for the second page with limit 25) |
| user_id | string | – | Filter mailboxes owned by a specific Outreach user |
No output schema declared.
No examples provided.
outreach_list_mailings ~126
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 | – | Record offset into the result list for pagination (maps to the API's page[offset]; e.g. 25 for the second page with limit 25) |
| prospect_id | string | – | Filter mailings for a specific prospect |
No output schema declared.
No examples provided.
outreach_list_sequence_steps ~151
List the steps of an Outreach sequence. Example: { "sequence_id": "456" } Returns each step's type (auto_email, manual_email, call, task), interval, and order. WORKFLOW: Use outreach_list_sequences to find the sequence ID first, then outreach_get_sequence_template with a step's sequenceTemplates ID to read the email copy.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results (default 25, max 50) |
| page_offset | number | – | Record offset into the result list for pagination (maps to the API's page[offset]; e.g. 25 for the second page with limit 25) |
| sequence_id | string | yes | Sequence ID (required) |
No output schema declared.
No examples provided.
outreach_list_sequences ~132
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 | – | Record offset into the result list for pagination (maps to the API's page[offset]; e.g. 25 for the second page with limit 25) |
No output schema declared.
No examples provided.
outreach_list_tasks ~129
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 | – | Record offset into the result list for pagination (maps to the API's page[offset]; e.g. 25 for the second page with limit 25) |
| 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_remove_prospect_from_sequence ~164
Pause or finish a prospect's enrollment in a sequence. Example: { "prospect_id": "123", "sequence_id": "456", "action": "pause" } ACTIONS: "pause" (default) stops future sends but can be resumed later; "remove" finishes the enrollment via the sequence state's finish action — the prospect receives no further steps, and re-enrolling restarts the sequence from the top. WORKFLOW: Finds the prospect's sequence state for the given sequence, then applies the action.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | "pause" (reversible, default) or "remove" (finish the enrollment) |
| prospect_id | string | yes | Prospect ID |
| sequence_id | string | yes | Sequence ID |
No output schema declared.
No examples provided.
outreach_search_prospects ~205
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.
| 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 | – | Record offset into the result list for pagination (maps to the API's page[offset]; e.g. 25 for the second page with limit 25) |
| tags | array | – | Filter by tags |
No output schema declared.
No examples provided.
outreach_update_prospect ~148
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 |
| custom_fields | object | – | Outreach custom field values, keyed custom1 through custom35 (e.g. { "custom1": "enterprise" }) |
| 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.
What is the Outreach MCP server?
Outreach is an MCP server listed in the public MCP registry as io.github.mindstone/mcp-server-outreach. Outreach sales engagement MCP server: prospects, sequences, accounts, tasks, and mailings. This page covers its npm package (@mindstone/mcp-server-outreach).
Is the Outreach MCP server safe to use?
Outreach scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 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 Outreach MCP server expose?
Outreach exposes 22 tools: outreach_connect_account, outreach_list_connected_accounts, outreach_disconnect_account, outreach_search_prospects, outreach_get_prospect, and 17 more. Their descriptions and schemas cost roughly 2,524 tokens of context every time the server is loaded.
Is the Outreach MCP server still maintained?
Outreach is still listed as active in the MCP registry. We last reached this channel on 21 September 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 Outreach MCP server under?
Outreach declares the FSL-1.1-MIT licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.