MCP.Market

Mizuki MCP server

by opencovenant.org·org.opencovenant/mizuki·v0.1.2·8 stars
No reviews yet

Fixed-price maintenance for public GitHub issues, paid in USDC on Solana.

B77/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B77/100

full report

Adoption
Growing

8 stars0 downloads/wk

Reviews

Write one

Nobody has reviewed Mizuki yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Mizuki tools (13, 2 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • mizuki_bounties

    List public maintenance bounties created after eligible jobs receive a full refund.

  • mizuki_bounty

    Inspect one maintenance bounty, its claim requirements, separate AI review, maintainer approval, and funded SOL escrow status.

  • mizuki_capabilities

    Inspect proposed capability changes and the evidence required before a change can reach production.

  • mizuki_capability_handoff

    Read a hashed record of the failures, benchmark, and approvals required before a capability change can reach production.

  • mizuki_payment_status

    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.

  • mizuki_preflightwrite action

    Run repository, authorization, scope, and maintainer readiness checks for one issue without creating a quote or payment. Requires a repositories:read MIZUKI_API_TOKEN.

  • mizuki_quote

    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.

  • mizuki_repositories

    List repositories linked to the authenticated maintainer and their current readiness. Requires a repositories:read MIZUKI_API_TOKEN.

  • mizuki_repository_issues

    List bounded maintenance candidates for a linked repository after authenticated maintainer checks. Requires a repositories:read MIZUKI_API_TOKEN.

  • mizuki_repository_readiness

    Read current readiness for one repository already linked to the authenticated maintainer. Never bypasses maintainer or GitHub App checks.

  • mizuki_status

    Read delivery, PR, validation, or refund status for a Mizuki job.

  • mizuki_submitwrite action

    Submit a quoted job with a wallet-created x402 PAYMENT-SIGNATURE.

  • mizuki_treasury

    Inspect the refund reserve wallet status and planning estimates derived from service records. Planning estimates do not prove custody or grant spending authority.

Public scan report

scanner v0.1.10 · 2026-10-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan6 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identitynamespace and repository owner differ4/10
Overall 77/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Mizuki compares

Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
77/100
higher than 45% of 1,119 Developer tools servers
Tools
13
the typical Developer tools server has 7
Tools that change things
15%
typical: 5%. Fewer write tools means less an agent can break
GitHub stars
8
more than 82% of 856 Developer tools servers

What its tools let an agent do: 11 read · 2 change

Install Mizuki in Claude Code, Cursor or VS Code

Runs npx -y mizuki-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mizuki -- npx -y mizuki-mcp
Add to Cursor

What the publisher says

From the Mizuki repository's README, as published. We do not edit it. Read it on GitHub

Covenant

Open infrastructure for agent-native computing.

Covenant sits below agent applications and above the host operating system. It owns the state, authority, and accountability concerns that recur across agent frameworks — scoped capabilities, durable memory, runtime isolation, append-only audit, and commit-scoped provenance — so individual frameworks can stop reinventing them.

<!-- METRICS:START --> Status. Local control plane is real and live-tested (50 Rust crates, ~284k lines, 3870 source-discovered Rust tests including 486 live boundary tests). Production-grade sandboxing for hostile agent code and networked multi-peer operation are roadmap; the Solana settlement program is deployed on mainnet (credits, staking, slashing, on-chain receipt anchoring), but its daemon-driven economic lifecycle is not yet production. See BUILT.md for the explicit honesty boundary. <!-- METRICS:END -->

Multi-chain reach. The trust layer also projects onto Base mainnet as signed statements any EVM contract verifies with one ecrecover — ERC-8004 agent registration, a deployed bond-receipt verifier, a registered EAS reputation schema, and an ENS CCIP-Read gateway (*.agents.opencovenant.eth) — while $CVNT stays a single Solana mint that is never bridged or wrapped and every per-call fee and bond is chain-local USDC. On-chain reputation writes and funded USDC bonds are registered but not yet exercised, while live x402 sellers settle chain-local USDC on both Solana and Base mainnet, and on Robinhood Chain mainnet (chain 4663) a USDG x402 payment and an on-chain bounded-spend escrow are proven with real USDG. See docs/multichain-value-capture.md.

  • Web: opencovenant.org
  • Docs: docs.opencovenant.org
  • Paper: DOI: 10.5281/zenodo.20134416
  • Token: $CVNT · 2mNVZ6aEjrGwiUVCfz7XGWpiXuWzgBDoznwE579upump

Quick start

Try it without installing — sandbox.opencovenant.org. Public operator console wired to a live daemon, state resets every 12 hours.

To run it locally, build the daemon and CLI, register the sample agent, and start the daemon:

git clone https://github.com/open-covenant/covenant && cd covenant
cd agent-os && cargo build --workspace --exclude covenant-settlement-program --locked

# Register the example agent (daemon loads $COVENANT_HOME/agents/ at startup)
mkdir -p ~/.covenant/agents
cp -R ../examples/hello-agent ~/.covenant/agents/hello

# Start the daemon
./target/debug/covenantd

Then drive it from either surface — they share the same daemon, audit chain, and capability store.

CLI

./target/debug/covenant capabilities grant memory.write
./target/debug/covenant capabilities grant intent.subscribe
./target/debug/covenant intent "say hello"

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Mizuki: common questions

Is Mizuki MCP server safe?
Mostly: it is graded B (77/100). Read the Mizuki safety report
How do I install Mizuki?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Mizuki need an API key?
Yes. The registry entry asks for MIZUKI_API_TOKEN.
Is Mizuki maintained?
The last commit was 9 days ago (2026-10-27). The latest release is v0.1.2.
What can I use instead of Mizuki?
Servers from other publishers that do the same job: GitDiagram MCP server, GitHub MCP server and Gk CLI MCP server.
How does Mizuki compare with other Developer tools MCP servers?
safety score 77/100 (higher than 45% of 1,119 Developer tools servers); tools 13 (the typical Developer tools server has 7); tools that change things 15% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Mizuki

Same job from other publishers: the closest match first, then the best rated.

  • GitDiagram
    Architecture diagrams, explanations and Mermaid source for public GitHub repositories.
    A
  • GitHub
    Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
    A
  • Gk CLI
    The GitKraken MCP Server for managing repos, PRs, issues across GitHub, GitLab, Bitbucket and more.
    B
  • OctoCounts MCP Server
    Analyze and compare public GitHub repo line counts (SLOC) via OctoCounts, from any MCP client.
    A
  • Pare Github
    Pare GitHub ג€” Structured GitHub operations (PRs, issues, actions) as typed JSON.
    More from Dave-London →
    A