Desktop Commander MCP
Website
This is MCP server for Claude that gives it terminal control, file system search and diff file editing capabilities
Is Desktop Commander MCP safe? Promising trust profile, but some evidence still deserves review.
Compare Desktop Commander MCP
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Desktop Commander MCP scores 59.1/100 (Grade C), ranked #695 of 1371 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.3/10; 8% of recent commits are signed; last pushed 2026-10-13. Every point is earned from checkable signals — never paid placement. How scoring works →
What Desktop Commander MCP can reach, and who runs it
Checked 2026-10-09, each with its source. PUBLISHER is the company's or project's own statement, which we haven't verified; CHECKED is something we observed ourselves. These facts describe the product. They don't change its score.
What it can reach
- PUBLISHER It lets the AI client you connect read and write files and run any terminal command on your machine; the project calls it a privileged local automation tool.
- PUBLISHER Its allowed-directories setting and command blocklist are guardrails against accidents, not a security boundary: terminal commands can still reach files outside the allowed directories. For real isolation the project recommends Docker or a virtual machine.
- PUBLISHER It doesn't try to tell a genuine request from prompt injection; it assumes the connected AI client is trusted.
Where your data goes
- PUBLISHER Telemetry is on by default and can be turned off. It records base command names without their arguments, and no names, email addresses or file paths.
- PUBLISHER Every tool call is logged with its arguments, unredacted, in a file on the machine running it; that file isn't uploaded. If you use Remote Desktop Commander, its service holds tool arguments and results only briefly, to route each call.
Security practice
- CHECKED OSV lists 2 advisories (both low) for its npm package, @wonderwhy-er/desktop-commander, published in June 2026. The repository has a SECURITY.md; GitHub private vulnerability reporting is off.
How Desktop Commander MCP could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Raise the OSSF Scorecard from 4.3 to 9.0lowest checks: CII-Best-Practices 0, Contributors 0, Dependency-Update-Tool 0 +9.8 → 68.9 B · #226 of 781
- Sign every commit8% signed today +4.6 → 63.7 C · #310 of 781
Chain of custody
Scanners check what the code says. This traces who ships Desktop Commander MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Partly signed
github.com/wonderwhy-er/DesktopCommanderMCP, MIT, last pushed 2026-10-13. 8% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 4.3/10 (scanned Oct 1, 2026). The checks that decide who can get a change released:
- Code Review3
- Branch Protection3
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies2
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 3CI-Tests 8CII-Best-Practices 0Code-Review 3Contributors 0Dangerous-Workflow 10Dependency-Update-Tool 0Fuzzing 0License 10Maintained 10Packaging 10Pinned-Dependencies 2SAST 0Security-Policy 10Signed-Releases 0Token-Permissions 0Vulnerabilities 0 -
Published packages None
No registry package. Desktop Commander MCP is used from its repository, so what you run is whatever you check out: pin a release tag or commit.
Changes to this chain
No change to package provenance, package source links, Scorecard coverage or license in HVTracker's daily snapshots of Desktop Commander MCP.
Evidence behind this score
Coverage C: 2 of 5 independent evidence types found.
- GitHub repository data
- Package downloads (missing)
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues Desktop Commander MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How Desktop Commander MCP compares in MCP Servers
- #376 PostgreSQL MCP Server 59.1 ±0
- #377 Sub Agents MCP 59.1 ±0
- #378 Desktop Commander MCP 59.1 this agent
- #379 ChromaDB Remote MCP Server 59.0 −0.1
- #380 RPG Maker MV Ultimate MCP 59.0 −0.1
Bars show each HVTrust score; the tick marks Desktop Commander MCP’s 59.1.
Where the 59.1 comes from
HVTrust dimensions vs the MCP Servers average
59.1 / 100 · 100.0% confidenceDesktop Commander MCP MCP Servers average (781 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
88.4 / 100Common questions about Desktop Commander MCP
Does Desktop Commander MCP publish package provenance?
Does Desktop Commander MCP have an OpenSSF Scorecard?
Is Desktop Commander MCP actively maintained?
What license does Desktop Commander MCP use?
Are Desktop Commander MCP's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Maintain Desktop Commander MCP?
For maintainers
HVTrust scores Desktop Commander MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/desktop-commander-mcp)
<a href="https://hvtracker.net/agents/desktop-commander-mcp"><img src="https://hvtracker.net/badge/desktop-commander-mcp.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON