Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/hmmhmmhm/daiso-mcp/ghidra)<a href="https://agentmods.dev/mcp/hmmhmmhm/daiso-mcp/ghidra"><img src="https://agentmods.dev/badge/mcp/hmmhmmhm/daiso-mcp/ghidra/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/hmmhmmhm/daiso-mcp/ghidra"><img src="https://agentmods.dev/badge/mcp/hmmhmmhm/daiso-mcp/ghidra.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
ghidra 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 10d 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
{
"ghidra": {
"command": "python3",
"args": [
"/Users/hm/Documents/GitHub/daiso-mcp/scripts/ghidra/cli_mcp_ghidra.py"
]
}
}What else .mcp.json configures
This page is one entry in a file that holds 3. 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.
- 10d ago First seen · 8 lines scan A 62f08de07d00
ghidra is an MCP server published in the GitHub repository hmmhmmhm/daiso-mcp (327 stars, last pushed today), 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-30.
Other mcp servers, from other repositories
agentmap
The TS/JS-accurate repo map for coding agents: ts-morph import/symbol/call graph + MCP query tools. Runs locally from the @raymondchins/agentmap npm package.
sqry
MCP server "sqry" as configured in verivus-oss/sqry. Runs in Docker (ghcr.io/verivus-oss/sqry:4.8.16).
prodlint
Production readiness for vibe-coded apps. 52 checks for security, reliability, and performance. Runs locally from the prodlint npm package.
depwire
Dependency graph + 24 MCP tools. Impact analysis, simulation, security, agent coordination. Runs locally from the depwire-cli npm package.
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.
ovecc
Architecture guardrails for AI-written code: dependency graph, impact, dead code, CI gate. Runs locally from the ovecc npm package.