io.github.kitepon-rgb/aiterm-mcp

No dedicated API keys or environment variables are declared, so the direct secret surface is small; however, as a terminal tool, executed commands may interact with existing shell credentials, SSH config, or agent forwarding, creating indirect exposure or misuse risk.

No fixed remote host is declared, and the materials do not show automatic exfiltration to a specific service; however, the description explicitly supports nesting SSH and containers inside the persistent terminal, so commands can initiate network connections and transmit data.

Its core function is to drive a persistent tmux-backed terminal over MCP, which is explicit local command-execution capability; this typically allows spawning processes, running shell commands, and extending operations through SSH/containers, but no evidence is provided of privilege requests beyond its stated function.

As a terminal session, its data-access scope is largely determined by the local account running the MCP process, typically including files, directories, and session state reachable by that user; the materials do not indicate extra system-level over-privileging, but the default data surface is still broad.

Positive factors include its presence in the official registry, open-source availability, and updates within the last year, making the code auditable in principle; caution remains because the README is absent, the license is undeclared, and community adoption is very low (0 stars), leaving limited public trust signals.