OutreachBox
NPM · @OUTREACHBOX/MCP · 2 COMPONENTS
Cold email, prospect research, inbox triage, and content marketing in OutreachBox.
Available components
Last scanned (17 hours ago)
Scores higher than 30% of npm servers
Category CRM and Sales
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 33 of 106 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- 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 26 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 3182 tokens (~56/item across 56 items; 56 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 Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 56 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.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 42
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 npm/@outreachbox/mcp@1.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 106 packages
| Packages resolved | 106 |
|---|---|
| Stale | 33 |
| 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 →
social_publish ~112
Publish content to a connected social account (LinkedIn, Twitter, etc.). Provide either a saved contentId or raw post text.
| Name | Type | Req | Description |
|---|---|---|---|
| accountId | string | yes | Connected social account ID to publish to |
| content | string | – | Raw post text to publish directly |
| contentId | string | – | ID of saved content to publish |
| platform | string | – | Platform name e.g. linkedin, twitter (used when publishing raw content) |
| title | string | – | Title for the post when publishing raw content |
No output schema declared.
No examples provided.
templates_create ~126
Create a reusable email template. Variables in {{double-brace}} syntax are auto-extracted.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | Additional categories |
| category | string | – | Primary category |
| htmlContent | string | yes | HTML body content (supports {{variables}}) |
| isShared | boolean | – | Share the template across the organization |
| name | string | yes | Template name |
| subject | string | yes | Email subject line (supports {{variables}}) |
| textContent | string | – | Plain-text body fallback |
| variables | array | – | Explicit variable names (auto-extracted from content otherwise) |
No output schema declared.
No examples provided.
templates_delete ~30
Permanently delete an email template by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The database ID of the resource |
No output schema declared.
No examples provided.
templates_get ~35
Get a single email template including its full content and variables by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The database ID of the resource |
No output schema declared.
No examples provided.
templates_list ~36
List reusable email templates (own, shared, and system) available to the organization.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter templates by category |
No output schema declared.
No examples provided.
templates_update ~88
Update fields on an existing email template by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | – |
| category | string | – | – |
| htmlContent | string | – | – |
| id | string | yes | Template ID to update |
| isShared | boolean | – | – |
| name | string | – | – |
| subject | string | – | – |
| textContent | string | – | – |
| variables | array | – | – |
No output schema declared.
No examples provided.
How do I install the OutreachBox MCP server?
OutreachBox runs locally as an npm package, launched with npx -y @outreachbox/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @outreachbox/mcp
claude mcp add pulsereal-outreachbox -- npx -y @outreachbox/mcp
What is the OutreachBox MCP server?
OutreachBox is an MCP server listed in the public MCP registry as io.github.pulsereal/outreachbox. Cold email, prospect research, inbox triage, and content marketing in OutreachBox. This page covers its npm package (@outreachbox/mcp).
Is the OutreachBox MCP server safe to use?
OutreachBox scores 57 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. 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 OutreachBox MCP server expose?
OutreachBox exposes 56 tools: contacts_create, contacts_bulk, contacts_list, contacts_get, contacts_update, and 51 more. Their descriptions and schemas cost roughly 3,182 tokens of context every time the server is loaded.
Is the OutreachBox MCP server still maintained?
OutreachBox is still listed as active in the MCP registry. We last reached this channel on 5 November 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 OutreachBox MCP server under?
OutreachBox declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the OutreachBox MCP server?
VerifyMCP ran 15 checks on OutreachBox, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about OutreachBox: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.