# LaunchEngine.dev (npm · @launchengine-dev/mcp)

Find posts where someone is asking for a product like yours, scored 1-100, with reply drafts.

- Trust score: 74/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@launchengine-dev/mcp`: 74/100 (this document), [markdown](https://verifymcp.io/servers/naman6019-launchengine-dev/launchengine-dev-mcp.md), [page](https://verifymcp.io/servers/naman6019-launchengine-dev/launchengine-dev-mcp)

## Channel facts

- Registry: `npm`
- Package: `@launchengine-dev/mcp`
- Version: `0.0.3`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 30 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 26 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 959 tokens (~159/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the LaunchEngine.dev MCP server?

LaunchEngine.dev runs locally as an npm package, launched with npx -y @launchengine-dev/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add naman6019-launchengine-dev -- npx -y @launchengine-dev/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "naman6019-launchengine-dev": {
      "command": "npx",
      "args": [
        "-y",
        "@launchengine-dev/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "naman6019-launchengine-dev": {
      "command": "npx",
      "args": [
        "-y",
        "@launchengine-dev/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add naman6019-launchengine-dev -- npx -y @launchengine-dev/mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "naman6019-launchengine-dev": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@launchengine-dev/mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add naman6019-launchengine-dev --command npx --arg -y --arg @launchengine-dev/mcp
```

### Hermes

```yaml
mcp_servers:
  naman6019-launchengine-dev:
    command: "npx"
    args: ["-y", "@launchengine-dev/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "naman6019-launchengine-dev": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@launchengine-dev/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add naman6019-launchengine-dev -t stdio -c npx -a -y @launchengine-dev/mcp
```

### Other

```json
{
  "mcpServers": {
    "naman6019-launchengine-dev": {
      "command": "npx",
      "args": [
        "-y",
        "@launchengine-dev/mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 69, −4)

- [security regression] CVE-2023-54404 affects this package: high
- [security regression] Known CVEs: pass → fail

### 2026-10-22 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 72, +3)

- [functional improvement] Stability: unverified → 0.23

## MCP tools (6)

### `list_projects` (~47 tokens)

List projects

List the projects in the workspace: name, URL, description, target ICP and competitors. Free. Call this first - every other tool takes a project_id or a signal id that starts here.

### `get_credit_balance` (~42 tokens)

Get credit balance

Return the workspace's credit balance and plan. Free; call it before a metered tool (find_intent_signals, draft_reply cost 1 credit each).

### `find_intent_signals` (~377 tokens)

Find intent signals

Return scored posts from Reddit, Hacker News and the open web where someone is asking for a product like the project's - highest intent score (1-100) first, with the matched query and the reasons for the score. Reads signals found by earlier scans; pass scan: true to search live sources first. Costs 1 credit.

Input parameters:

- `include_muted` (boolean): Include posts from authors and subreddits the workspace has muted. Default false, matching the dashboard.
- `limit` (integer): Maximum signals to return, 1-100, highest score first. With scan: true it also caps results fetched per search query.
- `min_intent_score` (integer): Lowest intent score to return, 1-100. 90+ is asking for exactly this now, 75-89 is comparing options, 60-74 is related; below 60 is mostly noise.
- `platforms` (array): Sources to include. "web" is pages found through search indexes. "twitter" is accepted but not scanned yet, so it returns nothing.
- `project_id` (string, required): Project to search. Get ids from list_projects.
- `scan` (boolean): Refresh from live sources before returning. Slower, and spends one of the workspace's daily scans (free plan: one a day across all projects) on top of the call's credit. Leave false to read signals f…
- `since_days` (integer): Only posts from the last N days, 1-365.
- `status` (string): Only signals in this state. Omit for all states.
- `web_mode` (string): Only used with scan: true. "single" queries one web-search provider; "parallel" queries every configured provider and merges the results, for wider coverage at more upstream cost.

### `get_intent_details` (~57 tokens)

Get signal details

Fetch one signal by id: the post's title, snippet, URL, author, score, reasons, engagement and any saved draft reply. Free.

Input parameters:

- `intent_id` (string, required): Signal id, from find_intent_signals.

### `draft_reply` (~130 tokens)

Draft a reply

Draft a reply to a signal's post for a person to review and post. Never posts anything. The draft helps with the poster's problem and names no product. Saved on the signal, replacing any earlier draft. Costs 1 credit.

Input parameters:

- `intent_id` (string, required): Signal to reply to, from find_intent_signals.
- `tone` (string): Writing style: "consultative" (helpful, conversational), "direct" (gets to the point), or "technical" (practitioner detail). In every tone the draft helps with the problem and names no product, yours…

### `subscribe_to_keyword` (~146 tokens)

Monitor a keyword

Add a keyword for a project's scans to search, or update one already added. A project with at least one keyword is included in the daily scheduled scan (06:00 UTC). Free.

Input parameters:

- `competitors` (array): Competitor names to store with this keyword, up to 25; replaces the stored list. Scans currently search the project's own competitor list, not this one.
- `keyword` (string, required): Phrase to search for in every scan of this project, 2-120 characters, e.g. "alternative to Mixpanel". Subscribing the same keyword again updates it.
- `project_id` (string, required): Project to monitor for. Get ids from list_projects.

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/naman6019-launchengine-dev/launchengine-dev-mcp#diagnostics

## Score history

- 2026-11-05: 74
- 2026-11-04: 74
- 2026-11-03: 73
- 2026-11-02: 73
- 2026-11-01: 72
- 2026-10-31: 72
- 2026-10-30: 72
- 2026-10-29: 71
- 2026-10-28: 71
- 2026-10-27: 70
- 2026-10-26: 70
- 2026-10-25: 69
- 2026-10-24: 69
- 2026-10-23: 73
- 2026-10-22: 73
- 2026-10-21: 72
- 2026-10-20: 69
- 2026-10-19: 69
- 2026-10-18: 69
- 2026-10-17: 69
- 2026-10-16: 69
- 2026-10-15: 69
- 2026-10-14: 69
- 2026-10-13: 38
- 2026-10-12: 38
- 2026-10-11: 38

## Common questions

### What is the LaunchEngine.dev MCP server?

LaunchEngine.dev is an MCP server listed in the public MCP registry as io.github.Naman6019/launchengine-dev. Find posts where someone is asking for a product like yours, scored 1-100, with reply drafts. This page covers its npm package (@launchengine-dev/mcp).

### Is the LaunchEngine.dev MCP server safe to use?

LaunchEngine.dev scores 74 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 LaunchEngine.dev MCP server expose?

LaunchEngine.dev exposes 6 tools: list_projects, get_credit_balance, find_intent_signals, get_intent_details, draft_reply, subscribe_to_keyword. Their descriptions and schemas cost roughly 799 tokens of context every time the server is loaded.

### Is the LaunchEngine.dev MCP server still maintained?

LaunchEngine.dev 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 LaunchEngine.dev MCP server under?

LaunchEngine.dev declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@launchengine-dev/mcp
- Socket report: https://socket.dev/npm/package/@launchengine-dev/mcp
- Repository: https://github.com/Naman6019/launchengine-mcp
- Website: https://launchengine.dev/docs/agents
- Changelog RSS feed: https://verifymcp.io/servers/naman6019-launchengine-dev/launchengine-dev-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/naman6019-launchengine-dev/launchengine-dev-mcp.json
- HTML version of this page: https://verifymcp.io/servers/naman6019-launchengine-dev/launchengine-dev-mcp