Llm Tools Mcp — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Llm Tools Mcp (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
<div align="center">
llm-tools-mcpConnect to MCP servers right from your shell. Plugin for [llm](https://github.com/simonw/llm) (by [@simonw](https://github.com/simonw)).
</div>
[!Note] Current focus: Authorization #4
Install this plugin in the same environment as LLM:
llm install llm-tools-mcp[!WARNING] It's recommended to use the --ta flag and approve each tool execution.mcp.json file in ~/.llm-tools-mcp.Example file:
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem",
"~/demo"
]
}
}
}[!WARNING] llm tools is not implemented for dynamic toolboxes (see this), so tools loaded as part of MCP won't be visible. llm tools listllm with tools. llm --ta -T MCP "what files are in the demo directory? show me contents of one of the files (any)"Dynamically change your MCP config:
llm --ta -T 'MCP("/path/to/custom/mcp.json")' "your prompt here"uv sync --all-extras./check.sh./test.sh./e2e/e2e-docker.shstdout/stderr from the MCP SDK to a file or designated location~/.llm-tools-mcp directory namingmcp.json is malformeduv?)~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.