Skills/npm/mcp-server

mcp-server@2.3.7

VERIFIED· not started

Publisher claims: "Model Context Protocol (MCP) server for Prenta CMS — gives AI agents read/write access to your CMS over stdio" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server)Publisher prenta · publishing for 107 daysInstalls 2,278Last detonated 3d ago
$claude mcp add mcp-server -- npx -y @prenta/mcp-server
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
PRENTA_API_KEYConfiguration, not credentials: PRENTA_BASE_URL
Where it talks to
no vendor host named in the codeAlso your-site.com — not the publisher's domain; check what for before connecting.
What the honeypot saw
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, and read the third-party hosts first. The code names your-site.com as well as its own vendor. The guard injects PRENTA_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.

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

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

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-11 and scored it 92/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 · 7 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
6.4sprocessdependency 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-J17i3H/task/home/.npm/_logs/2026-11-11T19_14_48_911Z-debug-0.log
6.4sclaimednot started: dependency install failed (exit 1); the server itself was not observed
6.4sprocessscript backend runs setup only
6.5sprocessno install scripts to re-run

Static findings

MEDIUM
Process kill commanddist/client.d.ts:32 · Process kill command — agent can terminate processes* Present only when `enabled` is `false`: `'settings'` = the kill switch inFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05

No other findings across 7,086 lines in 25 files.

Cost to the agent

Instructions loaded
≈64 tok
1 file · 25 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 @prenta/mcp-server@2.3.7 as of 3d ago. This is the package itself, not its dependencies.