io.github.CloudCorpRecords/termmux
NPM · @RENETURCIOS/TERMMUX · 2 COMPONENTS
Drive local tmux sessions, windows and panes: list, create, send keys, capture output.
Available components
Last scanned (43 minutes ago)
Scores higher than 31% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
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 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 633 tokens (~52/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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; "kill_session" implies "kill" 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 12 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.
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 48
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 npm/@reneturcios/termmux@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 | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
capture_pane ~73
Capture the visible contents of a tmux pane as text
| Name | Type | Req | Description |
|---|---|---|---|
| lines | number | – | Optional number of lines of pane history to capture |
| pane_target | string | – | Optional pane target (window.pane) to capture |
| session_name | string | yes | The name of the tmux session containing the pane |
No output schema declared.
No examples provided.
create_session ~62
Create a new tmux session
| Name | Type | Req | Description |
|---|---|---|---|
| session_name | string | yes | The name for the new tmux session |
| start_directory | string | – | Optional working directory the session starts in |
| window_name | string | – | Optional name for the session's first window |
No output schema declared.
No examples provided.
create_window ~67
Create a new window in a tmux session
| Name | Type | Req | Description |
|---|---|---|---|
| session_name | string | yes | The name of the tmux session to create the window in |
| start_directory | string | – | Optional working directory the window starts in |
| window_name | string | yes | The name for the new window |
No output schema declared.
No examples provided.
get_session_info ~43
Get details of one tmux session: window count, creation time and attached state
| Name | Type | Req | Description |
|---|---|---|---|
| session_name | string | yes | The name of the tmux session to describe |
No output schema declared.
No examples provided.
kill_session ~33
Kill a tmux session by name
| Name | Type | Req | Description |
|---|---|---|---|
| session_name | string | yes | The name of the tmux session to kill |
No output schema declared.
No examples provided.
kill_window ~50
Kill a window in a tmux session
| Name | Type | Req | Description |
|---|---|---|---|
| session_name | string | yes | The name of the tmux session containing the window |
| window_name | string | yes | The name of the window to kill |
No output schema declared.
No examples provided.
list_panes ~60
List the panes of a tmux session, optionally of one window
| Name | Type | Req | Description |
|---|---|---|---|
| session_name | string | yes | The name of the tmux session whose panes to list |
| window_name | string | – | Optional window name to limit the listing to one window |
No output schema declared.
No examples provided.
list_sessions ~14
List all tmux sessions
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_windows ~36
List the windows of a tmux session
| Name | Type | Req | Description |
|---|---|---|---|
| session_name | string | yes | The name of the tmux session whose windows to list |
No output schema declared.
No examples provided.
rename_session ~44
Rename a tmux session
| Name | Type | Req | Description |
|---|---|---|---|
| new_name | string | yes | The new name for the session |
| session_name | string | yes | The current name of the tmux session |
No output schema declared.
No examples provided.
select_window ~53
Select (activate) a window in a tmux session
| Name | Type | Req | Description |
|---|---|---|---|
| session_name | string | yes | The name of the tmux session containing the window |
| window_name | string | yes | The name of the window to select |
No output schema declared.
No examples provided.
send_keys ~98
Send keys (a command line or key names) to a tmux pane
| Name | Type | Req | Description |
|---|---|---|---|
| keys | string | yes | The command line or key names to send to the pane |
| pane_target | string | – | Optional pane target (window.pane) to send the keys to |
| press_enter | boolean | – | Whether to press Enter after sending the keys |
| session_name | string | yes | The name of the tmux session containing the target pane |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/termmux MCP server?
io.github.CloudCorpRecords/termmux runs locally as an npm package, launched with npx -y @reneturcios/termmux. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/termmux
claude mcp add cloudcorprecords-termmux -- npx -y @reneturcios/termmux
What is the io.github.CloudCorpRecords/termmux MCP server?
io.github.CloudCorpRecords/termmux is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/termmux. Drive local tmux sessions, windows and panes: list, create, send keys, capture output. This page covers its npm package (@reneturcios/termmux).
Is the io.github.CloudCorpRecords/termmux MCP server safe to use?
io.github.CloudCorpRecords/termmux scores 63 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. 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 tools does the io.github.CloudCorpRecords/termmux MCP server expose?
io.github.CloudCorpRecords/termmux exposes 12 tools: list_sessions, create_session, kill_session, list_windows, create_window, and 7 more. Their descriptions and schemas cost roughly 633 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/termmux MCP server still maintained?
io.github.CloudCorpRecords/termmux 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/termmux MCP server under?
io.github.CloudCorpRecords/termmux declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.