Ai Mcp Terminal MCP Server

ai-mcp-terminal PyPI v1.0.54

Published by kanniganfan — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

AI终端管理器 - 支持MCP协议的多线程终端系统,提供并发执行、智能调度、交互检测、Web界面等功能

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 22

high Tool "execute_command" exposes command/code executionMTC-CAP-001

Tool "execute_command" appears to run shell commands or evaluate code (keyword "execute command" in tool name, parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool execute_command

high Tool "broadcast_command" exposes command/code executionMTC-CAP-001

Tool "broadcast_command" appears to run shell commands or evaluate code (parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool broadcast_command

high Tool "execute_batch" exposes command/code executionMTC-CAP-001

Tool "execute_batch" appears to run shell commands or evaluate code (parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool execute_batch

high Tool "get_output" exposes command/code executionMTC-CAP-001

Tool "get_output" appears to run shell commands or evaluate code (parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool get_output

high Tool "get_batch_output" exposes command/code executionMTC-CAP-001

Tool "get_batch_output" appears to run shell commands or evaluate code (parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool get_batch_output

high Tool "execute_sequence" exposes command/code executionMTC-CAP-001

Tool "execute_sequence" appears to run shell commands or evaluate code (parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool execute_sequence

high Tool "execute_with_retry" exposes command/code executionMTC-CAP-001

Tool "execute_with_retry" appears to run shell commands or evaluate code (parameter "command"). Arbitrary execution driven by model input is one of the most dangerous MCP capabilities; combined with any untrusted input it becomes RCE.

Fix: Sandbox execution, allowlist commands/arguments, and never pass model output to a shell unescaped.

Location: tool execute_with_retry

high Shell/command execution in server code (src/terminal_manager.py)MTC-SRC-002

In the server's implementation (`src/terminal_manager.py:417`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: ndows": subprocess.run(["where", command], capture_output=True, check=True) else:

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server src/terminal_manager.py

medium Unconstrained command parameter "command" on "execute_command"MTC-CAP-006

Tool "execute_command" takes a command-shaped parameter "command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool execute_command · inputSchema.properties.command

medium Unconstrained command parameter "command" on "broadcast_command"MTC-CAP-006

Tool "broadcast_command" takes a command-shaped parameter "command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool broadcast_command · inputSchema.properties.command

medium Unconstrained command parameter "command" on "execute_batch"MTC-CAP-006

Tool "execute_batch" takes a command-shaped parameter "command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool execute_batch · inputSchema.properties.command

medium Unconstrained command parameter "only_last_command" on "get_output"MTC-CAP-006

Tool "get_output" takes a command-shaped parameter "only_last_command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool get_output · inputSchema.properties.only_last_command

medium Unconstrained command parameter "only_last_command" on "get_batch_output"MTC-CAP-006

Tool "get_batch_output" takes a command-shaped parameter "only_last_command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool get_batch_output · inputSchema.properties.only_last_command

medium Unconstrained command parameter "timeout_per_command" on "execute_sequence"MTC-CAP-006

Tool "execute_sequence" takes a command-shaped parameter "timeout_per_command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool execute_sequence · inputSchema.properties.timeout_per_command

medium Unconstrained command parameter "command" on "execute_with_retry"MTC-CAP-006

Tool "execute_with_retry" takes a command-shaped parameter "command" with no enum/pattern constraint. Free-form, model- or attacker-controlled arguments reaching a shell is the command-injection precondition.

Fix: Constrain the parameter (enum/pattern), or build the command from a fixed template with escaped args.

Location: tool execute_with_retry · inputSchema.properties.command

low Mutating tool "execute_command" declares no destructiveHintMTC-CAP-005

Tool "execute_command" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool execute_command

low Mutating tool "broadcast_command" declares no destructiveHintMTC-CAP-005

Tool "broadcast_command" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool broadcast_command

low Mutating tool "execute_batch" declares no destructiveHintMTC-CAP-005

Tool "execute_batch" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool execute_batch

low Mutating tool "get_output" declares no destructiveHintMTC-CAP-005

Tool "get_output" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool get_output

low Mutating tool "get_batch_output" declares no destructiveHintMTC-CAP-005

Tool "get_batch_output" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool get_batch_output

low Mutating tool "execute_sequence" declares no destructiveHintMTC-CAP-005

Tool "execute_sequence" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool execute_sequence

low Mutating tool "execute_with_retry" declares no destructiveHintMTC-CAP-005

Tool "execute_with_retry" can mutate/egress but declares no destructiveHint. Clients that don't default to spec-safe behavior may not prompt before running it.

Fix: Declare accurate annotations, and gate destructive tools on user confirmation regardless.

Location: tool execute_with_retry

Tools 26

Each tool and what it can reach — statically extracted from the published source.

  • broadcast_commandruns code / shell
  • execute_batchruns code / shell
  • execute_commandruns code / shell
  • execute_sequenceruns code / shell
  • execute_with_retryruns code / shell
  • get_batch_outputruns code / shell
  • get_outputruns code / shell
  • batch_send_keysno sensitive capability
  • check_completionno sensitive capability
  • create_batchno sensitive capability
Show 16 more tools ↓
  • create_sessionno sensitive capability
  • detect_interactionsno sensitive capability
  • execute_workflowno sensitive capability
  • get_all_sessionsno sensitive capability
  • get_live_outputno sensitive capability
  • get_session_statusno sensitive capability
  • get_statsno sensitive capability
  • get_terminal_statesno sensitive capability
  • interrupt_batchno sensitive capability
  • interrupt_commandno sensitive capability
  • kill_batchno sensitive capability
  • kill_sessionno sensitive capability
  • send_inputno sensitive capability
  • send_keysno sensitive capability
  • send_textno sensitive capability
  • wait_until_completeno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.0.54 latest A 93/100 22 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/ai-mcp-terminal/badge.svg)](https://mcptrustchecker.com/registry/ai-mcp-terminal)
HTML
<a href="https://mcptrustchecker.com/registry/ai-mcp-terminal"><img src="https://mcptrustchecker.com/registry/ai-mcp-terminal/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/ai-mcp-terminal/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan ai-mcp-terminal --online --registry pypi

Use the free API → How scoring works

More in Developer Tools