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/botAGI/agmind-mcpWrote 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/botagi/agmind-mcp/agmind-mcp)<a href="https://agentmods.dev/mcp/botagi/agmind-mcp/agmind-mcp"><img src="https://agentmods.dev/badge/mcp/botagi/agmind-mcp/agmind-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
agmind-mcp 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 6d 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
{ "agmind-mcp": { "command": "npx", "args": [ "-y", "agmind-mcp" ] } }
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.
- 6d ago First seen · 9 lines scan A 3f378ea203b1
agmind-mcp is an MCP server published in the GitHub repository botAGI/agmind-mcp (0 stars, last pushed 4d ago), licensed Apache-2.0. 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
gguf-mcp
Inspect local GGUF/safetensors models: quantization, params, VRAM fit — headers only. Runs locally from the gguf-mcp npm package.
voltage-input-mcp
MCP server "voltage-input-mcp" as configured in casualkre/voltage-input-mcp. Runs locally from the voltage-input-mcp Python package.
genome
DNA-inspired memory layer for AI agents: zero-LLM-call ingestion, retrieval that beats full-context on overflowing histories. Runs locally from the genome-memory Python package.
ai-guardian
Governed observability + governance for on-endpoint local LLMs (Ollama): model inventory/provenance, a deterministic secrets/PII/jailbreak prompt scanner, allow/deny policy, and route-through guarding — the complement to IGEL AI Armor, with a built-in governance harness (audit, budget, undo, risk tiers). Runs locally…
mcp-ollama
MCP server "mcp-ollama" as configured in true-alter/mcp-ollama. Runs locally from the @truealter/mcp-ollama npm package.
sqlbench
MCP server "sqlbench" as configured in rctruta/sql-benchmarks-dagster. Runs mcp_server.py with python.