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/LazyAGI/LazyMindInstalling this writes the configuration, not the program: `lazymind` has to be on your PATH already, or the server will not start.
Wrote 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/lazyagi/lazymind/lazymind-workflow-lazymind)<a href="https://agentmods.dev/mcp/lazyagi/lazymind/lazymind-workflow-lazymind"><img src="https://agentmods.dev/badge/mcp/lazyagi/lazymind/lazymind-workflow-lazymind/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/lazyagi/lazymind/lazymind-workflow-lazymind"><img src="https://agentmods.dev/badge/mcp/lazyagi/lazymind/lazymind-workflow-lazymind.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
lazymind 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 17d 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
{
"lazymind": {
"command": "lazymind",
"args": [
"mcp",
"codex-workflow"
]
}
}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.
- 17d ago First seen · 9 lines scan A a6836734f5db
lazymind is an MCP server published in the GitHub repository LazyAGI/LazyMind (214 stars, last pushed today), 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-09-29.
Other mcp servers, from other repositories
engram-server
MCP server "engram-server" as configured in jamjet-labs/jamjet. Runs in Docker (ghcr.io/jamjet-labs/engram-server:0.5.0).
rag-rat
CLI and MCP entrypoint for indexing repositories into local source, graph, history, and memory evidence. Runs locally from the @rag-rat/bin npm package.
context-server
Lightweight MCP server for semantic search over organizational markdown. Runs locally from the context-server Python package.
mcp-kql-server
AI-Powered MCP server for KQL query execution with Natural Language to KQL (NL2KQL) conversion, intelligent schema memory, RAG-enhanced context assistance, and semantic search capabilities. Runs locally from the mcp-kql-server Python package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.