Is Launch Engine safe and trustworthy?

tashan scores Launch Engine on public evidence — tashan score 36.0/100, it is currently active, note: a single primary maintainer (bus-factor risk), no known advisories against the current release. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Launch Engine?

In Claude Code: run `claude mcp add launch-engine -- npx -y launch-engine-mcp`. In Cursor / Claude Desktop, add it to mcp.json / claude_desktop_config.json.

Who maintains Launch Engine?

source: ZionHopkins/launch-engine-mcp.

‹ The Index

Launch Engine

npm

Business Execution OS for solo founders and bootstrappers — 42 structured tools guiding raw idea to validated revenue. Market research, buyer personas, offer design, landing pages, email sequences, ad copy, traffic strategy, SEO content engine, revenue ph

Works with: Claude Code, Cursor, Claude Desktop, Codex CLI, Gemini CLI, Cline, Windsurf, VS Code (installable)
installable: each client documents how to load an MCP server of this type — that is the client's promise, not a claim verified against this capability

Category: Communication — see all ranked ›

Work: Market analysis · SEO · Content marketing

Who it is for: Product manager · Marketer / growth · Writer / content

Install (Claude Code):

claude mcp add launch-engine -- npx -y launch-engine-mcp

tashan score: 36.0
Adoption: 76/wk
Upkeep: 48.0
Freshness: 62.0
Evidence coverage: 100% of the inputs this score can use
Health: active

Security audit

Every finding is shown in full — which advisory, the version that fixes it, and the exact command run at install time. Nothing in this audit is behind a licence.

No known advisoriesclearchecked against OSV for 1.2.0

No access inferred from declared dependenciesnothing it depends on reaches files, shell or network. This reads declarations only — built-in APIs are invisible to it, so absence of a declaration is not absence of access

No build provenanceno attestation — the published artifact cannot be traced to its source

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

Launch Engine scores 36 today. Pro keeps the series, so you can see whether that is a project getting better or one on its way down — and tells you the day it moves.

Every score since we started measuring, for any capability
The named replacement when something you run is dying — not just that it is
tashan doctor over the config you already have, on your machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/pkg-launch-engine-mcp.svg)](https://tashan.sh/capability/pkg-launch-engine-mcp.html)

npm ↗ · source ↗ · pkg:launch-engine-mcp

Everything on this page is public evidence and free. What it cannot know is whether you run this — npx tashan-cli doctor reads your own config and names what is wrong in it, also free. tashan Pro tells you the day any of it changes.

Already running this? npx tashan-cli doctor checks your whole config against the Index — how it works ›

Measured 2026-08-14 · scorer s5 · how · something wrong here?