awwwards-mcp@1.18.0
CAUTION· not startedPublisher claims: "Awwwards design inspiration, screenshots, motion and scene evidence for AI agents." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
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: 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
- no credential variables read in the code
- Where it talks to
- awwwards.com (its own)Also esm.sh, jsdelivr.net, local.invalid, unpkg.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 under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable and talks to awwwards.com, its own; 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; not started: dependency install failed; the server itself was not observed) on 2026-11-14 and scored it 78/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: Auto-update or dynamic fetch configuration; Auto-update or dynamic fetch configuration; Auto-update or dynamic fetch configuration. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 9 s · 2 scenarios · 0 deviationsStatic findings
export function buildUpdateNotice(current, latest, autoUpdateEnabled) {Fix: Pin versions and sources; vendor anything fetched at install time.…plus a static perspective camera applied from its exact captured matrix (matrix auto-update off); captured controls are never recreated, and unsupported geometry, materials, cameras and controls are listed as unresolved instead of guessed.…Fix: Pin versions and sources; vendor anything fetched at install time.: `awwwards-mcp: update with \`npm install -g awwwards-mcp@latest\` (or clear your npx cache), or set AWWWARDS_AUTO_UPDATE=1 to self-update on startup.`,Fix: Pin versions and sources; vendor anything fetched at install time.// Skip the daily gate when auto-update is on but no latest is known yet?Fix: Pin versions and sources; vendor anything fetched at install time.autoUpdateEnabledFix: Pin versions and sources; vendor anything fetched at install time./* one broken rule must not kill the scan for this input */Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.…andatory, are recorded with a timestamp in scene-captures/<captureId>/provenance.json, and are not verified by the server - do not download assets you may not use. It only fetches observed inventory URLs that carry no query string, fragmen…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.…hts.evidence because downloading is a licensing decision, recorded in provenance.json; caps are 16 MiB/file, 64 MiB/run, 5 redirects, 1 req/s, 15s body and 120s overall, and only observed URLs without query, fragment or credentials are fet…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.// npm/npx are .cmd shims on Windows. Spawning npm.cmd with shell:true emitsFix: Pin versions and sources; vendor anything fetched at install time.// tool call forever — kill the child and reject so the caller gets theFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.: `awwwards-mcp: update with \`npm install -g awwwards-mcp@latest\` (or clear your npx cache), or set AWWWARDS_AUTO_UPDATE=1 to self-update on startup.`,Fix: Pin versions and sources; vendor anything fetched at install time.…imeline stub from a scroll census, optional PoseGrid), manifest (motion.manifest.json scaffold from page bands + scroll census, optional section overrides), or scene_stub (offline Vite + Three.js scaffold from a scene-evidence-v1 pack: mod…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.…onManifest(ctx) { ctx.tool("build_motion_manifest", "Build a motion.manifest.json scaffold from measured evidence: an analyze_page_structure result (bands) + an analyze_scroll_map census, with optional section overrides. Sections are mappe…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.// Direct child kill only (no shell): Node maps this to TerminateProcessFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.: `awwwards-mcp: update with \`npm install -g awwwards-mcp@latest\` (or clear your npx cache), or set AWWWARDS_AUTO_UPDATE=1 to self-update on startup.`,Fix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.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 awwwards-mcp@1.18.0 as of 3 h ago. This is the package itself, not its dependencies.
What would make this Verified
2 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim insane0777: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Auto-update or dynamic fetch configuration≈ +4 on the totalPin versions and sources; vendor anything fetched at install time.
- Process kill command≈ +2 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.
- npx invocation of non-well-known package≈ +2 on the totalPin versions and sources; vendor anything fetched at install time.
- Unpinned dependencies≈ +1 on the totalPin exact versions (and ideally hashes) in package.json, requirements or the install script so the bundle cannot change under you.