Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.nyuchi/mzizi-mcp

NPM · @NYUCHI/MZIZI-MCP · 2 COMPONENTS · SCANNED AUG 3

Read-only MCP over the Mzizi design system registry — nodes, components, ownership.

+33 this week 55 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security88
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (107 of 111), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (107 of 111), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 1 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability31
  • AI-judged instruction clarity (poor).Fail
  • Tool/resource definitions use about 129 tokens (~129/item across 1 items; 1 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @nyuchi/mzizi-mcp

# add to Claude Code
claude mcp add nyuchi-mzizi-mcp -- npx -y @nyuchi/mzizi-mcp
# add to Codex CLI
codex mcp add nyuchi-mzizi-mcp -- npx -y @nyuchi/mzizi-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nyuchi-mzizi-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@nyuchi/mzizi-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add nyuchi-mzizi-mcp --command npx --arg -y --arg @nyuchi/mzizi-mcp
# ~/.hermes/config.yaml
mcp_servers:
  nyuchi-mzizi-mcp:
    command: "npx"
    args: ["-y", "@nyuchi/mzizi-mcp"]
// mcp.json
{
  "mcpServers": {
    "nyuchi-mzizi-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@nyuchi/mzizi-mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Aug 26 +52
    • Provenance: unverified → fail security
    • Known CVEs: unverified → partial security
    • Install scripts: unverified → pass security
    • Malware scan: unverified → pass security
    • Dependency health: partial → unverified functional
    • License: unverified → pass functional
    • Maintenance: unverified → pass functional
    • Schema quality: unverified → poor functional
    • Stability: unverified → 0.20 functional
    • Tool coverage: unverified → 100 functional
    • MCP protocol: unverified → pass functional
    • Licence: Apache-2.0 functional
  • 1 Aug 26 +2
    • Provenance: unverified → fail security
    • Known CVEs: unverified → partial security
    • Install scripts: unverified → pass security
    • Dependency health: unverified → partial functional
    • License: unverified → pass functional
    • Maintenance: unverified → pass functional
    • Tool coverage: unverified → 100 functional
    • Licence: Apache-2.0 functional
    • Package version: 0.5.0-beta.8 → 0.6.0 functional
    • Package version: 0.5.0-beta.5 → 0.5.0 functional
  • 31 Jul 26 −22
    • Package version: 0.5.0-beta.5 → 0.5.0-beta.7 functional
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 22

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/@nyuchi/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 107 packages

107 packages in the resolved dependency tree · 104 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 1 exposed · ~27 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
mzizi_registry_unavailable ~27

The mcp_tool_registry could not be read: TypeError: fetch failed

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.