io.github.JoblessJoe/local-llm-worker
NPM · LOCAL-LLM-WORKER
Local LLM does Claude's bulk work: reads logs and files, researches the web, writes test-gated code.
Available components
Last scanned (20 hours ago)
Scores higher than 40% of npm servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency13
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Maintenance check failed: the publisher has marked this version as deprecated on the registry, telling users to stop installing it. See how to fix → Fail
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 813 tokens (~203/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 −6
- Source repository: pass → fail ▼ security
- Maintenance: pass → fail ▼ functional
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +35
- Injection markers: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.30 ▲ functional
- 13 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 12 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- Package version: 0.1.0 → 0.1.4 functional
- 8 Oct 26 −31
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Package version: 0.1.0 → 0.1.3 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Oct 2026 · Analysed npm/local-llm-worker@0.1.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
configure ~195
Set up or change local-llm-worker (backend URL, models, search, which tools to use automatically via auto_use). No arguments: effective config, where each value comes from, config file paths, detected backend API, reachability and the backend's model list. With {set, scope}: merge keys into the user or project config file (null removes a key). Changes apply on the next call without a restart. Call this first on a new machine.
| Name | Type | Req | Description |
|---|---|---|---|
| scope | string | – | Which file to write (default user). |
| set | object | – | Keys to change. Valid keys: base_url, api, api_key, headers, model, offload_model, delegate_model, research_model, search_url, research_sources, page_timeout_ms, allow_private_urls, num_ctx, max_toke… |
No output schema declared.
No examples provided.
delegate ~272
Implement a small function, helper or file with the LOCAL model: write the test first, then call this. The local model writes ONE file until YOUR test command passes, in an isolated git worktree. Returns only a PASS/FAIL verdict. Write the test first; the worker never sees test source, only parsed failures. Independent delegates can run in parallel. Read the diff before relying on the result.
| Name | Type | Req | Description |
|---|---|---|---|
| apply | boolean | – | Copy the passing file into the checkout (default true). |
| context | string | – | Exact API surface the file may use, verbatim (names, signatures, return shapes). |
| max_attempts | integer | – | Generate/test rounds (default from config). |
| model | string | – | Override the configured model for this call. |
| properties | – | – | Invariants that must hold for every input, ideally one per gating test. |
| show_code | boolean | – | Also return the code (default false: costs tokens). |
| spec | string | yes | What the file must do. Resolve every ambiguity here. |
| target_file | string | yes | File to create or modify, relative to the git root. |
| test_command | string | yes | Shell command run in the worktree; exit 0 = pass. |
| test_files | array | – | Test files; the target may not be one of them. |
No output schema declared.
No examples provided.
offload ~160
Read big output with the LOCAL model instead of reading it yourself: test runs, builds, logs, large files or diffs. It reads files and/or a command's output and answers your question. Only the short answer comes back, so large logs, files or diffs never enter your context. Good for: summarising a huge test log, finding where something is defined across big files, extracting numbers.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | – | Shell command whose stdout+stderr is the material (e.g. a test run). |
| files | array | – | Paths relative to the git root (or cwd outside a repo). |
| model | string | – | Override the configured model for this call. |
| task | string | yes | The question to answer from the material. |
No output schema declared.
No examples provided.
research ~186
Web lookup with the LOCAL model, instead of WebSearch/WebFetch: docs, current versions, facts from pages. Answers a question from the live web WITHOUT the pages entering your context. Searches SearXNG (or reads the "urls" you give), downloads the pages in full, has the LOCAL model answer with inline [n] citations, and returns only that answer plus the source list. Use it when the details on the pages matter. Slow by design: expect tens of seconds to minutes.
| Name | Type | Req | Description |
|---|---|---|---|
| max_sources | integer | – | Pages to read when searching (default from config). |
| model | string | – | Override the configured model for this call. |
| query | string | – | Search query if it should differ from the question. |
| question | string | yes | The research question, in full. |
| urls | array | – | Read these pages instead of searching (no search_url needed). |
No output schema declared.
No examples provided.
How do I install the io.github.JoblessJoe/local-llm-worker MCP server?
io.github.JoblessJoe/local-llm-worker runs locally as an npm package, launched with npx -y local-llm-worker. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · local-llm-worker
claude mcp add joblessjoe-local-llm-worker -- npx -y local-llm-worker
What is the io.github.JoblessJoe/local-llm-worker MCP server?
io.github.JoblessJoe/local-llm-worker is an MCP server listed in the public MCP registry as io.github.JoblessJoe/local-llm-worker. Local LLM does Claude's bulk work: reads logs and files, researches the web, writes test-gated code. This page covers its npm package (local-llm-worker).
Is the io.github.JoblessJoe/local-llm-worker MCP server safe to use?
io.github.JoblessJoe/local-llm-worker scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.JoblessJoe/local-llm-worker MCP server expose?
io.github.JoblessJoe/local-llm-worker exposes 4 tools: offload, research, delegate, configure. Their descriptions and schemas cost roughly 813 tokens of context every time the server is loaded.
Is the io.github.JoblessJoe/local-llm-worker MCP server still maintained?
io.github.JoblessJoe/local-llm-worker is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.JoblessJoe/local-llm-worker MCP server under?
io.github.JoblessJoe/local-llm-worker declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.