memi— mcp server

Design-system memory for coding agents — Figma tokens, shadcn/ui codegen, Tailwind audits.

by sarveshsea·MCP Server·github.com/sarveshsea/memi
15stars4forksReview on GitHub →

Is memi safe to install?

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

Score
83/100
●●●●●●●●○○
↑ +0 since first scan (83 → 83)Re-scan~30s
Latest scan
ScannedJun 25, 2026 · 32d ago
Scans run1 over 90 days
Detectors55 checks · 5 categories
Findings4 warnings · 0 high
EngineSaferSkills 2b638c6
View methodology →
SaferSkills installs
This week0
This month0
All time0
CategoryWeightCategory scoreContribution
Securityprompt, exec, net, exfil, eval
35%
52
18.2 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 · 4 flagged

Securityscore 52 · 4 findings
MEDIUMInstruction telling the agent not to ask for approvalSS-SKILL-INJECT-DONT-ASK-01 · Prompt injection · docs/GITHUB_ACHIEVEMENTS.md
MEDIUM — it fires on intent; the real damage depends on the host agent's own approval-gating.
Why it matters

The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.

The exact value spotted
excerptdocs/GITHUB_ACHIEVEMENTS.md· markdown
7- Use external repositories only for useful submissions, fixes, docs, or directory listings.
8- Use the sandbox repository only for harmless GitHub workflow achievement tests.
9- Do not ask for fake stars or use alternate accounts to inflate stars.
10- Do not submit low-effort PRs to farm Pull Shark.
11- Keep every accepted PR linked to a real Memoire distribution or ecosystem improvement.
Occurrences
1 occurrence · at L9
How to fix
Remove the approval-skipping instruction, or scope it narrowly to a specific safe, reversible action.
  1. Delete blanket "don't ask / no need to confirm" directives from the skill.
  2. If the skill is a genuine autonomous job, restrict the opt-out to a named non-destructive action rather than all actions.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-DONT-ASK-01sha25668b030f55bcd484a…rubric 365aacaView on GitHub
MEDIUMInstruction telling the agent not to ask for approvalSS-SKILL-INJECT-DONT-ASK-01 · Prompt injection · docs/STARSTRUCK.md
MEDIUM — it fires on intent; the real damage depends on the host agent's own approval-gating.
Why it matters

The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.

The exact value spotted
excerptdocs/STARSTRUCK.md· markdown
25```
26 
27Do not ask for fake stars, star swaps, or bot engagement. The ask must sit after a demo, ins
… (45 chars elided on L27)
28 
29## First Move: Publish The MCP Patch
Occurrences
1 occurrence · at L27
How to fix
Remove the approval-skipping instruction, or scope it narrowly to a specific safe, reversible action.
  1. Delete blanket "don't ask / no need to confirm" directives from the skill.
  2. If the skill is a genuine autonomous job, restrict the opt-out to a named non-destructive action rather than all actions.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-DONT-ASK-01sha25668b030f55bcd484a…rubric 365aacaView on GitHub
MEDIUMInstruction telling the agent not to ask for approvalSS-SKILL-INJECT-DONT-ASK-01 · Prompt injection · notes/accessibility-audit/accessibility-audit.md
MEDIUM — it fires on intent; the real damage depends on the host agent's own approval-gating.
Why it matters

The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.

The exact value spotted
excerptnotes/accessibility-audit/accessibility-audit.md· markdown
350 
351**Redundant entry (WCAG 3.3.7 — new in 2.2):**
352- Don't ask users to re-enter information they've already provided in the same session
353- Auto-populate from previous steps (shipping → billing address)
354- Exception: security re-authentication, data confirmation
Occurrences
1 occurrence · at L352
How to fix
Remove the approval-skipping instruction, or scope it narrowly to a specific safe, reversible action.
  1. Delete blanket "don't ask / no need to confirm" directives from the skill.
  2. If the skill is a genuine autonomous job, restrict the opt-out to a named non-destructive action rather than all actions.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-DONT-ASK-01sha25615dae9807bd892c6…rubric 365aacaView on GitHub
MEDIUMInstruction telling the agent not to ask for approvalSS-SKILL-INJECT-DONT-ASK-01 · Prompt injection · skills/MOTION_VIDEO_DESIGN.md
MEDIUM — it fires on intent; the real damage depends on the host agent's own approval-gating.
Why it matters

The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.

The exact value spotted
excerptskills/MOTION_VIDEO_DESIGN.md· markdown
22## Freedom Level: Maximum
23 
24You operate as a motion design intelligence engine. You don't ask — you analyze the design,
… (108 chars elided on L24)
25 
26**Key Principle:** Motion is not decoration — it is communication. Every animation serves a
… (61 chars elided on L26)
Occurrences
1 occurrence · at L24
How to fix
Remove the approval-skipping instruction, or scope it narrowly to a specific safe, reversible action.
  1. Delete blanket "don't ask / no need to confirm" directives from the skill.
  2. If the skill is a genuine autonomous job, restrict the opt-out to a named non-destructive action rather than all actions.
Framework references
OWASPLLM01ATLASAML.T0051
Trace & refs
ruleSS-SKILL-INJECT-DONT-ASK-01sha256ce5204b52388d24f…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