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/gaabrielrd/local-model-workers-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/gaabrielrd/local-model-workers-mcp/local-model-workers)<a href="https://agentmods.dev/mcp/gaabrielrd/local-model-workers-mcp/local-model-workers"><img src="https://agentmods.dev/badge/mcp/gaabrielrd/local-model-workers-mcp/local-model-workers.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
local-model-workers 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 7d 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
{
"local-model-workers": {
"command": "local-model-workers-mcp",
"args": [],
"env": {
"LMW_PROVIDERS": "[{\"name\":\"lm-studio\",\"type\":\"lm-studio\",\"base_url\":\"http://pc-gabriel.local:1234/v1\",\"allowed_models\":[\"qwen/qwen3.5-9b\",\"google/gemma-4-12b-qat\"],\"priority\":0,\"tls_verify\":false}]"
}
}
}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.
- 7d ago First seen · 9 lines scan A ff1c099af00d
local-model-workers is an MCP server published in the GitHub repository gaabrielrd/local-model-workers-mcp (1 stars, last pushed 1mo 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
knowledge_catalog
MCP server "knowledgecatalog", hosted remotely at dataplex.googleapis.com, as configured in gemini-cli-extensions/data-agent-kit-starter-pack. Needs 1 environment variable to run.
dataproc
MCP server "dataproc", hosted remotely at dataproc-$gcpregion.googleapis.com, as configured in gemini-cli-extensions/data-agent-kit-starter-pack. Needs 1 environment variable to run.
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.
Pinecone
Model Context Protocol server for Pinecone - enables AI assistants to interact with Pinecone indexes and documentation. Runs locally from the @pinecone-database/mcp npm package. Needs 1 environment variable to run.
hubmesh
Centrality-aware GraphRAG retrieval planner — drop-in layer over any vector DB. Runs locally from the hubmesh Python package.
ollama-vision-mcp
MCP server "ollama-vision-mcp" as configured in masterLazy/ollama-vision-mcp. Runs locally from the ollama-vision-mcp Python package.