io.github.CloudCorpRecords/deskcommand
OCI · GHCR.IO/CLOUDCORPRECORDS/DESKCOMMAND · 2 COMPONENTS
Run terminal processes, edit files and search code on the local machine from an MCP client.
Available components
Last scanned (7 hours ago)
Scores higher than 43% of OCI 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 Security0
- 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 could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
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 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1155 tokens (~44/item across 26 items; 26 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "force_terminate" implies "terminate" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 26 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 0
- Provenance: unverified → fail ▼ security
- 31 Oct 26 38
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 5 Nov 2026 · Analysed oci/ghcr.io/cloudcorprecords/deskcommand@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
create_directory ~37
Create a new directory or ensure a directory exists, including nested paths
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | The directory path to create or ensure exists |
No output schema declared.
No examples provided.
edit_block ~93
Apply a surgical text replacement in a file: replace old_string with new_string
| Name | Type | Req | Description |
|---|---|---|---|
| expected_replacements | number | – | Optional expected number of replacements; the edit fails if the actual count differs |
| file_path | string | yes | The path of the file to edit |
| new_string | string | yes | The text to replace old_string with |
| old_string | string | yes | The exact text in the file to replace |
No output schema declared.
No examples provided.
force_terminate ~34
Force terminate a running terminal process session
| Name | Type | Req | Description |
|---|---|---|---|
| pid | number | yes | The PID of the terminal process session to force terminate |
No output schema declared.
No examples provided.
get_config ~14
Get the current server configuration
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_file_info ~34
Retrieve detailed metadata about a file or directory
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | The path of the file or directory to describe |
No output schema declared.
No examples provided.
get_more_search_results ~61
Get more results from an active search session
| Name | Type | Req | Description |
|---|---|---|---|
| length | number | – | Optional number of results to return |
| offset | number | – | Optional result offset to page from |
| sessionId | string | yes | The search session id returned by start_search |
No output schema declared.
No examples provided.
get_prompts ~43
Get available prompts, or one prompt by id
| Name | Type | Req | Description |
|---|---|---|---|
| promptId | string | – | Optional prompt id to fetch a single prompt; all available prompts are returned when omitted |
No output schema declared.
No examples provided.
get_recent_tool_calls ~20
Get the recent tool calls recorded by this server
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_usage_stats ~16
Get usage statistics for this server
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
give_feedback_to_desktop_commander ~34
Record feedback about this tool for later review
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | The feedback message to record |
No output schema declared.
No examples provided.
interact_with_process ~68
Send input to a running process and wait for its response
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | The input text to send to the process |
| pid | number | yes | The PID of the running process to interact with |
| timeout_ms | number | – | Optional milliseconds to wait for the process response |
No output schema declared.
No examples provided.
kill_process ~30
Terminate a process by its PID
| Name | Type | Req | Description |
|---|---|---|---|
| pid | number | yes | The PID of the process to terminate |
No output schema declared.
No examples provided.
list_directory ~33
Get a detailed listing of all files and directories at a path
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | The directory path to list |
No output schema declared.
No examples provided.
list_processes ~21
List all running processes with their PID, command and status
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_searches ~15
List all active search sessions
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_sessions ~14
List all active terminal sessions
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
move_file ~48
Move or rename a file or directory
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | The new path for the file or directory |
| source | string | yes | The current path of the file or directory to move |
No output schema declared.
No examples provided.
read_file ~62
Read the complete contents of a file, optionally a line range
| Name | Type | Req | Description |
|---|---|---|---|
| length | number | – | Optional number of lines to read |
| offset | number | – | Optional starting line offset to read from |
| path | string | yes | The path of the file to read |
No output schema declared.
No examples provided.
read_multiple_files ~31
Read the contents of multiple files simultaneously
| Name | Type | Req | Description |
|---|---|---|---|
| paths | array | yes | The paths of the files to read |
No output schema declared.
No examples provided.
read_process_output ~56
Read output from a running process, waiting up to a timeout for new output
| Name | Type | Req | Description |
|---|---|---|---|
| pid | number | yes | The PID of the process whose output to read |
| timeout_ms | number | – | Optional milliseconds to wait for new output |
No output schema declared.
No examples provided.
set_config_value ~43
Set a configuration value by key
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | The configuration key to set |
| value | string | yes | The value to set for the configuration key |
No output schema declared.
No examples provided.
start_process ~69
Start a new terminal process in a shell and return its initial output
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | The command line to start in the shell |
| shell | string | – | Optional shell to run the command with |
| timeout_ms | number | – | Optional milliseconds to wait for the process's initial output |
No output schema declared.
No examples provided.
start_search ~133
Start a search for a pattern in files under a path and return a session id
| Name | Type | Req | Description |
|---|---|---|---|
| filePattern | string | – | Optional glob pattern limiting which files are searched |
| ignoreCase | boolean | – | Whether the search ignores case |
| maxResults | number | – | Optional maximum number of results to return |
| path | string | yes | The directory path to search under |
| pattern | string | yes | The pattern to search for |
| searchType | string | – | Optional search type: 'files' searches file names, 'literal' matches the pattern literally, otherwise the pattern is treated as a regular expression over file contents |
No output schema declared.
No examples provided.
stop_search ~33
Stop an active search by its session id
| Name | Type | Req | Description |
|---|---|---|---|
| searchId | string | yes | The search session id returned by start_search |
No output schema declared.
No examples provided.
write_file ~53
Create a new file or completely overwrite an existing file with new content
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The full content to write to the file |
| path | string | yes | The path of the file to create or overwrite |
No output schema declared.
No examples provided.
write_pdf ~60
Write text content to a file at a path (PDF-oriented in the original; this rebuild writes the content as given)
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The content to write to the file |
| path | string | yes | The path of the file to write |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/deskcommand MCP server?
io.github.CloudCorpRecords/deskcommand runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/deskcommand:0.1.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/cloudcorprecords/deskcommand
claude mcp add cloudcorprecords-deskcommand -- docker run --rm -i ghcr.io/cloudcorprecords/deskcommand:0.1.0
What is the io.github.CloudCorpRecords/deskcommand MCP server?
io.github.CloudCorpRecords/deskcommand is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/deskcommand. Run terminal processes, edit files and search code on the local machine from an MCP client. This page covers its container image (ghcr.io/cloudcorprecords/deskcommand).
Is the io.github.CloudCorpRecords/deskcommand MCP server safe to use?
io.github.CloudCorpRecords/deskcommand scores 40 out of 100 on VerifyMCP. 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.CloudCorpRecords/deskcommand MCP server expose?
io.github.CloudCorpRecords/deskcommand exposes 26 tools: create_directory, edit_block, force_terminate, get_config, get_file_info, and 21 more. Their descriptions and schemas cost roughly 1,155 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/deskcommand MCP server still maintained?
io.github.CloudCorpRecords/deskcommand is still listed as active in the MCP registry. We last reached this channel on 5 November 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.CloudCorpRecords/deskcommand MCP server under?
io.github.CloudCorpRecords/deskcommand declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.