LaunchEngine.dev
NPM · @LAUNCHENGINE-DEV/MCP
Find posts where someone is asking for a product like yours, scored 1-100, with reply drafts.
Available components
Last scanned (2 hours ago)
Scores higher than 48% of npm servers
Category Marketing and SEO
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
- 30 of 93 dependencies flagged as unhealthy. 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 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 Usability71
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
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.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 24 Oct 26 −4
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 22 Oct 26 +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.
- 21 Oct 26 +3
- Stability: unverified → 0.23 ▲ 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 5 Nov 2026 · Analysed npm/@launchengine-dev/mcp@0.0.3
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 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
draft_reply Draft a reply ~130
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.
| Name | Type | Req | Description |
|---|---|---|---|
| intent_id | string | yes | 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… |
No output schema declared.
No examples provided.
find_intent_signals Find intent signals ~377
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
get_credit_balance Get credit balance ~42
Return the workspace's credit balance and plan. Free; call it before a metered tool (find_intent_signals, draft_reply cost 1 credit each).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_intent_details Get signal details ~57
Fetch one signal by id: the post's title, snippet, URL, author, score, reasons, engagement and any saved draft reply. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| intent_id | string | yes | Signal id, from find_intent_signals. |
No output schema declared.
No examples provided.
list_projects List projects ~47
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
subscribe_to_keyword Monitor a keyword ~146
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | Project to monitor for. Get ids from list_projects. |
No output schema declared.
No examples provided.
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.
npm · @launchengine-dev/mcp
claude mcp add naman6019-launchengine-dev -- npx -y @launchengine-dev/mcp
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.