cli@0.1.32

VERIFIED· startup only

Publisher claims: "OpenNodes (ONP) client: search verified AI nodes, pre-price chains, invoke with signed receipts; OpenAI-compatible gateway with onp/auto routing; stdio MCP server for Cursor, VS Code, and Claude Desktop" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher opennodes · publishing for 49 daysInstalls 6,086Last detonated 5 h ago
$claude mcp add cli -- npx -y @opennodes/cli
WatchReport an issue

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
Needs
--no-env-keys — give it to the server where it runs, through vet-skills run --secrets, so the value never enters the server's environment. Never paste a credential into a chat, a ticket or a report.

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; at startup it asked for --no-env-keys
Where it talks to
opennodes.io (its own)
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 opennodes.io, its own; the guard pins the network to what the honeypot saw and logs every call.

$vet-skills run --net declared -- npx -y @opennodes/cli

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

What changed since 0.1.31

vet-skills diff cli 0.1.31 0.1.32

In the sandbox, this version reached for nothing 0.1.31 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-19 and scored it 90/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 (it asks for --no-env-keys); 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 · 22 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
1.8sprocessdependency install exit 0
22sclaimedstartup only: exited before answering, asking for --no-env-keys
22sprocessscript backend runs setup only
22sprocessno install scripts to re-run

Static findings

MEDIUM
File type combined with upload actionbin.js:69 · File type combined with upload action — agent may exfiltrate local data filesif (pii_masked) console.log(`pii masked before sending: ${describeMaskCounts(pii_masked) || 'nothing found'}`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.
AST07
MEDIUM
npx invocation of non-well-known packagebin.js:81 · npx invocation of non-well-known package — may execute untrusted code// Installed from npm → portable npx form; running from a checkout → absolute path.Fix: Pin versions and sources; vendor anything fetched at install time.
AST06

Cost to the agent

Instructions loaded
≈85 tok
1 file · 10 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

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 @opennodes/cli@0.1.32 as of 4 h ago. This is the package itself, not its dependencies.

cli@0.1.32 safety verdict: Verified (startup only) — KillerSkills