Desktop Commander MCP

This is MCP server for Claude that gives it terminal control, file system search and diff file editing capabilities

MCP Servers TypeScript Grade C Listed MIT
58.9/100
Rank #402 of 1316
Compare Desktop Commander MCP

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-08-28 · 1d ago
Recent change
Rank +2

Is Desktop Commander MCP safe? Desktop Commander MCP scores 58.9/100 (Grade C), ranked #402 of 1316 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 5.2/10; 83% of recent commits are signed; last pushed 2026-08-28. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-08-26
Rank Moved
Rank dropped 39 spots (#360 → #399)
2026-08-24
Rank Moved
Rank dropped 20 spots (#341 → #361)
2026-08-22
Rank Moved
Rank rose 17 spots (#361 → #344)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.2/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
70.5
Activity sub-score · out of 100
#153

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 →

Signals refreshed 2026-08-29 06:32 UTC · Repo last pushed yesterday

Rank Trend

2026-08-11 2026-08-29

Activity & Reach

Stars
9.4k
Forks
1.1k
Last Push
2026-08-28
yesterday
Commits (4 wk)
3
Downloads (7d)
HN mentions (30d)
Open Issues
157
Rank Change
▼6
was #396

Analysis

HVTrust Dimensions vs MCP Servers

58.9 / 100 · 100.0% confidence

Desktop Commander MCP MCP Servers average (777 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
10.7 / 25
3.8 above avg 6.9
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.5 below avg 13.3
Transparency50% declared license · 50% OSSF Scorecard
12.9 / 17
2.8 above avg 10.1
Maintenance60% last-push freshness · 40% commit activity
14.3 / 20
2.1 above avg 12.2
AdoptionLog-scaled stars · package downloads
9.5 / 20
3.7 above avg 5.8

Activity Inputs

70.5 / 100
StarsRepository reach
23.8 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
7.5 / 25
CommunityFork signal
14.2 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
5.2 / 10
OpenSSF Scorecard · scanned Aug 25, 2026
Signed Commits
83%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 3
CI-Tests 9
CII-Best-Practices 0
Code-Review 5
Contributors 0
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging -1
Pinned-Dependencies 0
SAST 0
Security-Policy 10
Signed-Releases -1
Token-Permissions 10
Vulnerabilities 0

Is Desktop Commander MCP safe?

Desktop Commander MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Desktop Commander MCP publish package provenance?
No published build provenance is currently detected for Desktop Commander MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Desktop Commander MCP have an OpenSSF Scorecard?
Desktop Commander MCP has an OpenSSF Scorecard score of 5.2/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Desktop Commander MCP actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Desktop Commander MCP use?
Desktop Commander MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Desktop Commander MCP's commits signed?
83% of the last 100 commits to Desktop Commander MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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
Scored in HVTrust

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 Server Support
high confidence
Implemented
Desktop Commander MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
3 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • 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
Rank 12Listed 1HVTrust 1Grade 1Scorecard 1
2026-08-26
Rank Moved
Rank dropped 39 spots (#360 → #399)
2026-08-24
Rank Moved
Rank dropped 20 spots (#341 → #361)
2026-08-22
Rank Moved
Rank rose 17 spots (#361 → #344)
2026-08-20
Rank Moved
Rank dropped 14 spots (#348 → #362)
2026-08-17
Rank Moved
Rank rose 10 spots (#352 → #342)
2026-08-16
Rank Moved
Rank dropped 16 spots (#336 → #352)
2026-08-14
Rank Moved
Rank rose 11 spots (#347 → #336)
2026-08-13
Rank Moved
Rank dropped 33 spots (#314 → #347)
2026-08-12
Rank Moved
Rank rose 16 spots (#330 → #314)
2026-08-10
Rank Moved
Rank dropped 18 spots (#311 → #329)
2026-08-08
Rank Moved
Rank dropped 80 spots (#223 → #303)
2026-07-15
Scorecard Added
OSSF Scorecard: 5.2/10
2026-07-15
Grade Changed
Trust grade D → C
2026-07-15
Rank Moved
Rank rose 203 spots (#383 → #180)
2026-07-15
HVTrust Changed
HVTrust up 36.2pts (26.1 → 62.3)
2026-07-14
Newly Listed
First tracked at rank #383

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 58.9 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/desktop-commander-mcp.svg)](https://hvtracker.net/agents/desktop-commander-mcp)
HTML:
<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

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON