ue-mcp@1.4.14
VERIFIED· startup onlyPublisher claims: "Unreal Engine MCP server - 31 tools, 3714+ actions for AI-driven editor control" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Startup only; authenticated tool behavior not tested.- Tested
- server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
- Not tested
- the tool list (the server exited before answering) · what the tools do when called with real credentials
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
- no credential variables read in the code
- Where it talks to
- ue-mcp.com (its own)Also fab.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- the tool list (the server exited before answering) · what the tools do when called with real credentials
Connect it under the guard. Startup only; authenticated tool behavior not tested. The code names no credential variable and talks to ue-mcp.com, its own; the guard pins the network to what the honeypot saw and logs every call.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
What changed since 1.4.13
vet-skills diff ue-mcp 1.4.13 1.4.14In the sandbox, this version reached for nothing 1.4.13 did not. Compared from the two recorded runs, not from source.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-18 and scored it 80/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 37 s · 2 scenarios · 0 deviationsStatic findings
* The same flow is offered inside `npx ue-mcp init` when the user opts intoFix: Pin versions and sources; vendor anything fetched at install time.`Skip - feedback submissions will refuse until I run \`npx ue-mcp auth\` or call with author="bot"`,Fix: Pin versions and sources; vendor anything fetched at install time.* through npx under `gate` without lifting it. npx ignoresFix: Pin versions and sources; vendor anything fetched at install time.reload_bridge: specBp("mutate", "Hot-reload Python bridge handlers from disk.", "reload_handlers"),Fix: Pin versions and sources; vendor anything fetched at install time./** Where effectiveNpx comes from; with nothing installed npx fetches the registry's latest. */Fix: Pin versions and sources; vendor anything fetched at install time.info(`Submissions will refuse until you run \`npx ue-mcp auth\` or call with author="bot".`);Fix: Pin versions and sources; vendor anything fetched at install time.const usage = `npx ue-mcp ${def.name} mode <${def.values.join("|")}> [--editor <name>]`;Fix: Pin versions and sources; vendor anything fetched at install time.info(`Skipped. Run npx ue-mcp auth to set this up later, or pass author="bot" at submit time.`);Fix: Pin versions and sources; vendor anything fetched at install time.* through npx under `gate` without lifting it. npx ignoresFix: Pin versions and sources; vendor anything fetched at install time.console.log(` ${DIM}to post anonymously as the ue-mcp-feedback bot.${RESET}`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why./** Walk up from cwd; the first node_modules/ue-mcp is what npx resolves locally. */Fix: Pin versions and sources; vendor anything fetched at install time.console.log(` ${DIM}Clear: npx ue-mcp ${def.name} mode ${CLEAR_WORDS[0]} [--editor <name>]${RESET}`);Fix: Pin versions and sources; vendor anything fetched at install time.* `npx ue-mcp` (an npx server whose args include "ue-mcp" with no @version pinFix: Pin versions and sources; vendor anything fetched at install time./** Walk up from cwd; the first node_modules/ue-mcp is what npx resolves locally. */Fix: Pin versions and sources; vendor anything fetched at install time./** Client entries whose npx launch that gate refuses for a new release. */Fix: Pin versions and sources; vendor anything fetched at install time.* silently shadows the global install (npx prefers the local copy, so updatingFix: Pin versions and sources; vendor anything fetched at install time.* `npx ue-mcp auth` - interactive GitHub device-flow auth so feedback(submit)Fix: Pin versions and sources; vendor anything fetched at install time.console.log(` ${DIM}Example: npx ue-mcp resolve 16${RESET}`);Fix: Pin versions and sources; vendor anything fetched at install time.warn("shim", `the bridge is ${version}, newer than this ue-mcp ${packageVersion()}, and npx was not found beside node to run it`);Fix: Pin versions and sources; vendor anything fetched at install time.…errides and resolved parameter values. DataTable and CompositeDataTable require .json or .csv; format overrides their serializer. Relative outputPath resolves against the project directory; missing folders are created. replaceExisting defa…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.* that owns it (an npx cache). It never goes into the project or the workingFix: Pin versions and sources; vendor anything fetched at install time.…n a content path and compare disk vs AssetRegistry (including in-memory pending-kill entries). Returns onDiskCount, inMemoryIncludedCount, ghostCount and paths.", "d…Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.// 2. A project-local node_modules/ue-mcp shadows every other install (npxFix: Pin versions and sources; vendor anything fetched at install time.fail(`Local shadow: node_modules/ue-mcp@${preDoctor.localShadow.version} in ${shadowProjectRoot}. npx runs it, not ${aligned}.`);Fix: Pin versions and sources; vendor anything fetched at install time.* that owns it (an npx cache). It never goes into the project or the workingFix: Pin versions and sources; vendor anything fetched at install time.console.log(` ${BOLD}Usage:${RESET} npx ue-mcp resolve <issue-number>`);Fix: Pin versions and sources; vendor anything fetched at install time.…l Editor gracefully (asks the editor to quit itself via the bridge; never an OS kill of an editor). Acts only on the editor for the loaded project, resolved from the…Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.// A bare `npx ue-mcp update` runs the stable line. A binary bridge from a newerFix: Pin versions and sources; vendor anything fetched at install time.* npx ue-mcp resolve <issue-number>Fix: Pin versions and sources; vendor anything fetched at install time.`3. Verify with \`npx tsc --noEmit\``,Fix: Pin versions and sources; vendor anything fetched at install time.// kill timeout. A server also serving flows over HTTP stays up for those.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."Bash(npx tsc --noEmit)",Fix: Pin versions and sources; vendor anything fetched at install time./** npm's npx entry beside this node, which runs without a shell; null when it is not there. */Fix: Pin versions and sources; vendor anything fetched at install time.…"prepublishOnly": "node -e \"fs.rmSync('dist',{recursive:true,force:true})\" && npx tsc && tsx scripts/generate-default-config.ts && tsx scripts/generate-tool-metadata…Fix: Pin versions and sources; vendor anything fetched at install time./** The command line that runs the daemon: this entry, or `npx ue-mcp@<version>` for another version. */Fix: Pin versions and sources; vendor anything fetched at install time.`Run \`ue-mcp update\` (or npm i -g ue-mcp@latest).`);Fix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.` Update the npm package to match the plugin: 'npm install ue-mcp@latest'.`);Fix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.step(`Newer prereleases: npm install -g ue-mcp@${tag}. Back to stable: npm install -g ue-mcp@latest.`);Fix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed....toggle("agent-guides", "Write the ue-mcp block into AGENTS.md, GEMINI.md or .github/copilot-instructions.md for the clients configured"),Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
Not checked against OSV yet; the weekly check has not reached this version.