create-umbraco-mcp-server@1.0.0
CAUTION· startup onlyPublisher claims: "Create a new Umbraco MCP server project" 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: Caution 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
AUTHORIZE_PATHDEFAULT_CLIENT_SECRETNODE_TLS_REJECT_UNAUTHORIZEDTOKEN_PATHUMBRACO_ADMIN_PASSWORDUMBRACO_CLIENT_SECRETor--admin-passwordConfiguration, not credentials: JEST_WORKER_ID, LOGIN_PATH, SWAGGER_UI_BASE_PATH, UMBRACO_ADMIN_EMAIL, UMBRACO_BASE_URL, UMBRACO_CLIENT_ID, UMBRACO_CLOUD_REGION, UMBRACO_CLOUD_ROUTING_ENABLED, UMBRACO_EXPECTED_MAJOR, UMBRACO_OPENAPI_SPEC, UMBRACO_READONLY, USE_MOCK_API, USE_MOCK_MCP_CHAIN, USER_PATH- Where it talks to
- no vendor host named in the codeAlso nuget.org, umbraco.com — not the publisher's domain; check what for before connecting.
- What we saw when it ran
- 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 with a scoped credential, under the guard, and read the third-party hosts first. The code names nuget.org, umbraco.com as well as its own vendor. The guard injects AUTHORIZE_PATH, DEFAULT_CLIENT_SECRET, NODE_TLS_REJECT_UNAUTHORIZED, TOKEN_PATH, UMBRACO_ADMIN_PASSWORD, UMBRACO_CLIENT_SECRET only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
What changed since 1.0.0-beta.47
vet-skills diff create-umbraco-mcp-server 1.0.0-beta.47 1.0.0In the sandbox, this version reached for nothing 1.0.0-beta.47 did not. Compared from the two recorded runs, not from source.
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; startup only; authenticated tool behavior not tested) on 2026-11-19 and scored it 70/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Access to sensitive file paths; Access to sensitive file paths. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 36 s · 2 scenarios · 0 deviationsStatic findings
const envPath = path9.join(projectDir, ".env");Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# With .env file (recommended)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."\nRun 'npx @umbraco-cms/create-umbraco-mcp-server <name>' to create a new project first."Fix: Pin versions and sources; vendor anything fetched at install time.return { url: envUrl, source: ".env" };Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// `npm run generate` stamps from the Umbraco instance in `.env`;Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.* "◇ injected env (0) from .env"). This server's stdout carries MCP protocolFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// Loads .env, so the transformer below can ask the connected Umbraco whichFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.* `.env`. It cannot come from the spec — every Umbraco spec hard-codesFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Custom .env pathFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.they are read from `.env`.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.**Never pass secrets as CLI arguments.** Use a `.env` file or the MCP config `env` block.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// - Transform the response formatFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.console.log(pc4.green(` Updated .env \u2192 UMBRACO_BASE_URL=${baseUrl}`));Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."args": ["--env-file=.env", "./dist/index.js"]Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.WORKER_URL=$(grep -o 'https://[a-z0-9-]*\.trycloudflare\.com' "$WORKER_LOG" 2>/dev/null | head -1)Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.- Each lookup failure warns with its own reason before the throw, so a broken `.env` isFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.4. Add these to your `.env` file:Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.const envExamplePath = path9.join(projectDir, ".env.example");Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.const envPath = path9.join(projectDir, ".env");Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// Also let the SDK reload .env and re-apply dry-run/output mode on the next load.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.UMBRACO_URL=$(grep -o 'https://[a-z0-9-]*\.trycloudflare\.com' "$UMBRACO_LOG" 2>/dev/null | head -1)Fix: Replace encoded or assembled strings with plain literals and remove undeclared network calls.Create a `.env` file:Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Call a tool directly (requires auth via .env)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.- `.mcp.json` uses `node --env-file=.env ./dist/index.js` so credentials stay in `.env` (gitignored)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.* Loads .env quietly.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.**Never pass secrets as CLI arguments.** Use a `.env` file or the MCP config `env` block.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# npx wrangler secret put UMBRACO_BASE_URLFix: Pin versions and sources; vendor anything fetched at install time.# 1. Create KV namespace: npx wrangler kv namespace create OAUTH_KVFix: Pin versions and sources; vendor anything fetched at install time."test:e2e": "npx playwright test --config tests/hosted-e2e/playwright.config.ts",Fix: Pin versions and sources; vendor anything fetched at install time.* npx wrangler deploy # Production deploymentFix: Pin versions and sources; vendor anything fetched at install time.console.log(pc4.dim(` ${step++}. (in a separate terminal) npx @umbraco-cms/create-umbraco-mcp-server discover`));Fix: Pin versions and sources; vendor anything fetched at install time.* npx wrangler dev # Local developmentFix: Pin versions and sources; vendor anything fetched at install time.echo " npx @umbraco-cms/create-umbraco-mcp-server init"Fix: Pin versions and sources; vendor anything fetched at install time."deploy:worker": "npx wrangler deploy"Fix: Pin versions and sources; vendor anything fetched at install time.# npx wrangler secret put LOGIN_SESSION_HASH_KEY # optional: overrides theFix: Pin versions and sources; vendor anything fetched at install time.# npx wrangler secret put TENANT_HASH_KEY # optional: keys the hashedFix: Pin versions and sources; vendor anything fetched at install time.# npx wrangler secret put UMBRACO_OAUTH_CLIENT_IDFix: Pin versions and sources; vendor anything fetched at install time.kill $UMBRACO_PID $WORKER_PID 2>/dev/nullFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."\nRun 'npx @umbraco-cms/create-umbraco-mcp-server <name>' to create a new project first."Fix: Pin versions and sources; vendor anything fetched at install time."dev:worker": "npx wrangler dev",Fix: Pin versions and sources; vendor anything fetched at install time.console.log(pc4.dim(" npx @umbraco-cms/create-umbraco-mcp-server init"));Fix: Pin versions and sources; vendor anything fetched at install time."dev:worker:https": "npx wrangler dev --local-protocol https",Fix: Pin versions and sources; vendor anything fetched at install time.See the [SDK docs](../packages/mcp-server-sdk/README.md) and the published [Tool Types Codegen guide](https://docs.umbraco.com/) for full usage.Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.**Always use npm scripts** (`npm run compile`, `npm test`, `npm run build`) — never run `node`, `npx tsc`, or `jest` directly.Fix: Pin versions and sources; vendor anything fetched at install time.Run locally: `npx wrangler dev --port 8787`Fix: Pin versions and sources; vendor anything fetched at install time."Bash(npx tsc*)",Fix: Pin versions and sources; vendor anything fetched at install time.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/create-umbraco-mcp-server@1.0.0 as of 14 h ago. This is the package itself, not its dependencies.
What would make this Verified
10 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim umbraco-cms: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Destructive file system command detected≈ +4 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
- Tunneling service URL≈ +4 on the totalReplace encoded or assembled strings with plain literals and remove undeclared network calls.
- Credential pass-through configuration≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.