Mizuki
NPM · MIZUKI-MCP · SCANNED SEP 20
Fixed-price maintenance for public GitHub issues, paid in USDC on Solana.
Available components
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 Security98
- 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
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- 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 17 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 567 tokens (~43/item across 13 items; 13 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Mizuki MCP server?
Mizuki runs locally as an npm package, launched with npx -y mizuki-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 · mizuki-mcp
claude mcp add org-opencovenant-mizuki -- npx -y mizuki-mcp
{
"mcpServers": {
"org-opencovenant-mizuki": {
"command": "npx",
"args": [
"-y",
"mizuki-mcp"
]
}
}
} {
"servers": {
"org-opencovenant-mizuki": {
"command": "npx",
"args": [
"-y",
"mizuki-mcp"
]
}
}
} codex mcp add org-opencovenant-mizuki -- npx -y mizuki-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"org-opencovenant-mizuki": {
"type": "local",
"command": [
"npx",
"-y",
"mizuki-mcp"
],
"enabled": true
}
}
} openclaw mcp add org-opencovenant-mizuki --command npx --arg -y --arg mizuki-mcp
mcp_servers:
org-opencovenant-mizuki:
command: "npx"
args: ["-y", "mizuki-mcp"] {
"McpServers": {
"org-opencovenant-mizuki": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mizuki-mcp"
]
}
}
} assistant mcp add org-opencovenant-mizuki -t stdio -c npx -a -y mizuki-mcp
{
"mcpServers": {
"org-opencovenant-mizuki": {
"command": "npx",
"args": [
"-y",
"mizuki-mcp"
]
}
}
} 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 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +4
- Stability: unverified → 0.23 ▲ functional
- 3 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Sept 26 52
First indexed and scored.
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 20 Sept 2026 · Analysed npm/mizuki-mcp@0.1.2
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 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| 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 →
mizuki_bounties ~26
List public maintenance bounties created after eligible jobs receive a full refund.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mizuki_bounty ~41
Inspect one maintenance bounty, its claim requirements, separate AI review, maintainer approval, and funded SOL escrow status.
| Name | Type | Req | Description |
|---|---|---|---|
| bounty_id | string | yes | – |
No output schema declared.
No examples provided.
mizuki_capabilities ~25
Inspect proposed capability changes and the evidence required before a change can reach production.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mizuki_capability_handoff ~41
Read a hashed record of the failures, benchmark, and approvals required before a capability change can reach production.
| Name | Type | Req | Description |
|---|---|---|---|
| capability_id | string | yes | – |
No output schema declared.
No examples provided.
mizuki_payment_status ~68
Safely check whether an exact quote and idempotency key already reserved a job. This read never requests a wallet signature or submits payment. Requires a jobs:read MIZUKI_API_TOKEN.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | – |
| quote_id | string | yes | – |
No output schema declared.
No examples provided.
mizuki_preflight ~53
Run repository, authorization, scope, and maintainer readiness checks for one issue without creating a quote or payment. Requires a repositories:read MIZUKI_API_TOKEN.
| Name | Type | Req | Description |
|---|---|---|---|
| github_issue_url | string | yes | – |
No output schema declared.
No examples provided.
mizuki_quote ~58
Get a fixed-price quote and x402 payment requirements for a public GitHub issue. With MIZUKI_API_TOKEN, the repository must already be connected and the quote is linked for payment recovery.
| Name | Type | Req | Description |
|---|---|---|---|
| github_issue_url | string | yes | – |
No output schema declared.
No examples provided.
mizuki_repositories ~35
List repositories linked to the authenticated maintainer and their current readiness. Requires a repositories:read MIZUKI_API_TOKEN.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mizuki_repository_issues ~51
List bounded maintenance candidates for a linked repository after authenticated maintainer checks. Requires a repositories:read MIZUKI_API_TOKEN.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | – |
| repo | string | yes | – |
No output schema declared.
No examples provided.
mizuki_repository_readiness ~50
Read current readiness for one repository already linked to the authenticated maintainer. Never bypasses maintainer or GitHub App checks.
| Name | Type | Req | Description |
|---|---|---|---|
| owner | string | yes | – |
| repo | string | yes | – |
No output schema declared.
No examples provided.
mizuki_status ~33
Read delivery, PR, validation, or refund status for a Mizuki job.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | – |
No output schema declared.
No examples provided.
mizuki_submit ~50
Submit a quoted job with a wallet-created x402 PAYMENT-SIGNATURE.
| Name | Type | Req | Description |
|---|---|---|---|
| idempotency_key | string | yes | – |
| payment_signature | string | yes | – |
| quote_id | string | yes | – |
No output schema declared.
No examples provided.
mizuki_treasury ~36
Inspect the refund reserve wallet status and planning estimates derived from service records. Planning estimates do not prove custody or grant spending authority.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the Mizuki MCP server?
Mizuki is an MCP server listed in the public MCP registry as org.opencovenant/mizuki. Fixed-price maintenance for public GitHub issues, paid in USDC on Solana. This page covers its npm package (mizuki-mcp).
Is the Mizuki MCP server safe to use?
Mizuki scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 Mizuki MCP server expose?
Mizuki exposes 13 tools: mizuki_quote, mizuki_submit, mizuki_status, mizuki_repositories, mizuki_repository_readiness, and 8 more. Their descriptions and schemas cost roughly 567 tokens of context every time the server is loaded.
Is the Mizuki MCP server still maintained?
Mizuki is still listed as active in the MCP registry. We last reached this channel on 20 September 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 Mizuki MCP server under?
Mizuki 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.