mcp@0.5.211

VERIFIED· not started

Publisher claims: "Phenomenal MCP bridge — connects a stdio-only MCP client to the Phenomenal MCP server over Streamable HTTP, with browser sign-in." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher phenomenalorg · publishing for 70 daysInstalls 12,876Last detonated 1 h ago
$claude mcp add mcp -- npx -y @phenomenalorg/mcp
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What changed since 0.5.207

vet-skills diff mcp 0.5.207 0.5.211

In the sandbox, this version reached for nothing 0.5.207 did not. Compared from the two recorded runs, not from source.

0.5.207 was not run in the sandbox (install failed); the comparison covers what static analysis recorded only.

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; not started: dependency install failed; the server itself was not observed) on 2026-11-18 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; 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 · 1 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.9sprocessdependency install exit 1 · npm error code EUNSUPPORTEDPROTOCOL npm error Unsupported URL Type "workspace:": workspace:* npm error A complete log of this run can be found in: /tmp/ks-detonate-o38lz2/task/home/.npm/_logs/2026-11-18T18_39_32_335Z-debug-0.log
0.9sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.9sprocessscript backend runs setup only
0.9sprocessno install scripts to re-run

Static findings

MEDIUM
npx invocation of non-well-known packagedist/cli.js:102 · npx invocation of non-well-known package — may execute untrusted code' npx @phenomenalorg/mcp [<url>] [--url <url>] [--skill [dir]] [--logout]',Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
File permission modification commandpackage.json:38 · File permission modification command — agent changes file ownership/permissions"build": "node scripts/copy-skill.mjs && tsc -p tsconfig.build.json && chmod +x dist/cli.js",Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05

Cost to the agent

Instructions loaded
≈1,417 tok
1 file · 21 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 @phenomenalorg/mcp@0.5.211 as of 36 min ago. This is the package itself, not its dependencies.