mcp@2.0.15
VERIFIED· install onlyPublisher claims: "Expose HazelJS tools as MCP (Model Context Protocol) tools over STDIO" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-10 and scored it 93/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 · 0 s · 1 scenarios · 0 deviationsStatic findings
export type { McpClientOptions, McpServerConfig, McpTransportConfig, McpStdioTransportConfig, McpHttpTransportConfig, McpRemoteTool, McpToolCallResult, } from './client/types';Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.No other findings across 1,670 lines in 19 files.
Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
No advisories in OSV for @hazeljs/mcp@2.0.15 as of 5d ago. This is the package itself, not its dependencies.