Local Commander
MCPB · LOCAL-COMMANDER-MCP-AGENT-0.1.3.MCPB · 3 COMPONENTS
Files, Git, allowlisted dev commands, processes and localhost inside folders you choose.
Last scanned (15 hours ago)
Scores higher than 65% of MCPB 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 Security25
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs were checked across the 7 of 7 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- 0 of 7 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until we can run it. How we score packages →
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.
- 17 Oct 26 17
First indexed and scored.
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 23 Oct 2026 · Analysed mcpb/https://github.com/netbka/local-commander-mcp-agent/releases/download/v0.1.3/local-commander-mcp-agent-0.1.3.mcpb
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Dependencies 7 packages
| Packages resolved | 7 |
|---|---|
| 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 →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
How do I install the Local Commander MCP server?
Local Commander ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 36012c8b3e364f294d29ba197552b9f63b1e4f8d981511b4141b3b1e446bc31a; the commands to do that are on this page. If it does not match, do not open it.
mcpb · local-commander-mcp-agent-0.1.3.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
36012c8b3e364f294d29ba197552b9f63b1e4f8d981511b4141b3b1e446bc31a
macOS / Linux
echo "36012c8b3e364f294d29ba197552b9f63b1e4f8d981511b4141b3b1e446bc31a local-commander-mcp-agent-0.1.3.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\local-commander-mcp-agent-0.1.3.mcpb).Hash -eq "36012c8b3e364f294d29ba197552b9f63b1e4f8d981511b4141b3b1e446bc31a"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the Local Commander MCP server?
Local Commander is an MCP server listed in the public MCP registry as io.github.netbka/local-commander-mcp-agent. Files, Git, allowlisted dev commands, processes and localhost inside folders you choose. This page covers its MCPB bundle (https://github.com/netbka/local-commander-mcp-agent/releases/download/v0.1.3/local-commander-mcp-agent-0.1.3.mcpb).
Is the Local Commander MCP server safe to use?
Local Commander scores 17 out of 100 on VerifyMCP. 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 licence is the Local Commander MCP server under?
Local Commander declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.