# io.github.mzizi-dev/mzizi-mcp (npm · @nyuchi/mzizi-mcp)

Mzizi design system MCP: search and execute over components, tokens, crates, skills and docs. Free.

- Trust score: 67/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `mcp.mzizi.dev`: 61/100, [markdown](https://verifymcp.io/servers/mzizi-dev-mzizi-mcp/mcp.md), [page](https://verifymcp.io/servers/mzizi-dev-mzizi-mcp/mcp)
- npm · `@nyuchi/mzizi-mcp`: 67/100 (this document), [markdown](https://verifymcp.io/servers/mzizi-dev-mzizi-mcp/nyuchi-mzizi-mcp.md), [page](https://verifymcp.io/servers/mzizi-dev-mzizi-mcp/nyuchi-mzizi-mcp)

## Channel facts

- Registry: `npm`
- Package: `@nyuchi/mzizi-mcp`
- Version: `0.26.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 0 of 7 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 1 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 5087 tokens (~124/item across 41 items; 3 tools + 38 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 8/100
  - Stability check failed: the tool surface changed between 0.13.0 and 0.26.0: 12 tool removals, 0 breaking changes, 2 additions.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 87% of tool parameters carry a description.
  - Structured output schemas are declared (33% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the io.github.mzizi-dev/mzizi-mcp server?

io.github.mzizi-dev/mzizi-mcp runs locally as an npm package, launched with npx -y @nyuchi/mzizi-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add mzizi-dev-mzizi-mcp -- npx -y @nyuchi/mzizi-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "mzizi-dev-mzizi-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@nyuchi/mzizi-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mzizi-dev-mzizi-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@nyuchi/mzizi-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add mzizi-dev-mzizi-mcp -- npx -y @nyuchi/mzizi-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mzizi-dev-mzizi-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@nyuchi/mzizi-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mzizi-dev-mzizi-mcp --command npx --arg -y --arg @nyuchi/mzizi-mcp
```

### Hermes

```yaml
mcp_servers:
  mzizi-dev-mzizi-mcp:
    command: "npx"
    args: ["-y", "@nyuchi/mzizi-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "mzizi-dev-mzizi-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@nyuchi/mzizi-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add mzizi-dev-mzizi-mcp -t stdio -c npx -a -y @nyuchi/mzizi-mcp
```

### Other

```json
{
  "mcpServers": {
    "mzizi-dev-mzizi-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@nyuchi/mzizi-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 67, +1)

- [security regression] Stability: fail → unverified
- [security regression] Tool safety: pass → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional] Package version: 0.25.0 → 0.26.0

### 2026-11-19 (score 66, −1)

- [security regression] Tool safety: pass → unverified
- [security regression] Stability: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional] Package version: 0.24.0 → 0.25.0

### 2026-11-18 (score 67, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-17 (score 52, −28)

- [security regression] Malware scan: pass → unverified
- [security regression] Stability: pass → fail
- [functional regression] Tool coverage: 95% → 87%
- [functional improvement] Schema quality: 136 → 122
- [functional improvement] Tool coverage: 23% → 33%
- [functional] Schema quality: excellent → good
- [functional] Destructive annotations: pass → 100
- [functional] Package version: 0.21.0 → 0.24.0
- [functional] Package version: 0.21.0 → 0.23.0
- [functional] Package version: 0.21.0 → 0.22.0

### 2026-11-15 (score 80, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-14 (score 65, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.20.0 → 0.21.0

### 2026-11-13 (score 80, +26)

- [security regression] Stability: 0.97 → unverified
- [security regression] Tool safety: pass → unverified
- [security improvement] Malware scan: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [security] Stability: 0.97 → pass
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional improvement] Dependency health: unverified → 1.00
- [functional] Package version: 0.19.0 → 0.20.0

### 2026-11-12 (score 54, −26)

- [security regression] Known CVEs: pass → unverified
- [security regression] Malware scan: pass → unverified
- [functional regression] Dependency health: 1.00 → unverified
- [functional] Package version: 0.17.0 → 0.19.0
- [functional] Package version: 0.17.0 → 0.18.0

## MCP tools (3)

### `mzizi_search` (~297 tokens)

Search Mzizi

Find anything this server can answer, and the operations that act on it. Searches components, conventions, engineering constraints, AI instruction sets, releases, the Rust crates, the agent skills, the toolchain (the CLI, how to install anything, this server) and, when docs.mzizi.dev answers, the documentation. Returns `results` (hits, paged), `docs` (documentation matches), and `operations`: each with its `arguments` (JSON Schema), the `permission` it needs (free, or sign-in) and `mayRun`, whether you may run it now. Run one with mzizi_execute {operation, arguments}. `allOperations` lists every operation. A component hit with `rustCrate` has a Mzizi Roots (Rust) implementation, which is the lead; at an equal score it ranks first. Paged: up to 50 hits per call and at most 25000 characters; results.meta.has_more and results.meta.next_offset say how to get the rest.

Input parameters:

- `limit` (integer): Hits per call (default 50, at most 200).
- `offset` (integer): Hits to skip, for paging. Use results.meta.next_offset from the previous call.
- `query` (string, required): Free-text search, e.g. 'button', 'install', 'cli', 'contrast', 'crates' or an operation name. Every word must match.

Output parameters:

- `allOperations` (array)
- `operations` (array)
- `query` (string)
- `results` (object)

### `mzizi_execute` (~192 tokens)

Run a Mzizi operation

Run one operation by name with its arguments. mzizi_search lists operations with their arguments, the permission each needs and whether you may run it. Operations: get_component, list_components, get_tokens, get_architecture, get_doctrine, get_skills, check_accessibility, list_crates, describe, docs_search_mzizi, docs_query_docs_filesystem_mzizi, docs_submit_feedback. Reads need no account; the fundi operation needs sign-in, and a refusal names the permission it needs and how to sign in. The result is the operation's own answer. The earlier tool names (mzizi_get_component and the rest) are accepted as operation names.

Input parameters:

- `arguments` (object): The operation's arguments, as its `arguments` schema in mzizi_search states them. Omit for none.
- `operation` (string, required): The operation's name, e.g. 'get_component'.

### `mzizi_feedback` (~399 tokens)

Report an issue or give feedback

Your issue desk (was mzizi_report_issue): report a problem with a component or the registry. It goes to your own desk, which reproduces it via fundi, drafts an issue body with what the reproduction returned and logs it to fundi; fundi files the GitHub issue and tracks it, so action 'get' shows where yours got to. 'list' shows your reports, 'retry' re-attempts one that drafted but could not be logged. Needs sign-in: the desk belongs to your Mzizi console user; without it, the answer carries the report as a pre-filled GitHub issue for mzizi-dev/mzizi-registry, so it is never lost, and over HTTP the server answers with an OAuth challenge so your client can offer sign-in. With target 'docs', it instead reports a problem with a documentation page on docs.mzizi.dev (give `path` and `message`); that needs no account.

Input parameters:

- `action` (string): What to do. Defaults to filing a new report.
- `component` (string): Component the report concerns.
- `kind` (string): Report kind. Required for action 'file'.
- `limit` (integer)
- `message` (string): What happened. Required for action 'file'.
- `path` (string): For target 'docs': the page's URL path, without .mdx, e.g. /toolchain/cli.
- `reportId` (string): Report id. Required for actions 'get' and 'retry'.
- `severity` (string)
- `skill` (string): fundi skill to run for the reproduction. fundi never infers a skill from text, so omit this to let the report kind choose one.
- `target` (string): Where it goes: 'issue-desk' (default; sign-in) or 'docs' (a docs.mzizi.dev page; free).

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/mzizi-dev-mzizi-mcp/nyuchi-mzizi-mcp#diagnostics

## Score history

- 2026-11-21: 67
- 2026-11-20: 67
- 2026-11-19: 66
- 2026-11-18: 67
- 2026-11-17: 52
- 2026-11-16: 80
- 2026-11-15: 80
- 2026-11-14: 65
- 2026-11-13: 80
- 2026-11-12: 54
- 2026-11-11: 80
- 2026-11-10: 79
- 2026-11-09: 79
- 2026-11-08: 78
- 2026-11-07: 78
- 2026-11-06: 77
- 2026-11-05: 77
- 2026-11-04: 69
- 2026-11-03: 80
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 80
- 2026-10-28: 79
- 2026-10-27: 79
- 2026-10-26: 78
- 2026-10-25: 78
- 2026-10-24: 77
- 2026-10-23: 77

## Common questions

### What is the io.github.mzizi-dev/mzizi-mcp server?

io.github.mzizi-dev/mzizi-mcp is listed in the public MCP registry as io.github.mzizi-dev/mzizi-mcp. Mzizi design system MCP: search and execute over components, tokens, crates, skills and docs. Free. This page covers its npm package (@nyuchi/mzizi-mcp).

### Is the io.github.mzizi-dev/mzizi-mcp server safe to use?

io.github.mzizi-dev/mzizi-mcp scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.mzizi-dev/mzizi-mcp server expose?

io.github.mzizi-dev/mzizi-mcp exposes 3 tools: mzizi_search, mzizi_execute, mzizi_feedback. Their descriptions and schemas cost roughly 888 tokens of context every time the server is loaded.

### Is the io.github.mzizi-dev/mzizi-mcp server still maintained?

io.github.mzizi-dev/mzizi-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.mzizi-dev/mzizi-mcp server under?

io.github.mzizi-dev/mzizi-mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the io.github.mzizi-dev/mzizi-mcp server?

VerifyMCP ran 15 checks on io.github.mzizi-dev/mzizi-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.mzizi-dev/mzizi-mcp: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@nyuchi/mzizi-mcp
- Socket report: https://socket.dev/npm/package/@nyuchi/mzizi-mcp
- Website: https://mzizi.dev/
- Changelog RSS feed: https://verifymcp.io/servers/mzizi-dev-mzizi-mcp/nyuchi-mzizi-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/mzizi-dev-mzizi-mcp/nyuchi-mzizi-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/mzizi-dev-mzizi-mcp/nyuchi-mzizi-mcp.json
- HTML version of this page: https://verifymcp.io/servers/mzizi-dev-mzizi-mcp/nyuchi-mzizi-mcp
