ubugeeei-prod/vize (ubugeeei-prod/vize) is an MCP server listed on the M8ven Trust Index. It scores 96 out of 100, grade A. It declares 26 tools. No publisher has claimed this listing.

A
Trusted
96/100
1 month ago

ubugeeei-prod/vize

MCP server for building Vue.js design systems - component analysis, documentation, variant generation, and design tokens

ubugeeei-prod/vize· npm: @vizejs/musea-mcp-server· listed on npm

Trusted. Deep verification, no outstanding findings, and an established reputation. 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

ubugeeei-prod

Source: npm

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
🚨
Secret credentials may flow to a network call
2 flows detected: GITHUB_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 4 credentials: BENCHMARK_COMMENT_KEY, GH_TOKEN, GITHUB_TOKEN, TEST_REPORT_COMMENT_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// 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.
configAI_FIX_AGENT_COMMAND
🔐 secretBENCHMARK_COMMENT_KEY
🔐 secretGH_TOKEN
configGITHUB_API_URL
configGITHUB_EVENT_NAME
configGITHUB_EVENT_PATH
configGITHUB_OUTPUT
configGITHUB_REF_NAME
configGITHUB_REPOSITORY
configGITHUB_RUN_ID
configGITHUB_SERVER_URL
configGITHUB_SHA
configGITHUB_STEP_SUMMARY
🔐 secretGITHUB_TOKEN
configHELIX_RUNTIME
configMUSEA_PROJECT_ROOT
configMUSEA_TOKENS_PATH
configNEEDS_JSON
configNPM_BIN
configPR_NUMBER
🔐 secretTEST_REPORT_COMMENT_KEY
configTEST_REPORT_HEAD_SHA
configTEST_REPORT_RUN_ATTEMPT
configTEST_REPORT_RUN_ID
configTEST_REPORT_RUN_URL
configTEST_REPORT_WORKFLOW_NAME
configVIZE_BENCH_RUNNER
configVIZE_BIN
configVIZE_CHECK_GATE_TSGO
configVIZE_CHECK_GATE_VUE_TSC
configVIZE_DARWIN_LIBICONV_LIB
configVIZE_LSP_BIN
configVIZE_SERVER_PATH
configVIZE_SKIP_ROOT_BUILD_TASK
configVIZE_TEST_NVIM_PATH
configVIZE_TEST_VIM_LSP_PATH
configVIZE_TEST_VIM_PATH
configXDG_CONFIG_HOME
// 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

26/26 tools missing one or more hints — analyze_component (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_palette (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_components (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +23 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 test coverage

Only 0/26 tools referenced in tests (0%)

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

Shell command execution

6 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Secrets not written to files

1 secret value written to files

Avoid persisting secrets to disk. Keep them in memory or your secret manager.

Secrets not logged

4 secret values sent to console.log

Redact or omit secret values from log output.

Domain consistency

npm scope @vize doesn't match GitHub owner ubugeeei

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 7 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 Score](https://m8ven.ai/badge/mcp/ubugeeei-prod/vize)](https://m8ven.ai/mcp/ubugeeei-prod/vize)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 791a5a002a9e93ac1fb01b193dc06a6869272f3e
code hash: 026aec77ea6de0e4a6822d3894796975de9ab728115249f98b5d278977d6244f
verified: 8/6/2026, 2:57:23 PM
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