mcp@15.3.2

VERIFIED· not started

Publisher claims: "Experimental package — This module provides a MCP Server" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher o3r · publishing for 469 daysInstalls 5,015Last detonated 14 h ago
$claude mcp add mcp -- npx -y @o3r/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 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
O3R_MCP_GITHUB_TOKENConfiguration, not credentials: O3R_MCP_CACHE_MAX_AGE, O3R_MCP_CACHE_PATH, O3R_MCP_LOG_LEVEL
Where it talks to
no vendor host named in the code
What we saw when it ran
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard. It asks for O3R_MCP_GITHUB_TOKEN and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.

$vet-skills run --net declared -- npx -y @o3r/mcp

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

What changed since 15.3.1

vet-skills diff mcp 15.3.1 15.3.2

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

15.3.1 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-19 and scored it 95/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 · 36 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
36sprocessdependency install exit 1 · (Use `node --trace-warnings ...` to show where the warning was created) npm error Cannot read properties of null (reading 'edgesOut') npm error A complete log of this run can be found in: /tmp/ks-detonate-CzRRId/task/home/.npm/_logs/2026-11-19T10_33_21_400Z-debug-0.log
36sclaimednot started: dependency install failed (exit 1); the server itself was not observed
36sprocessscript backend runs setup only
36sprocessno install scripts to re-run

Static findings

No findings across 708 lines in 21 files.

Cost to the agent

Instructions loaded
≈47 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 @o3r/mcp@15.3.2 as of 14 h ago. This is the package itself, not its dependencies.

mcp@15.3.2 safety verdict: Verified (not started) — KillerSkills