io.github.mzizi-dev/mzizi-mcp
NPM · @NYUCHI/MZIZI-MCP · 2 COMPONENTS
Mzizi design system MCP: search and execute over components, tokens, crates, skills and docs. Free.
Available components
Last scanned (20 hours ago)
Scores higher than 38% of npm servers
Category Developer Tools
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 → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 7 dependencies flagged as unhealthy. View diagnostics → Pass
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 Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management8
- Stability check failed: the tool surface changed between 0.13.0 and 0.26.0: 12 tool removals, 0 breaking changes, 2 additions. See how to fix → Fail
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 87% of tool parameters carry a description.Partial
- Structured output schemas are declared (33% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +1
- Stability: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 0.25.0 → 0.26.0 functional
- 19 Nov 26 −1
- Tool safety: pass → unverified ▼ security
- Stability: fail → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Package version: 0.24.0 → 0.25.0 functional
- 18 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 17 Nov 26 −28
- Malware scan: pass → unverified ▼ security
- Stability: pass → fail ▼ security
- Tool coverage: 95% → 87% ▼ functional
- Schema quality: 136 → 122 ▲ functional
- 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 functional
- 15 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 14 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.20.0 → 0.21.0 functional
- 13 Nov 26 +26
- Stability: 0.97 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Stability: 0.97 → pass security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Dependency health: unverified → 1.00 ▲ functional
- Package version: 0.19.0 → 0.20.0 functional
- 12 Nov 26 −26
- Known CVEs: pass → unverified ▼ security
- Malware scan: pass → unverified ▼ security
- Dependency health: 1.00 → unverified ▼ functional
- Package version: 0.17.0 → 0.19.0 functional
- Package version: 0.17.0 → 0.18.0 functional
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 21 Nov 2026 · Analysed npm/@nyuchi/mzizi-mcp@0.26.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 7 packages
| Packages resolved | 7 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
mzizi_execute Run a Mzizi operation ~192
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.
| Name | Type | Req | Description |
|---|---|---|---|
| arguments | object | – | The operation's arguments, as its `arguments` schema in mzizi_search states them. Omit for none. |
| operation | string | yes | The operation's name, e.g. 'get_component'. |
No output schema declared.
No examples provided.
mzizi_feedback Report an issue or give feedback ~399
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
mzizi_search Search Mzizi ~297
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Free-text search, e.g. 'button', 'install', 'cli', 'contrast', 'crates' or an operation name. Every word must match. |
| Name | Type | Req | Description |
|---|---|---|---|
| allOperations | array | yes | – |
| operations | array | yes | – |
| query | string | yes | – |
| results | object | yes | – |
No examples provided.
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.
npm · @nyuchi/mzizi-mcp
claude mcp add mzizi-dev-mzizi-mcp -- npx -y @nyuchi/mzizi-mcp
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.