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/inspectrum)<a href="https://agentmods.dev/mcp/yannmenec/inspectrum/inspectrum"><img src="https://agentmods.dev/badge/mcp/yannmenec/inspectrum/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/inspectrum"><img src="https://agentmods.dev/badge/mcp/yannmenec/inspectrum/inspectrum.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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": {
"command": "npx",
"args": [
"-y",
"inspectrum"
],
"env": {}
}
}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 d80cdae61ced
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-08-31.
Other mcp servers, from other repositories
dvalincode
Deterministic security scanning, no model or API key, plus offline-verifiable proof a fix worked. Runs locally from the dvalincode npm package.
dvalin
Open security engineering for code written by humans and AI agents — every repair carries its own offline-verifiable proof. Runs locally from the dvalincode npm package.
mindtrain
MCP server "mindtrain" as configured in shigella520/MindTrain. Runs ./scripts/mindtrain_mcp_bridge.py with python3.
taskflow
Run taskflow on Claude Code: the npm tarball provides the Claude subagent runner and MCP server; the plugin is distributed through the repository marketplace. Runs locally from the claude-taskflow npm package.
next-devtools-mcp
Next.js development tools MCP server with stdio transport. Runs locally from the next-devtools-mcp npm package.
next-devtools
MCP server "next-devtools" as configured in vercel/next-devtools-mcp. Runs ./dist/index.js with node.