aesthetic-computer— mcp server

MCP server for aesthetic.computer - publish JavaScript, KidLisp art, and clock melodies

by whistlegraph·MCP Server·github.com/whistlegraph/aesthetic-computer
89starsReview on GitHub →

Is aesthetic-computer safe to install?

SaferSkills independently audited aesthetic-computer (MCP Server) and scored it 96/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 1 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

Score
96/100
●●●●●●●●●●
↑ +0 since first scan (96 → 96)Re-scan~30s
Latest scan
ScannedJun 25, 2026 · 30d ago
Scans run1 over 90 days
Detectors55 checks · 5 categories
Findings1 warnings · 0 high
EngineSaferSkills 2b638c6
View methodology →
SaferSkills installs
This week0
This month0
All time0
CategoryWeightCategory scoreContribution
Securityprompt, exec, net, exfil, eval
35%
88
30.8 pts
Supply chainhash, typosquat, maintainer, lockfile
20%
100
20.0 pts
Maintenancestaleness, pinning, CI
15%
100
15.0 pts
TransparencySKILL.md, perms, README
15%
100
15.0 pts
Communityinstalls, verify, response
15%
100
15.0 pts

Findings & checks · 1 flagged

Securityscore 88 · 1 finding
MEDIUM"Never tell the user" non-disclosure imperative in the skillSS-SKILL-INJECT-IMPERATIVE-01 · Prompt injection · ac-shop/SECURITY.md
MEDIUM — it fires on intent; whether the agent honors the non-disclosure imperative depends on the host model.
Why it matters

A bulleted imperative like {match} tells the agent to never reveal, disclose, or mention something to the user. Used adversarially it can instruct the agent to hide its tool calls or lie about what it did — stripping the transparency a user relies on to trust the agent.

The exact value spotted
excerptac-shop/SECURITY.md· markdown
43- The use of commercial scanners is prohibited (e.g., Nessus).
44- Rules for reporting must be followed.
45- Do not disclose any issues publicly before they have been resolved.
46- Shopify reserves the right to modify the rules for this program or deem any submissions in
… (86 chars elided on L46)
47- Contacting Shopify Support over chat, email or phone about your HackerOne report is not al
… (102 chars elided on L47)
Occurrences
1 occurrence · at L45
How to fix
Remove the non-disclosure imperative, or rescope it so it limits output format, not honesty to the user.
  1. Delete any "never reveal / never tell the user" line aimed at the model's own behavior.
  2. Keep legitimate confidentiality rules about external data (e.g. "do not echo API keys"), which are user-protective, not user-deceiving.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-IMPERATIVE-01sha25640f836ae691c1fe8…rubric 365aacaView on GitHub
Supply chainscore 100 · 0 findings
✓—All supply chain checks passedNo findings in this category for the latest scan.pass
Maintenancescore 100 · 0 findings
✓—All maintenance checks passedNo findings in this category for the latest scan.pass
Transparencyscore 100 · 0 findings
✓—All transparency checks passedNo findings in this category for the latest scan.pass
Communityscore 100 · 0 findings
✓—All community checks passedNo findings in this category for the latest scan.pass
Vendor response · right of reply
Are you the maintainer? Submit a response →

Audit the pieces. Scan the whole. Decide.

~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.

Scan a GitHub repoBrowse capabilities