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/conquext/neuron-mcp-serverWrote 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/conquext/neuron-mcp-server/neuron)<a href="https://agentmods.dev/mcp/conquext/neuron-mcp-server/neuron"><img src="https://agentmods.dev/badge/mcp/conquext/neuron-mcp-server/neuron/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/conquext/neuron-mcp-server/neuron"><img src="https://agentmods.dev/badge/mcp/conquext/neuron-mcp-server/neuron.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
neuron 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
{
"neuron": {
"command": "npx",
"args": [
"-y",
"neuron-mcp-server"
],
"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 d3eae2a18a64
neuron is an MCP server published in the GitHub repository conquext/neuron-mcp-server (0 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
voidmail
MCP server for agent email: create @voidmail.ai inboxes, send to owner-approved recipients, receive, search and manage aliases. No phone or CAPTCHA. Runs locally from the @voidly/mcp-email npm package.
voidmail-hosted
MCP server "voidmail-hosted", hosted remotely at api.voidly.ai, as configured in voidly-ai/mcp-email.
mcp-aichat
MCP Server for AI Dialogue via AceDataCloud API. Runs locally from the mcp-aichat Python package. Needs 1 environment variable to run.
viber-mcp
MCP server for the Viber Bot REST API — drive a Viber bot from Claude Desktop, Claude Code, or any MCP client. Runs locally from the @serhii.zghama/viber-mcp npm package.
flowcastle
Build, edit, and deploy Telegram bots on FlowCastle's hosted visual flow platform. Remote server at api.flowcastle.ai.
outbox
MCP server "outbox" as configured in fieldcure/fieldcure-mcp-outbox. Launched with FieldCure.Mcp.Outbox.