Launch Engine — Business Execution OS
NPM · LAUNCH-ENGINE-MCP · SCANNED SEP 20
Agentic pipeline — 39 tools from idea to revenue for solo founders.
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 & Transparency19
- Repository check failed: the declared repository URL redirects; it must resolve directly. 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 169 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1945 tokens (~46/item across 42 items; 42 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "deploy" implies "deploy" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 42 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 Launch Engine — Business Execution OS MCP server?
Launch Engine — Business Execution OS runs locally as an npm package, launched with npx -y launch-engine-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 · launch-engine-mcp
claude mcp add zionhopkins-launch-engine -- npx -y launch-engine-mcp
{
"mcpServers": {
"zionhopkins-launch-engine": {
"command": "npx",
"args": [
"-y",
"launch-engine-mcp"
]
}
}
} {
"servers": {
"zionhopkins-launch-engine": {
"command": "npx",
"args": [
"-y",
"launch-engine-mcp"
]
}
}
} codex mcp add zionhopkins-launch-engine -- npx -y launch-engine-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"zionhopkins-launch-engine": {
"type": "local",
"command": [
"npx",
"-y",
"launch-engine-mcp"
],
"enabled": true
}
}
} openclaw mcp add zionhopkins-launch-engine --command npx --arg -y --arg launch-engine-mcp
mcp_servers:
zionhopkins-launch-engine:
command: "npx"
args: ["-y", "launch-engine-mcp"] {
"McpServers": {
"zionhopkins-launch-engine": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"launch-engine-mcp"
]
}
}
} assistant mcp add zionhopkins-launch-engine -t stdio -c npx -a -y launch-engine-mcp
{
"mcpServers": {
"zionhopkins-launch-engine": {
"command": "npx",
"args": [
"-y",
"launch-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.
- 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 +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.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 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.
- 12 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.
- 10 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.
- 9 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 20 Sept 2026 · Analysed npm/launch-engine-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 →
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 →
autonomy ~39
Agent Autonomy Score — scores a market across 7 dimensions for AI-buildable product viability.
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The market/pipeline slug |
No output schema declared.
No examples provided.
build_blocks ~38
3-Part Promotion Invention — builds the 7 Building Blocks from buyer research.
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The market/pipeline slug |
No output schema declared.
No examples provided.
capture_learning ~143
Capture a reusable learning/pattern to learnings.json. Called after key decisions, verdicts, and pipeline milestones.
| Name | Type | Req | Description |
|---|---|---|---|
| applies_to | string | yes | What future decisions this informs |
| category | string | yes | Learning category |
| confidence | string | yes | Confidence level based on evidence strength |
| evidence | string | yes | What data supports this pattern |
| pattern | string | yes | One sentence — the reusable insight |
| pipeline | string | yes | Market name / pipeline that produced this learning |
| stage | string | yes | Which SOP/stage generated this learning (e.g. 'scout', 'stress-test') |
| tags | array | yes | Searchable keywords for retrieval |
No output schema declared.
No examples provided.
channels ~33
Channel Deployment Engine — sets up and configures selected traffic channels.
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The market/pipeline slug |
No output schema declared.
No examples provided.
content_engine ~47
Organic Content & SEO/GEO Engine — topic cluster research, pillar/spoke content generation, schema markup, AI visibility baselines.
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The market/pipeline slug |
No output schema declared.
No examples provided.
content_repurpose ~58
Single-Pass Content Repurposing — takes one pillar page and generates 7+ platform-native assets (YouTube, short-form, Reddit, LinkedIn, newsletters, social).
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The market/pipeline slug |
No output schema declared.
No examples provided.
creative_test ~32
Creative Testing Protocol — generates and manages ad creative variations.
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The market/pipeline slug |
No output schema declared.
No examples provided.
daily_check ~37
Daily Operations Pulse — 5-minute daily check for any stage with live campaigns.
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The market/pipeline slug |
No output schema declared.
No examples provided.
deploy ~35
Campaign Deployment Engine — generates sales pages, email sequences, and ad copy.
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The market/pipeline slug |
No output schema declared.
No examples provided.
dream_100 ~34
Dream 100 Relationship Strategy — entity discovery and outreach sequences.
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The market/pipeline slug |
No output schema declared.
No examples provided.
feedback ~32
Optimizer Feedback Loop — diagnoses performance issues and routes fixes.
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The market/pipeline slug |
No output schema declared.
No examples provided.
funnel_optimize ~33
Funnel Optimization Engine — CRO testing across the conversion funnel.
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The market/pipeline slug |
No output schema declared.
No examples provided.
lessons ~76
Pattern Library & Learnings Engine — capture and retrieve patterns across pipelines.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Learning category to filter by |
| market_name | string | – | Pipeline name for context |
| mode | string | yes | capture: save a new learning | retrieve: search existing learnings |
| tags | array | – | Tags to search for |
No output schema declared.
No examples provided.
market_intel ~35
Market Intelligence OS — deep market research with competitive analysis and scoring.
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The market/pipeline slug |
No output schema declared.
No examples provided.
name_lock ~36
Name Lock Gate — locks the business/product name before any assets are built.
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The market/pipeline slug |
No output schema declared.
No examples provided.
passive_check ~42
Passive Asset Validation Check — scheduled performance checks at Day 14/30/45/60/90.
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The market/pipeline slug |
No output schema declared.
No examples provided.
passive_compound ~35
Anchor Compounding Engine — deploys related assets around proven anchors.
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The market/pipeline slug |
No output schema declared.
No examples provided.
passive_deploy ~38
Passive Asset Deployment Agent (PADA) — marketplace asset scoring and build specs.
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The market/pipeline slug |
No output schema declared.
No examples provided.
passive_portfolio ~33
Portfolio Feedback Report — quarterly review of all passive assets.
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The market/pipeline slug |
No output schema declared.
No examples provided.
platform ~33
Platform Engine — scores and selects the tech stack for product delivery.
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The market/pipeline slug |
No output schema declared.
No examples provided.
product ~31
Product Architecture Engine — designs the product/service delivery structure.
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The market/pipeline slug |
No output schema declared.
No examples provided.
qa ~36
Persona Alignment Gate — 7-check QA ensuring all copy aligns with buyer persona.
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The market/pipeline slug |
No output schema declared.
No examples provided.
rapid_check ~35
Rapid Test Daily Check — reviews metrics against decision thresholds.
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The rapid test slug to check/graduate |
No output schema declared.
No examples provided.
rapid_graduate ~40
Graduate Rapid Test to Full Pipeline — creates pipeline entry from rapid test data.
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The rapid test slug to check/graduate |
No output schema declared.
No examples provided.
rapid_status ~41
Rapid Test Portfolio Status — dashboard of all active/graduated/killed rapid tests.
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The rapid test slug to check/graduate |
No output schema declared.
No examples provided.
rapid_test ~69
Rapid Idea Test — compressed research + landing page + ads in a single pass.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | number | – | Test budget in dollars (default: 75) |
| duration_days | number | – | Test duration in days (default: 5) |
| idea | string | yes | The business idea to test |
No output schema declared.
No examples provided.
research ~37
Therapeutic Buyer Engine — deep buyer persona research with 25-35 web searches.
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The market/pipeline slug |
No output schema declared.
No examples provided.
save_asset ~88
Save a file to the assets/[market-name]/ directory. Use for all pipeline outputs: research, building blocks, copy, campaigns, etc.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The file content to write |
| file_path | string | yes | Path relative to assets/[market-name]/, e.g. 'research/scout-report.md' |
| market_name | string | yes | The market/pipeline slug |
No output schema declared.
No examples provided.
scale ~30
Scale Protocol — systematic scaling of validated traffic channels.
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The market/pipeline slug |
No output schema declared.
No examples provided.
scout ~59
Preliminary market scanning. Takes a raw idea and determines if it's worth deeper investigation.
| Name | Type | Req | Description |
|---|---|---|---|
| idea | string | yes | The market idea, niche, or problem to explore |
| market_name | string | – | URL-safe market slug (auto-generated from idea if omitted) |
No output schema declared.
No examples provided.
seo_check ~44
Monthly SEO/GEO Audit — content health, AI citation tracking, competitive gaps, technical SEO, content freshness scoring.
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The market/pipeline slug |
No output schema declared.
No examples provided.
status ~23
Pipeline Status Report — shows current pipeline stage, completed steps, and next actions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
stress_test ~43
Offer Stress Test — scores the offer across 10 dimensions, returns GO/REVISE/REBUILD.
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The market/pipeline slug |
No output schema declared.
No examples provided.
tournament ~54
Parallel Portfolio Tournament — batch-evaluates 3-5 business ideas through Layer 1 simultaneously with comparison gates. ~50-60% faster than sequential scout runs.
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The market/pipeline slug |
No output schema declared.
No examples provided.
traffic_analytics ~32
Traffic Analytics & Attribution — performance reporting and attribution.
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The market/pipeline slug |
No output schema declared.
No examples provided.
traffic_strategy ~31
Traffic Strategy Engine — researches and scores traffic channels.
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The market/pipeline slug |
No output schema declared.
No examples provided.
unit_economics ~40
Unit Economics Gate — models CPA, LTV, break-even, and budget requirements.
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The market/pipeline slug |
No output schema declared.
No examples provided.
update_pipeline_state ~175
Update pipeline-state.json. Use dot-notation paths to set values. Can create new pipelines and rapid tests.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | number | – | For rapid tests: test budget (default: 75) |
| create_pipeline | boolean | – | If true, creates a new pipeline entry if it doesn't exist |
| create_rapid_test | boolean | – | If true, creates a new rapid test entry |
| duration_days | number | – | For rapid tests: test duration (default: 5) |
| idea | string | – | For rapid tests: the original idea description |
| market_name | string | yes | The market/pipeline slug |
| path | string | yes | Dot-notation path to update, e.g. 'pipelines.my-market.layer_1.scout.status' |
| value | – | – | The value to set at the path |
No output schema declared.
No examples provided.
validate_check ~36
Daily 60-Second Health Check — quick metrics review during validation window.
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The market/pipeline slug |
No output schema declared.
No examples provided.
validate_decide ~41
Validation Verdict Engine — end-of-window decision: ADVANCE, ITERATE, or KILL.
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The market/pipeline slug |
No output schema declared.
No examples provided.
validate_prep ~35
Validation Deployment Package — generates the deployment checklist for real-world testing.
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The market/pipeline slug |
No output schema declared.
No examples provided.
voice_extract ~36
Brand Voice Extraction — generates brand voice calibration docs from QA-passed content.
| Name | Type | Req | Description |
|---|---|---|---|
| market_name | string | yes | The market/pipeline slug |
No output schema declared.
No examples provided.
What is the Launch Engine — Business Execution OS MCP server?
Launch Engine — Business Execution OS is an MCP server listed in the public MCP registry as io.github.ZionHopkins/launch-engine. Agentic pipeline, 39 tools from idea to revenue for solo founders. This page covers its npm package (launch-engine-mcp).
Is the Launch Engine — Business Execution OS MCP server safe to use?
Launch Engine — Business Execution OS scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 Launch Engine — Business Execution OS MCP server expose?
Launch Engine — Business Execution OS exposes 42 tools: scout, autonomy, market_intel, research, build_blocks, and 37 more. Their descriptions and schemas cost roughly 1,945 tokens of context every time the server is loaded.
Is the Launch Engine — Business Execution OS MCP server still maintained?
Launch Engine — Business Execution OS is still listed as active in the MCP registry. We last reached this channel on 20 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 Launch Engine — Business Execution OS MCP server under?
Launch Engine — Business Execution OS declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.