awwwards-mcp@1.19.0
VERIFIED· 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: 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
- 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-15 and scored it 85/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 · 9 s · 2 scenarios · 0 deviationsStatic findings
/* 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.// Direct child kill only (no shell): Node maps this to TerminateProcessFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.// 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.…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.…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.…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.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.19.0 as of 25 min ago. This is the package itself, not its dependencies.