plurnk-mcp@3.4.0
VERIFIED· install onlyPublisher claims: "Current Model Context Protocol host module for Plurnk." 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-13 and scored it 83/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
// wrapper can group-kill the whole tree, grandchildren included;Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.export declare const rawSessionBinding: (alias: string, definition: McpServerDefinition, environ: NodeJS.ProcessEnv) => string | undefined;Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.".env.defaults"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.export declare const rawWorkspaceBinding: (alias: string, definition: McpServerDefinition, environ: NodeJS.ProcessEnv) => string | readonly string[] | undefined;Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.constructor(definition: McpServerDefinition, environ?: NodeJS.ProcessEnv, options?: ServerConnectionOptions);Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.export declare const matchesWorkspaceBinding: (alias: string, definition: McpServerDefinition, environ: NodeJS.ProcessEnv, workspaceName: string | undefined) => boolean;Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.export declare const assertWorkspaceDefinitionScope: (alias: string, definition: McpServerDefinition, workspaceName: string | undefined, environ: NodeJS.ProcessEnv) => void;Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.return Results.failure(OWNER, "value-whole", 400, "kill retires the whole MCP server definition.", {}, { retryable: false });Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.…"src/**/*.test.ts\"", "test:intg": "node --conditions=plurnk-dev --env-file=.env.defaults --env-file-if-exists=../plurnk-execs/.env.defaults --experimental-test…Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.…int": "tsc --noEmit", "test:unit": "node --conditions=plurnk-dev --env-file=.env.defaults --env-file-if-exists=../plurnk-execs/.env.defaults --experimental-test…Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.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 @plurnk/plurnk-mcp@3.4.0 as of 14 h ago. This is the package itself, not its dependencies.