io.github.amol21p/interactive-terminal
NPM · MCP-INTERACTIVE-TERMINAL · SCANNED SEP 20
MCP server for real interactive terminal sessions — REPLs, SSH, databases, Docker
Available components
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 Security86
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Install-script check failed: the install command fetches or executes arbitrary code (inline_eval). An install hook runs on every machine, in CI, and on transitive installs, whether or not you ever run the server. View diagnostics → Fail
- 33 of 106 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 215 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 595 tokens (~85/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 7 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
How do I install the io.github.amol21p/interactive-terminal MCP server?
io.github.amol21p/interactive-terminal runs locally as an npm package, launched with npx -y mcp-interactive-terminal. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mcp-interactive-terminal
claude mcp add amol21p-interactive-terminal -- npx -y mcp-interactive-terminal
{
"mcpServers": {
"amol21p-interactive-terminal": {
"command": "npx",
"args": [
"-y",
"mcp-interactive-terminal"
]
}
}
} {
"servers": {
"amol21p-interactive-terminal": {
"command": "npx",
"args": [
"-y",
"mcp-interactive-terminal"
]
}
}
} codex mcp add amol21p-interactive-terminal -- npx -y mcp-interactive-terminal
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"amol21p-interactive-terminal": {
"type": "local",
"command": [
"npx",
"-y",
"mcp-interactive-terminal"
],
"enabled": true
}
}
} openclaw mcp add amol21p-interactive-terminal --command npx --arg -y --arg mcp-interactive-terminal
mcp_servers:
amol21p-interactive-terminal:
command: "npx"
args: ["-y", "mcp-interactive-terminal"] {
"McpServers": {
"amol21p-interactive-terminal": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mcp-interactive-terminal"
]
}
}
} assistant mcp add amol21p-interactive-terminal -t stdio -c npx -a -y mcp-interactive-terminal
{
"mcpServers": {
"amol21p-interactive-terminal": {
"command": "npx",
"args": [
"-y",
"mcp-interactive-terminal"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 17 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 16 Sept 26 −2
- Stability: pass → 0.83 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 14 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −2
- Stability: pass → 0.80 functional
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 20 Sept 2026 · Analysed npm/mcp-interactive-terminal@1.0.7
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 →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| postinstall | dangerous | node -e "try{require('fs').chmodSync(require('path').join(require.resolve('node-pty'),'..','..','prebuilds',process.platform+'-'+process.arch,'spawn-helper'),0o755)}catch{}" |
Background: Why install scripts are a supply-chain risk →
Dependencies 106 packages
| Packages resolved | 106 |
|---|---|
| Stale | 33 |
| 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 →
close_session ~49
Close/kill an interactive terminal session.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | The session ID to close |
| signal | string | – | Signal to send (e.g., SIGTERM, SIGKILL) |
No output schema declared.
No examples provided.
confirm_dangerous_command ~88
Execute a command that was flagged as dangerous by send_command. Requires a justification explaining WHY the command is necessary. This is a separate confirmation step for safety.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | The exact dangerous command to confirm and execute |
| justification | string | yes | Explanation of WHY this dangerous command is necessary (min 10 chars) |
| session_id | string | yes | The session ID |
No output schema declared.
No examples provided.
create_session ~127
Spawn an interactive terminal session (REPL, shell, database client, SSH, etc.). Returns a session_id for subsequent commands.
| Name | Type | Req | Description |
|---|---|---|---|
| args | array | – | Arguments to pass to the command |
| cols | number | – | Terminal width in columns |
| command | string | yes | The command to spawn (e.g., 'python3', 'bash', 'psql') |
| cwd | string | – | Working directory for the session |
| env | object | – | Additional environment variables |
| name | string | – | Human-readable session name |
| rows | number | – | Terminal height in rows |
No output schema declared.
No examples provided.
list_sessions ~20
List all active interactive terminal sessions. Safe read-only operation.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
read_output ~57
Read the current terminal screen without sending any input. Safe read-only operation.
| Name | Type | Req | Description |
|---|---|---|---|
| full_screen | boolean | – | Read full scrollback history instead of just the visible screen |
| session_id | string | yes | The session ID to read output from |
No output schema declared.
No examples provided.
send_command ~115
Send a command/input to an interactive session and wait for output. Appends newline automatically. Returns clean text output (no ANSI codes). If a dangerous command is detected, you must use confirm_dangerous_command first.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | The command/input to send (newline appended automatically) |
| max_output_chars | number | – | Override max output characters for this call |
| session_id | string | yes | The session ID to send input to |
| timeout_ms | number | – | Max time to wait for output (ms) |
No output schema declared.
No examples provided.
send_control ~139
Send a control character or special key to a session (e.g., ctrl+c to interrupt, ctrl+d to send EOF, arrow keys, tab for completion).
| Name | Type | Req | Description |
|---|---|---|---|
| control | string | yes | Control sequence to send. Supported: ctrl+a, ctrl+b, ctrl+c, ctrl+d, ctrl+e, ctrl+f, ctrl+k, ctrl+l, ctrl+n, ctrl+p, ctrl+r, ctrl+u, ctrl+w, ctrl+z, ctrl+\, ctrl+], enter, tab, escape, up, down, righ… |
| session_id | string | yes | The session ID |
No output schema declared.
No examples provided.
What is the io.github.amol21p/interactive-terminal MCP server?
io.github.amol21p/interactive-terminal is an MCP server listed in the public MCP registry as io.github.amol21p/interactive-terminal. MCP server for real interactive terminal sessions, REPLs, SSH, databases, Docker. This page covers its npm package (mcp-interactive-terminal).
Is the io.github.amol21p/interactive-terminal MCP server safe to use?
io.github.amol21p/interactive-terminal scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares an install script we flagged as high risk. 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.amol21p/interactive-terminal MCP server expose?
io.github.amol21p/interactive-terminal exposes 7 tools: create_session, send_command, read_output, list_sessions, close_session, and 2 more. Their descriptions and schemas cost roughly 595 tokens of context every time the server is loaded.
Is the io.github.amol21p/interactive-terminal MCP server still maintained?
io.github.amol21p/interactive-terminal is still listed as active in the MCP registry. We last reached this channel on 20 September 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.amol21p/interactive-terminal MCP server under?
io.github.amol21p/interactive-terminal declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.