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/Ka1y0/Tool_MCP_LMStudioWrote 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/ka1y0/tool_mcp_lmstudio/lmstudio-mcp)<a href="https://agentmods.dev/mcp/ka1y0/tool_mcp_lmstudio/lmstudio-mcp"><img src="https://agentmods.dev/badge/mcp/ka1y0/tool_mcp_lmstudio/lmstudio-mcp/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/ka1y0/tool_mcp_lmstudio/lmstudio-mcp"><img src="https://agentmods.dev/badge/mcp/ka1y0/tool_mcp_lmstudio/lmstudio-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
lmstudio-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 9d 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
{ "lmstudio-mcp": { "command": "npx", "args": [ "-y", "lmstudio-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.
- 9d ago First seen · 9 lines scan A 471535521293
lmstudio-mcp is an MCP server published in the GitHub repository Ka1y0/Tool_MCP_LMStudio (0 stars, last pushed 17d 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
windows-system-sounds-mcp
MCP server "windows-system-sounds-mcp" as configured in vasjabrevno-dev/windows-system-sounds-mcp. Runs locally from the windows-system-sounds-mcp Python package.
ollama-handoff
An MCP server that offloads cheap work from your cloud LLM agent to a local Ollama model. Runs locally from the ollama-handoff Python package. Needs 5 environment variables to run.
claude-prompts-mcp
Reusable prompt templates, multi-step workflow chains, and quality gates for any MCP client. Runs locally from the claude-prompts npm package.
prism-mcp
Persistent session memory for AI coding agents that never leaves your machine — including the on-device model that reasons over it. Restores your prior decisions, open TODOs, and changed files across sessions; adds associative recall of related past work. Runs locally from the prism-mcp-server npm package. Needs 1…
openrouter-multimodal
Chat with 300+ LLMs via OpenRouter. Analyze and generate images, audio, and video from MCP. Runs locally from the @stabgan/openrouter-mcp-multimodal npm package. Needs 13 environment variables to run.
tooltrust-scanner
Scans MCP servers for prompt injection, data exfiltration, and privilege escalation. Runs locally from the tooltrust-mcp npm package.