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.
git clone --depth 1 https://github.com/yannmenec/inspectrumWrote 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/yannmenec/inspectrum/cursor-inspectrum)<a href="https://agentmods.dev/mcp/yannmenec/inspectrum/cursor-inspectrum"><img src="https://agentmods.dev/badge/mcp/yannmenec/inspectrum/cursor-inspectrum/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/yannmenec/inspectrum/cursor-inspectrum"><img src="https://agentmods.dev/badge/mcp/yannmenec/inspectrum/cursor-inspectrum.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
inspectrum 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 1mo 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
{
"inspectrum": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"inspectrum@latest"
]
}
}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.
- 1mo ago First seen · 10 lines scan A 1a0d19c625cd
inspectrum is an MCP server published in the GitHub repository yannmenec/inspectrum (2 stars, last pushed 1mo 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-09-10.
Other mcp servers, from other repositories
scopewalker-mcp
Codebase analysis tools for AI agents: complexity, prop drilling, doc coverage, code smells. Runs locally from the scopewalker-mcp npm package. Needs 1 environment variable to run.
codereview
Risk-scan a diff, flag AI-generated-code tells, find secrets. 5 of 7 tools need no account. Remote server at mcp.moltlinestudio.com.
contextflux
MCP server "contextflux" as configured in divyanshu-iitian/ContextFlux. Runs locally from the contextflux npm package.
idencify
Whole-repo code graph for AI agents: impact analysis, dead code, cycles, semantic search — 14 tools. Remote server at mcp.idencify.com.
atelier-quality-gate
Two-agent post-generation quality gate (UI/UX Critic & Backend Architecture Guard) for vibe-coded apps. Runs locally from the atelier-quality-gate npm package.
vdiff-mcp
Breaking-change diffs for npm packages: removed exports, changed signatures, migration notes. Runs locally from the vdiff-mcp npm package. Needs 1 environment variable to run.