Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add mcp/kensaurus/mushi-mushi/mushi-stdiogit clone --depth 1 https://github.com/kensaurus/mushi-mushiWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/kensaurus/mushi-mushi/mushi-stdio)<a href="https://agentmods.dev/mcp/kensaurus/mushi-mushi/mushi-stdio"><img src="https://agentmods.dev/badge/mcp/kensaurus/mushi-mushi/mushi-stdio.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
mushi-stdio scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"mushi-stdio": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@mushi-mushi/mcp@latest"
],
"env": {
"MUSHI_API_KEY": "${MUSHI_API_KEY:-}",
"MUSHI_PROJECT_ID": "${MUSHI_PROJECT_ID:-}",
"MUSHI_API_ENDPOINT": "https://dxptnwrhwsqckaftyymj.supabase.co/functions/v1/api"
}
}
}What else .mcp.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 15 lines scan A 7a46e69d7a3f
mushi-stdio is an MCP server published in the GitHub repository kensaurus/mushi-mushi (3 stars, last pushed 8d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
crumbtrail
MCP server "crumbtrail", hosted remotely, as configured in CrumbtrailDev/crumbtrail-cli.
mcp
Feedbug MCP server: read visual bug reports (screenshot, console, DOM context) and let your AI agent trace them to source and fix them. Runs locally from the @feedbug/mcp npm package.
mcp-server
Unified MCP server for Ignite UI — documentation, API, and CLI scaffolding. Runs locally from the @igniteui/mcp-server npm package.
repo-lens-mcp
MCP server for multi-repository AST-based symbol search and API route discovery. Runs locally from the repo-lens-mcp npm package.
mcp-search
MCP server "mcp-search" as configured in thedotmack/claude-mem. Runs const f=require('fs'),p=require('path'),o=require('os'),c=require('child_process');const h=o.homedir();const C=process.env.CLAUDE_CONFIG_DIR||p.join(h,'.claude');const E=process.env.CLAUDE_PLUGIN_ROOT||process.env.PLUGIN_ROOT||'';const…
claude-flow
Ruflo CLI - Enterprise AI agent orchestration with 60+ specialized agents, swarm coordination, MCP server, self-learning hooks, and vector memory for Claude Code. Runs locally from the @claude-flow/cli npm package. Needs 6 environment variables to run.