Launchframe MCP Server

@launchframe/mcp npm v1.1.14

Published by @launchframe — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

LaunchFrame MCP Server — knowledge tools for AI agents building LaunchFrame projects

Trust grade
B
82/100
Last scanned get badge →
Trust
B · 82/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Critical
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
B Why this grade threat 94 − adoption risk = 82/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 6.3 = 94. What the published surface and source actually contain:

PointsWhat was foundCategory
−6.3 Untrusted input concatenated into a command sink MTC-SRC-009 injection

2. Client adoption risk — 94 − 12 = 82. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−10 capability blast radius (critical) — client exposure if the model is manipulated
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 3

critical Completed toxic-flow trifecta across toolsMTC-FLOW-002

This server (without client built-ins) exposes a complete data-exfiltration chain: cli_docker_logs → env_get_conventions → webhook_get_architecture. Untrusted input is ingested, private data is read, and it can be sent to an external sink via the agent composing the tools (→). Static analysis proves the primitive exists, not that a specific run will occur.

Fix: Remove one leg of the trifecta: isolate untrusted-input tools from secret-reading tools and from egress tools, or require human approval between them.

Location: flow cli_docker_logs → env_get_conventions → webhook_get_architecture

high Shell/command execution in server code (dist/tools/cli.js)MTC-SRC-002

In the server's implementation (`dist/tools/cli.js:2`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: port { execSync } from 'child_process'; /** * Request human confirmation for a destructive action via MCP elicitation.

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/tools/cli.js

medium Untrusted input concatenated into a command sink (dist/tools/cli.js)MTC-SRC-009

In the server's implementation (`dist/tools/cli.js:44`): A shell/process command assembled from concatenated or interpolated values is command injection when any part is attacker-influenced — the OWASP canonical RCE flow. Verify what reaches the interpolated value. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: const output = execSync(`launchframe docker:up${svc} --detach`, { cwd: projectPath, encoding: 'utf8' });

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/tools/cli.js

Tools 56

Each tool and what it can reach — statically extracted from the published source.

  • cli_docker_logsingests untrusted input
  • cli_waitlist_logsingests untrusted input
  • env_get_conventionsreads sensitive data
  • webhook_get_architecturenetwork egress
  • webhook_scaffold_handlernetwork egress
  • architecture_get_overviewno sensitive capability
  • auth_get_decorator_usageno sensitive capability
  • auth_get_guard_usageno sensitive capability
  • auth_get_overviewno sensitive capability
  • cli_cache_clearno sensitive capability
Show 46 more tools ↓
  • cli_cache_infono sensitive capability
  • cli_cache_updateno sensitive capability
  • cli_database_queryno sensitive capability
  • cli_deploy_buildno sensitive capability
  • cli_deploy_sync_featuresno sensitive capability
  • cli_deploy_upno sensitive capability
  • cli_dev_add_userno sensitive capability
  • cli_dev_logono sensitive capability
  • cli_dev_npm_installno sensitive capability
  • cli_docker_buildno sensitive capability
  • cli_docker_destroyno sensitive capability
  • cli_docker_downno sensitive capability
  • cli_docker_upno sensitive capability
  • cli_migration_createno sensitive capability
  • cli_migration_revertno sensitive capability
  • cli_migration_runno sensitive capability
  • cli_module_addno sensitive capability
  • cli_module_listno sensitive capability
  • cli_service_addno sensitive capability
  • cli_service_listno sensitive capability
  • cli_waitlist_deployno sensitive capability
  • cli_waitlist_downno sensitive capability
  • cli_waitlist_upno sensitive capability
  • credits_get_add_patternno sensitive capability
  • credits_get_deduction_patternno sensitive capability
  • credits_get_monetization_strategiesno sensitive capability
  • cron_get_patternno sensitive capability
  • cron_scaffold_jobno sensitive capability
  • database_schemano sensitive capability
  • email_get_conventionsno sensitive capability
  • email_scaffold_sendno sensitive capability
  • email_scaffold_templateno sensitive capability
  • entity_get_conventionsno sensitive capability
  • entity_scaffold_typeormno sensitive capability
  • feature_gates_get_check_patternno sensitive capability
  • feature_gates_get_overviewno sensitive capability
  • module_get_structureno sensitive capability
  • module_scaffold_nestjsno sensitive capability
  • queue_get_namesno sensitive capability
  • queue_scaffold_processorno sensitive capability
  • queue_scaffold_producerno sensitive capability
  • rbac_get_guard_usageno sensitive capability
  • rbac_get_overviewno sensitive capability
  • rbac_get_permission_patternno sensitive capability
  • subscriptions_get_plans_overviewno sensitive capability
  • variant_get_overviewno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.1.14 latest B 82/100 3 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: B · 82/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/launchframe-mcp/badge.svg)](https://mcptrustchecker.com/registry/launchframe-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/launchframe-mcp"><img src="https://mcptrustchecker.com/registry/launchframe-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/launchframe-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @launchframe/mcp --online

Use the free API → How scoring works

More in Developer Tools