Mushi Mushi
NPM · @MUSHI-MUSHI/MCP · 2 COMPONENTS
The bug mediator for AI-built apps: plain-English diagnosis + a ready fix, in your editor.
Available components
Last scanned (1 hour ago)
Scores higher than 98% 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 5 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to kensaurus/mushi-mushi). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 492 tokens (~164/item across 3 items; 3 tools + 0 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 80% of tool parameters carry a description.Partial
- Structured output schemas are declared (67% 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
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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.
- 4 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.30.2 → 0.30.3 functional
- 31 Oct 26 0
- Stability: 0.97 → pass security
- 30 Oct 26 +1
- Known CVEs: pass → unverified ▼ security
- Dependency health: 1.00 → unverified ▼ functional
- Package version: 0.30.0 → 0.30.2 functional
- Package version: 0.30.0 → 0.30.1 functional
- 29 Oct 26 −1
- Stability: pass → 0.93 functional
- 28 Oct 26 0
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Package version: 0.29.2 → 0.30.0 functional
- 27 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Package version: 0.24.6 → 0.29.2 functional
- 26 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Dependency health: 1.00 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Package version: 0.29.0 → 0.29.2 functional
- Package version: 0.29.0 → 0.29.1 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 5 Nov 2026 · Analysed npm/@mushi-mushi/mcp@0.30.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | kensaurus/mushi-mushi |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/kensaurus/mushi-mushi/.github/workflows/release.yml@refs/heads/master |
| Rekor log index | 3666289876 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:2c36e068a07cf01a64072aa433517e993914ac8ddb764a4070e1cf08b37d440cf929d20136a445d59426cf61e7bf9d200cfaa9a21217924a548e824ec |
Background: How many MCP packages publish verified provenance →
Dependencies 5 packages
| Packages resolved | 5 |
|---|---|
| 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 →
diagnose_setup Unified setup diagnose ~153
Diagnose Mushi setup health and return the single best next action. mode=full (default) runs both SDK-ingest and fix-dispatch preflight checks; mode=ingest runs ingest checks only (project exists, active API key, SDK heartbeat, at least one report); mode=dispatch runs dispatch readiness only (GitHub connected, codebase indexed, LLM key present, autofix enabled). Returns { ready, steps: [{ label, complete, required, hint }], nextAction }. Read-only. The one setup-diagnosis entry point — use this instead of separate connection/ingest checks.
| Name | Type | Req | Description |
|---|---|---|---|
| mode | string | – | – |
| projectId | string | – | (`project_id` is accepted too.) |
No output schema declared.
No examples provided.
get_mushi_doc Read a Mushi docs page ~120
Fetch one official Mushi docs page as Markdown, by a url from search_mushi_docs or a route such as "/quickstart/mcp". Returns { title, url, markdown, truncated }; markdown is capped at 8,000 characters and says where to read the rest. Only indexed docs pages resolve. Read-only; works without an API key. Use after search_mushi_docs when an excerpt is not enough.
| Name | Type | Req | Description |
|---|---|---|---|
| page | string | yes | A url from search_mushi_docs, or a docs route such as "/quickstart/mcp". |
| Name | Type | Req | Description |
|---|---|---|---|
| markdown | string | yes | – |
| title | string | yes | – |
| truncated | boolean | yes | – |
| url | string | yes | – |
No examples provided.
search_mushi_docs Search Mushi documentation ~141
Search the official Mushi documentation (guides, MCP setup, inventory, QA, skills) by keyword — titles, section headings and summaries are indexed. Returns ranked { results: [{ title, url, excerpt, score }] }. Read-only; works without an API key. Use before guessing API shapes, tool names, or RPC names, then get_mushi_doc to read a page; use run_nl_query for questions about your own project data, not the docs.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results (default 8). |
| query | string | yes | Keywords to search official Mushi docs (guides, MCP, inventory, QA). |
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
| results | array | yes | – |
No examples provided.
How do I install the Mushi Mushi MCP server?
Mushi Mushi runs locally as an npm package, launched with npx -y @mushi-mushi/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 · @mushi-mushi/mcp
claude mcp add kensaurus-mushi-mushi -- npx -y @mushi-mushi/mcp
What is the Mushi Mushi MCP server?
Mushi Mushi is an MCP server listed in the public MCP registry as io.github.kensaurus/mushi-mushi. The bug mediator for AI-built apps: plain-English diagnosis + a ready fix, in your editor. This page covers its npm package (@mushi-mushi/mcp).
Is the Mushi Mushi MCP server safe to use?
Mushi Mushi scores 95 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Mushi Mushi MCP server expose?
Mushi Mushi exposes 3 tools: search_mushi_docs, get_mushi_doc, diagnose_setup. Their descriptions and schemas cost roughly 414 tokens of context every time the server is loaded.
Is the Mushi Mushi MCP server still maintained?
Mushi Mushi is still listed as active in the MCP registry. We last reached this channel on 5 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 Mushi Mushi MCP server under?
Mushi Mushi declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.