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/chriswayneh/local-mcp-toolboxWrote 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/chriswayneh/local-mcp-toolbox/claude-code-local-mcp-toolbox)<a href="https://agentmods.dev/mcp/chriswayneh/local-mcp-toolbox/claude-code-local-mcp-toolbox"><img src="https://agentmods.dev/badge/mcp/chriswayneh/local-mcp-toolbox/claude-code-local-mcp-toolbox/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/chriswayneh/local-mcp-toolbox/claude-code-local-mcp-toolbox"><img src="https://agentmods.dev/badge/mcp/chriswayneh/local-mcp-toolbox/claude-code-local-mcp-toolbox.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
local-mcp-toolbox 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 8d 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
{
"local-mcp-toolbox": {
"command": "${LOCAL_MCP_TOOLBOX_EXE}",
"args": [
"serve",
"--config",
"${LOCAL_MCP_TOOLBOX_CONFIG}"
]
}
}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.
- 8d ago First seen · 10 lines scan A 4046c25f848c
local-mcp-toolbox is an MCP server published in the GitHub repository chriswayneh/local-mcp-toolbox (0 stars, last pushed 19d 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
moira
MCP server "moira" as configured in moira-mcp/moira. Runs in Docker (ghcr.io/moira-mcp/moira:0.3.4).
servicenow
MCP server "servicenow" as configured in serac-labs/serac. Runs locally from the servicenow-mcp-stdio npm package.
better-godot-mcp
MCP server for Godot Engine 4.x with 17 tools for scenes, scripts, and shaders. Runs locally from the @n24q02m/better-godot-mcp npm package. Needs 2 environment variables to run.
maven-tools-mcp
MCP server "maven-tools-mcp" as configured in arvindand/maven-tools-mcp. Runs in Docker (docker.io/arvindand/maven-tools-mcp:latest).
toon-memory
Offline persistent memory for AI coding agents — 35 tools, 80% fewer calls, no LLM. Runs locally from the toon-memory npm package. Needs 6 environment variables to run.
mcp-producer
MCP Server for Producer AI Music Generation via AceDataCloud API. Runs locally from the mcp-producer Python package. Needs 1 environment variable to run.