Is meshingly-mcp@0.5.2 safe to install?

Skills/npm/meshingly-mcp

meshingly-mcp@0.5.2

VERIFIED

Publisher claims: "End-to-end encrypted relay that lets AI coding sessions on different machines message each other." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server) · listed in the official MCP RegistryPublisher meshingly · publishing for 21 daysInstalls 0Last detonated 3d ago

$claude mcp add meshingly-mcp -- npx -y meshingly-mcp

Watch Report an issue

Coverage

Server started and answered tools/list.

Tested: MCP initialize and tools/list · every tool description, for hidden instructions · every file read, file written and host contacted by what ran
Not tested: what the tools do when called with real credentials

Before you give it your token

It will ask for: no credential variables read in the code
Where it talks to: meshingly.com (its own)
What the honeypot saw: no credential files read · no network
What we could not test: what the tools do when called with real credentials

Reasonable to connect. No credential asked for, no third-party host named, Server started and answered tools/list.

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios) on 2026-11-12 and scored it 88/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 20 s · 2 scenarios · 0 deviations

t+CategoryObserved action

0.0sprocessno install scripts in bundle

20sclaimed17 tools: meshingly_status, meshingly_create, meshingly_join, meshingly_peers, meshingly_send, meshingly_receive, meshingly_handoff, meshingly_queue, meshingly_claim, meshingly_release, meshingly_watch_start, meshingly_watch_stop, meshingly_watch_status, meshingly_journal, meshingly_recall, meshingly_settings, meshingly_done

20sprocessscript backend runs setup only

20sprocessno install scripts to re-run

Static findings

CRITICAL

False input termination markerSKILL.md:5 · False input termination marker — attempts to end user input section---Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.

AST01

MEDIUM

Process kill commanddist/background.js:70 · Process kill command — agent can terminate processes

/** Ends a process and everything it started: with `shell: true` the pid is the shell's, and a plain kill would leave the agent running. */

Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.

AST05

MEDIUM

npx invocation of non-well-known packagedist/settings-cli.js:24 · npx invocation of non-well-known package — may execute untrusted code

npx -y meshingly-mcp settings set <key>        leave the value out to be asked for it (no quoting needed: handy for a command with quotes or $)

Fix: Pin versions and sources; vendor anything fetched at install time.

AST06

MEDIUM

npx invocation of non-well-known packagedist/connection.js:204 · npx invocation of non-well-known package — may execute untrusted code: ` npx -y meshingly-mcp settings set ${k} (it asks for the value; the user types or pastes exactly: ${String(v)})`;Fix: Pin versions and sources; vendor anything fetched at install time.

AST06

MEDIUM

npx invocation of non-well-known packagedist/connection.js:203 · npx invocation of non-well-known package — may execute untrusted code? ` npx -y meshingly-mcp settings set ${k} ${arg}`Fix: Pin versions and sources; vendor anything fetched at install time.

AST06

MEDIUM

npx invocation of non-well-known packagedist/server.js:371 · npx invocation of non-well-known package — may execute untrusted code// `npx meshingly-mcp watch`: a command-line helper that wakes a session when work is queued. stdout stays free ofFix: Pin versions and sources; vendor anything fetched at install time.

AST06

MEDIUM

npx invocation of non-well-known packagedist/settings-cli.js:30 · npx invocation of non-well-known package — may execute untrusted codenpx -y meshingly-mcp settings set autoResume true continue queued work automatically after the limit is backFix: Pin versions and sources; vendor anything fetched at install time.

AST06

MEDIUM

npx invocation of non-well-known packagedist/settings-cli.js:22 · npx invocation of non-well-known package — may execute untrusted codenpx -y meshingly-mcp settings show every setting and where its value comes fromFix: Pin versions and sources; vendor anything fetched at install time.

AST06

MEDIUM

npx invocation of non-well-known packagedist/update.js:112 · npx invocation of non-well-known package — may execute untrusted code

? "To update, make sure the MCP command ends in meshingly-mcp@latest (npx -y meshingly-mcp@latest), then restart the session"

Fix: Pin versions and sources; vendor anything fetched at install time.

AST06

MEDIUM

npx invocation of non-well-known packagedist/settings-cli.js:25 · npx invocation of non-well-known package — may execute untrusted codenpx -y meshingly-mcp settings reset back to the defaultsFix: Pin versions and sources; vendor anything fetched at install time.

AST06

MEDIUM

npx invocation of non-well-known packagedist/settings-cli.js:23 · npx invocation of non-well-known package — may execute untrusted codenpx -y meshingly-mcp settings set <key> <value>Fix: Pin versions and sources; vendor anything fetched at install time.

AST06

MEDIUM

Process kill commanddist/background.js:90 · Process kill command — agent can terminate processes* refuse to start a new watcher and, worse, stop would kill a stranger.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.

AST05

MEDIUM

npx invocation of non-well-known packagedist/connection.js:150 · npx invocation of non-well-known package — may execute untrusted code"They can start it themselves in a terminal: npx -y meshingly-mcp watch",Fix: Pin versions and sources; vendor anything fetched at install time.

AST06

MEDIUM

npx invocation of non-well-known packagedist/update.js:113 · npx invocation of non-well-known package — may execute untrusted code

: "To update, they reinstall the way they installed it (npx -y meshingly-mcp@latest, or the plugin), then restart the session";

Fix: Pin versions and sources; vendor anything fetched at install time.

AST06

MEDIUM

npx invocation of non-well-known packagedist/watch.js:36 · npx invocation of non-well-known package — may execute untrusted code

Usage: npx -y meshingly-mcp watch [--cmd "claude -p"] [--interval 60] [--once] [--from-peers] [--on-question stop|recommended] [--dir <project>]

Fix: Pin versions and sources; vendor anything fetched at install time.

AST06

MEDIUM

npx invocation of non-well-known packagedist/watch.js:56 · npx invocation of non-well-known package — may execute untrusted codeEvery option has a setting that is used when the flag is absent: npx -y meshingly-mcp settingsFix: Pin versions and sources; vendor anything fetched at install time.

AST06

Cost to the agent

Instructions loaded

≈61 tok

1 file · 21 in bundle

Tool list per prompt

≈2,227 tok

17 tools · 131 per tool

Handshake

498 ms

launch to tools/list, stdio

Undocumented tools

description under 20 chars · avg 197

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

No advisories in OSV for meshingly-mcp@0.5.2 as of 3d ago. This is the package itself, not its dependencies.