memoire (memi-design/memi) is an MCP server listed on the M8ven Trust Index. M8ven has not graded it: there is no public source to read and no endpoint we can reach, so there is nothing for us to inspect. No publisher has claimed this listing.

C
Caution
74/100
18 days ago

memoire

Design system MCP server. 20 tools: extract design tokens from any URL, pull from Figma or Penpot, generate React + shadcn/ui components from specs, run WCAG audits, sync tokens bidirectionally.

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

memi-design

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
⚠️
Known vulnerabilities in dependencies: 1 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 5 credentials: ANTHROPIC_API_KEY, FIGMA_FILE_KEY, FIGMA_TOKEN, GITHUB_TOKEN, PENPOT_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies1 high1 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

highws@8.18.0GHSA-96hv-2xvq-fx4p

ws: Memory exhaustion DoS from tiny fragments and data chunks

ws: Uninitialized memory disclosure

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretANTHROPIC_API_KEY
configEXPECTED_COMMUNITY_NOTES
configEXPECTED_INSTALL_COMMAND
configEXPECTED_README_PHRASE
configEXPECTED_SITE_URL
configEXPECTED_SOURCE_COMMIT
configEXPECTED_SOURCE_REF
configEXPECTED_SOURCE_REPOSITORY
configEXPECTED_SOURCE_WORKFLOW
configEXPECTED_STUDIO_VERSION
configEXPECTED_VERSION
🔐 secretFIGMA_FILE_KEY
🔐 secretFIGMA_TOKEN
configGITHUB_BASE_REF
configGITHUB_REF
configGITHUB_STEP_SUMMARY
🔐 secretGITHUB_TOKEN
configMAX_TARBALL_BYTES
configMEMI_AI_MAX_OUTPUT
configMEMOIRE_BENCH_CLI
configMEMOIRE_BENCH_NO_FAIL
configMEMOIRE_BENCH_RUNS
configMEMOIRE_BENCH_WARMUPS
configMEMOIRE_COMMUNITY_NOTES_BASE_URL
configMEMOIRE_COMMUNITY_NOTES_ROOT
configMEMOIRE_DISABLE_LAYOUT_AI
configMEMOIRE_EXPECTED_NPM_USER
configMEMOIRE_LOG_LEVEL
configMEMOIRE_MCP_SMOKE_TIMEOUT_MS
configMEMOIRE_NOTES_BASE_URL
configMEMOIRE_PACK_MAX_BYTES
configMEMOIRE_PACK_MAX_FILES
configMEMOIRE_PACK_MAX_UNPACKED_BYTES
configMEMOIRE_PACK_MAX_UTILIZATION
configMEMOIRE_PUBLISH_READY_SKIP_AUTH
configMEMOIRE_PUBLISH_READY_SKIP_GIT
configMEMOIRE_SILENCE_DEPRECATIONS
configMEMOIRE_STUDIO_TARGET
configMIN_COMMUNITY_CATALOG_DATE
configNPM_CONFIG_PREFIX
configNPM_CONFIG_REGISTRY
configNPM_SIGNATURE_AUDIT_VERIFIED
configNPM_VERIFY_ATTEMPTS
configNPM_VERIFY_DELAY_MS
configPACKAGE_NAME
configPENPOT_FILE_ID
🔐 secretPENPOT_TOKEN
configRELEASE_RECORD_OUTPUT
configRELEASE_WORKFLOW_RUN_ATTEMPT
configRELEASE_WORKFLOW_RUN_ID
configSBOM_PATH
configSHELL
configSKIP_AUDIT_GATE
configSKIP_INSTALL_SMOKE
configSKIP_PACK_GATE
configSKIP_SITE_SMOKE
configSOURCE_DATE_EPOCH
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

50/50 tools missing one or more hints — pull_design_system (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); pull_design_system_rest (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_specs (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +47 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

42/50 tool handlers declare input schemas (84%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 12/50 tool handlers wrap calls in try/catch (24%)

Wrap each tool handler body in try/catch and return a structured error response.

Tool test coverage

Only 1/50 tools referenced in tests (2%)

Write tests that reference each tool by name so every tool has at least one test.

Secrets not logged

3 secret values sent to console.log

Redact or omit secret values from log output.

Production dependencies are patched

0 critical, 1 high severity in production deps — ws@8.18.0 (high), ws@8.18.0 (low)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dependency freshness

1/19 production deps stale: ssf@2022-06-26 (4.1y)

Domain consistency

npm scope @memoire-examples doesn't match GitHub owner sarveshsea

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 8 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/sarveshsea-m-moire-gqejgd?variant=verified)](https://m8ven.ai/mcp/sarveshsea-m-moire-gqejgd)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: fbe3005053040e921460c19d2a87169e4eac7462
code hash: 1917f52e1183089cd9b58fba632167eafbb4e92a15b18624715aee47cb8f550a
verified: 8/7/2026, 4:01:30 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client