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/JanYork/llm-wiki-cliInstalling this writes the configuration, not the program: `lwc` 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/janyork/llm-wiki-cli/claude-lwc-lwc)<a href="https://agentmods.dev/mcp/janyork/llm-wiki-cli/claude-lwc-lwc"><img src="https://agentmods.dev/badge/mcp/janyork/llm-wiki-cli/claude-lwc-lwc/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/janyork/llm-wiki-cli/claude-lwc-lwc"><img src="https://agentmods.dev/badge/mcp/janyork/llm-wiki-cli/claude-lwc-lwc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
lwc 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 2mo 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
{
"lwc": {
"type": "stdio",
"command": "lwc",
"args": [
"serve",
"--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.
- 2mo ago First seen · 10 lines scan A 97544c4573a5
lwc is an MCP server published in the GitHub repository JanYork/llm-wiki-cli (72 stars, last pushed 1mo 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-30.
lwc compared with mcp servers from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| lwcJanYork/llm-wiki-cli | MCP server | 72 | 1mo ago | Apache-2.0 | A | — | Claude Code |
| chrome-devtoolsPackmindHub/packmind | MCP server | 321 | 9d ago | Apache-2.0 | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| hypermnesia-mcpcdeust/Cortex | MCP server | 76 | yesterday | MIT | A | — | Claude Code |
| engineering-osengineering-os/engineering-os | MCP server | 34 | 4mo ago | Apache-2.0 | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| playwrightnguyenthienthanh/aura-frog | MCP server | 25 | 15d ago | MIT | A | — | Claude Code |
| lore-context-mcpLore-Context/lore-context | MCP server | 4 | 25d ago | none | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |
| playwrightreqvire-org/reqvire | MCP server | 30 | 3d ago | Apache-2.0 | A | — | Claude Code, Codex, Cursor, Gemini CLI, OpenCode |