io.github.closermethod/outbound-engine-mcp
NPM · OUTBOUND-ENGINE-MCP · SCANNED AUG 3
One cold-outreach engine for any target: HOOK/BRIDGE/SOFT-ASK, follow-up ladder, reply playbook.
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 Security86
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (94 of 98), 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 (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 19 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 565 tokens (~80/item across 7 items; 7 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 Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 63% of tool parameters carry a description.Partial
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.
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 · outbound-engine-mcp
claude mcp add closermethod-outbound-engine-mcp -- npx -y outbound-engine-mcp
codex mcp add closermethod-outbound-engine-mcp -- npx -y outbound-engine-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"closermethod-outbound-engine-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"outbound-engine-mcp"
],
"enabled": true
}
}
} openclaw mcp add closermethod-outbound-engine-mcp --command npx --arg -y --arg outbound-engine-mcp
mcp_servers:
closermethod-outbound-engine-mcp:
command: "npx"
args: ["-y", "outbound-engine-mcp"] {
"mcpServers": {
"closermethod-outbound-engine-mcp": {
"command": "npx",
"args": [
"-y",
"outbound-engine-mcp"
]
}
}
} 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.
- 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
- Tool coverage: 100 → unverified ▼ functional
- Security disclosure: fail → unverified ▼ functional
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- First check of Schema quality: unverified functional
- Licence: MIT functional
- 31 Jul 26 −7
- 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 45
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/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 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.
audit_cold_message ~86
Audit a drafted cold message against the engine rules: no money/rates, no identity-first opener, specific hook required, soft ask only, under ~90 words, one ask. Returns PASS/FAIL with named violations and a rewrite recipe.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | The full draft cold message text |
| target_type | string | — | Optional target type for pack-specific reminders |
No output schema declared.
No examples provided.
build_followup_ladder ~100
Returns the 5-step follow-up ladder (Day 3 bump, Day 7 value-give, Day 12 new proof, Day 18 soft close, Day 25 break-up) with the move and rule for each rung. 80% of deals close in follow-up; the break-up alone pulls ~30% of replies.
| Name | Type | Req | Description |
|---|---|---|---|
| target_type | string | — | Optional: contextualizes the soft-ask object in each rung |
No output schema declared.
No examples provided.
build_pricing_menu ~71
Returns the 3-option menu structure (Starter / Most Popular / Full), the two scoping questions to ask FIRST for the target type, and the drop-scope-not-price negotiation rule. Use only after the prospect asks about price — never in a cold message.
| Name | Type | Req | Description |
|---|---|---|---|
| target_type | string | yes | — |
No output schema declared.
No examples provided.
detect_red_flags ~67
Scan a prospect's reply or brief for walk-away signals: exposure-pay, spec-work requests, pay-on-performance, budget mismatch, scope-creep probes. Returns flags found and a CLEAN/CAUTION/WALK verdict.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The prospect's reply or brief text |
No output schema declared.
No examples provided.
get_full_pack ~50
Returns the complete engine: core rules, all target packs, follow-up ladder, reply playbook, pricing menu, red flags. Useful for full agent context (e.g. a Claude Project system prompt).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
handle_reply ~72
Given the type of reply received, returns what it means, the next move, the reply shape, and the trap to avoid. Reply types: price_question, interested, not_now, no_budget, exposure_offer, spec_request, pay_on_performance, ghosted_after_interest.
| Name | Type | Req | Description |
|---|---|---|---|
| reply_type | string | yes | — |
No output schema declared.
No examples provided.
structure_cold_pitch ~119
Get the HOOK / BRIDGE / SOFT ASK structure plus the 4 swap variables (who to pitch, signal to research, proof to lead with, soft-ask object) for a target type. Target types: brand_deal, ugc, newsletter_sponsorship, job, podcast, client_work.
| Name | Type | Req | Description |
|---|---|---|---|
| signal_found | string | — | Optional: the one specific true thing you found about this target (5 words). If omitted, the response reminds you: no signal, no pitch. |
| target_type | string | yes | — |
No output schema declared.
No examples provided.