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/solhammer/agentoolboxWrote 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/solhammer/agentoolbox/agent-toolbox)<a href="https://agentmods.dev/mcp/solhammer/agentoolbox/agent-toolbox"><img src="https://agentmods.dev/badge/mcp/solhammer/agentoolbox/agent-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/solhammer/agentoolbox/agent-toolbox"><img src="https://agentmods.dev/badge/mcp/solhammer/agentoolbox/agent-toolbox.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agent-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 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
{
"agent-toolbox": {
"command": "npx",
"args": [
"-y",
"agentoolbox-mcp"
],
"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 6c534f44d66d
agent-toolbox is an MCP server published in the GitHub repository solhammer/agentoolbox (0 stars, last pushed 2mo 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
mcp-server
Detect fabrication and hallucination in any LLM output. 30+ models supported. Runs locally from the @arkheia/mcp-server npm package. Needs 1 environment variable to run.
trusted-transcription
MCP server "trusted-transcription" as configured in Guillain-RDCDE/Trusted-Transcription. Runs locally from the trusted-transcription Python package.
honestcode
A lightweight MCP server that detects AI code hallucinations in real time — undefined symbols, wrong API calls, dead code, and type mismatches. Runs locally from the honestcode Python package.
mcp-tool-server
MCP server "mcp-tool-server" as configured in Kartik281204/MCP-Tool-Server. Runs locally from the mcp-tool-server Python package.
bridgenode-mcp
BridgeNode — x402 pay-per-request AI inference. OpenAI-compatible API + MCP, Solana USDC, gas-free. Runs locally from the @bridgenode/mcp npm package.
bridgenode
MCP server "bridgenode", hosted remotely at bridgenode.cc, as configured in bridgenode-ai/bridgenode-skill.