io.github.bytedance/mcp-server-commands
NPM · @AGENT-INFRA/MCP-SERVER-COMMANDS
An MCP server to run arbitrary commands
Available components
Last scanned (21 hours ago)
Scores higher than 38% 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 Security50
- No malware found by supply-chain analysis.Pass
- Known CVEs could not be checked: the version this server declares is not published in its registry.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: the version this server declares is not published in its registry.Unverified
Provenance & Transparency34
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: the declared version isn't published, so its provenance can't be verified. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 340 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 120 tokens (~60/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- Malware scan
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (3)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Known CVEs in Supply Chain SecurityKnown CVEs could not be checked: the version this server declares is not published in its registry.
- Install scripts in Supply Chain SecurityInstall-script risk not yet assessed.
- Dependency health in Supply Chain SecurityDependency health could not be checked: the version this server declares is not published in its registry.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 19 Nov 26 +1
- Stability: 0.97 → pass security
- 18 Nov 26 −1
- Stability: pass → 0.97 functional
- 12 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 −2
- Stability: pass → 0.90 functional
- 3 Nov 26 +1
- Stability: 0.97 → pass security
- 2 Nov 26 −1
- Stability: pass → 0.97 functional
- 27 Oct 26 +1
- Stability: 0.97 → pass security
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 21 Nov 2026 · Analysed npm/@agent-infra/mcp-server-commands@latest
Provenance Version not published
The package exists but this version is not published, so there is no artifact to attest.
| Result | Version not published |
|---|---|
| Ecosystem | npm |
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 →
run_command ~42
Run a command on this linux machine
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | Command with args |
| cwd | string | – | Current working directory, leave empty in most cases |
No output schema declared.
No examples provided.
run_script ~78
Run a script on this linux machine
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | Current working directory, leave empty in most cases |
| interpreter | string | – | Command with arguments. Script will be piped to stdin. Examples: bash, fish, zsh, python, or: bash --norc |
| script | string | yes | Script to run |
No output schema declared.
No examples provided.
How do I install the io.github.bytedance/mcp-server-commands server?
io.github.bytedance/mcp-server-commands runs locally as an npm package, launched with npx -y @agent-infra/mcp-server-commands. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @agent-infra/mcp-server-commands
claude mcp add bytedance-mcp-server-commands -- npx -y @agent-infra/mcp-server-commands
What is the io.github.bytedance/mcp-server-commands server?
io.github.bytedance/mcp-server-commands is listed in the public MCP registry as io.github.bytedance/mcp-server-commands. An MCP server to run arbitrary commands. This page covers its npm package (@agent-infra/mcp-server-commands).
Is the io.github.bytedance/mcp-server-commands server safe to use?
io.github.bytedance/mcp-server-commands scores 67 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.bytedance/mcp-server-commands server expose?
io.github.bytedance/mcp-server-commands exposes 2 tools: run_command, run_script. Their descriptions and schemas cost roughly 120 tokens of context every time the server is loaded.
Is the io.github.bytedance/mcp-server-commands server still maintained?
io.github.bytedance/mcp-server-commands is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the io.github.bytedance/mcp-server-commands server?
VerifyMCP ran 13 checks on io.github.bytedance/mcp-server-commands, covering Malware scan, Source repository, Provenance, License and 9 more. 3 items could not be completed, a gap on our side rather than a finding about io.github.bytedance/mcp-server-commands: Known CVEs, Install scripts and Dependency health. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.