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/RudrenduPaul/NeuronScopeWrote 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/rudrendupaul/neuronscope/neuronscope)<a href="https://agentmods.dev/mcp/rudrendupaul/neuronscope/neuronscope"><img src="https://agentmods.dev/badge/mcp/rudrendupaul/neuronscope/neuronscope/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/rudrendupaul/neuronscope/neuronscope"><img src="https://agentmods.dev/badge/mcp/rudrendupaul/neuronscope/neuronscope.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
neuronscope 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
{
"neuronscope": {
"command": "uvx",
"args": [
"neuronscope-cli",
"neuronscope-cli"
],
"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.
- 10d ago First seen · 10 lines scan A d710ead66fea
neuronscope is an MCP server published in the GitHub repository RudrenduPaul/NeuronScope (1 stars, last pushed 16d 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
truthroute
Sends the same prompt to multiple LLM providers in parallel and returns a divergence score via MCP. Runs locally from the truthroute-cli npm package.
traintools
Agent-ready, paper-backed PyTorch training diagnostics for gradients, batches, data quality, plasticity, and stopping. Runs locally from the traintools Python package.
aiglare
Audit AI/LLM features for governance guardrails: confidence, fallback, validation, human-in-loop. Runs locally from the @nugehs/aiglare npm package.
spectral
Spectral Python (SPy) is a Python module for hyperspectral image processing. Runs locally from the spectral Python package.
agentbridge
MCP server that exposes AgentBridge actions to AI agents with confirmation gates, origin pinning, and audit logging. Default stdio transport plus an opt-in Streamable HTTP transport with bearer auth. Runs locally from the @marmarlabs/agentbridge-mcp-server npm package.
lumo
library to manage your pytorch experiments. Runs locally from the lumo Python package.