Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.amol21p/interactive-terminal

NPM · MCP-INTERACTIVE-TERMINAL

MCP server for real interactive terminal sessions — REPLs, SSH, databases, Docker

0 this week 76 Trust /100

Last scanned (1 hour ago)

Scores higher than 53% of npm servers

Category Developer Tools

Trust breakdown (7 categories)

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 Security68
  • 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
  • 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
  • 32 of 103 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency44
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 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
  • 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
Changelog

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.

  • 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
  • 26 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 24 Oct 26 −5
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 20 Oct 26 0
    • Stability: 0.97 → pass security
  • 19 Oct 26 0
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +2
    • Stability: 0.87 → pass security
Diagnostics

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/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 →

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 103 packages
Packages resolved 103
Stale 32
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~595 tokens

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 →

Tool Tokens
close_session ~49

Close/kill an interactive terminal session.

NameTypeReqDescription
session_idstringyesThe session ID to close
signalstring–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.

NameTypeReqDescription
inputstringyesThe exact dangerous command to confirm and execute
justificationstringyesExplanation of WHY this dangerous command is necessary (min 10 chars)
session_idstringyesThe 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.

NameTypeReqDescription
argsarray–Arguments to pass to the command
colsnumber–Terminal width in columns
commandstringyesThe command to spawn (e.g., 'python3', 'bash', 'psql')
cwdstring–Working directory for the session
envobject–Additional environment variables
namestring–Human-readable session name
rowsnumber–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.

NameTypeReqDescription
full_screenboolean–Read full scrollback history instead of just the visible screen
session_idstringyesThe 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.

NameTypeReqDescription
inputstringyesThe command/input to send (newline appended automatically)
max_output_charsnumber–Override max output characters for this call
session_idstringyesThe session ID to send input to
timeout_msnumber–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).

NameTypeReqDescription
controlstringyesControl 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_idstringyesThe session ID

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add amol21p-interactive-terminal -- npx -y mcp-interactive-terminal
Common questions

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 76 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 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 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.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.