mcp-dev@18.1.11
VERIFIED· startup onlyPublisher claims: "A model context protocol (MCP) server for Umbraco CMS" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Startup only; authenticated tool behavior not tested.- Tested
- server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
- Not tested
- the tool list (the server exited before answering) · what the tools do when called with real credentials
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
- no credential variables read in the code
- Where it talks to
- no vendor host named in the codeAlso githubusercontent.com, mathiasbynens.be, safaribooksonline.com, openapis.org — 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
- the tool list (the server exited before answering) · what the tools do when called with real credentials
Connect it under the guard. Startup only; authenticated tool behavior not tested. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
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; startup only; authenticated tool behavior not tested) on 2026-11-13 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 · 58 s · 2 scenarios · 0 deviationsStatic findings
"test:e2e": "npx playwright test --config tests/cms-hosted-e2e/playwright.config.ts",Fix: Pin versions and sources; vendor anything fetched at install time."umbraco:stop": "lsof -ti :44391 | xargs kill 2>/dev/null; lsof -ti :56472 | xargs kill 2>/dev/null",Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."umbraco:stop": "lsof -ti :44391 | xargs kill 2>/dev/null; lsof -ti :56472 | xargs kill 2>/dev/null",Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."test:e2e": "npx playwright test --config tests/cms-hosted-e2e/playwright.config.ts",Fix: Pin versions and sources; vendor anything fetched at install time."test:e2e": "npx playwright test --config tests/cms-hosted-e2e/playwright.config.ts",Fix: Pin versions and sources; vendor anything fetched at install time."umbraco:stop": "lsof -ti :44391 | xargs kill 2>/dev/null; lsof -ti :56472 | xargs kill 2>/dev/null",Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.Cost to the agent
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 @umbraco-cms/mcp-dev@18.1.11 as of 16 h ago. This is the package itself, not its dependencies.