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.

SmartCLI — drive terminal TUIs

PYPI · SMARTCLI-TOOLKIT

Let agents drive vim, htop, lazygit: send keys, wait on screen state, read the rendered cell grid.

Available components

−3 this week 87 Trust /100

Last scanned (14 hours ago)

Scores higher than 90% of PyPI 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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 1 of 31 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to dwgx/SmartCLI). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 24 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1904 tokens (~136/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
  • Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 14 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 5 Nov 26 −4
    • Stability: pass → 0.73 functional
  • 4 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 2 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 1 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 31 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 30 Oct 26 +1
    • Stability: 0.97 → pass security
  • 29 Oct 26 +14
    • Malware scan: unverified → pass ▲ security
    • Stability: pass → 0.97 functional
  • 28 Oct 26 −15
    • Malware scan: pass → unverified ▼ 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 pypi/smartcli-toolkit@0.3.5

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo dwgx/SmartCLI
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/dwgx/SmartCLI/.github/workflows/publish.yml@refs/tags/v0.3.5
Rekor log index 3209284123
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:46573077c0390415edd2ef533975705b643dd237b15d256c3bfad3367623f534

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 31 packages
Packages resolved 31
Stale 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 14 exposed · ~1,904 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
alive ~25

Check whether the session's child process is still running.

NameTypeReqDescription
sidstringyes–

No output schema declared.

No examples provided.

close ~28

Terminate a session and its daemon. Always close sessions when done.

NameTypeReqDescription
sidstringyes–

No output schema declared.

No examples provided.

list_sessions ~51

List active drive-tui sessions. Returns {"ok", "sessions"}: each entry carries "sid", "port", "pid", "cmd", "cols", "rows", "cwd" and "started".

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

resize ~38

Resize the session's terminal to cols x rows.

NameTypeReqDescription
colsintegeryes–
rowsintegeryes–
sidstringyes–

No output schema declared.

No examples provided.

send_keys ~182

Send key tokens, e.g. ["Down", "Down", "Enter"], ["C-c"], ["M-x"]. Named tokens: Enter, Return, Tab, BackTab, Space, Backspace, Delete, Escape, Esc, Up, Down, Right, Left, Home, End, PageUp, PageDown, Insert, F1-F12. Combos: "C-<char>" or "^<char>" (Ctrl — letters plus @, Space, [, \, ]) and "M-<char>" (Meta/Alt, ESC prefix). Any other token is not an error — it is typed as literal text. Arrow keys adapt to the app's cursor-key mode (SS3 under DECCKM, CSI else), so menu navigation works in curses apps.

NameTypeReqDescription
keysarrayyes–
sidstringyes–

No output schema declared.

No examples provided.

send_line ~37

Type text followed by Enter — the common 'run this command' action.

NameTypeReqDescription
sidstringyes–
textstringyes–

No output schema declared.

No examples provided.

send_text ~37

Type literal text into the session (no Enter). Use for filling fields.

NameTypeReqDescription
sidstringyes–
textstringyes–

No output schema declared.

No examples provided.

snapshot ~203

Read a semantic snapshot of the session's current screen. Returns {"ok", "alive", "alt_screen", "text", "hash", "visual_hash"}: `alt_screen` is true while a full-screen program (vim, less, htop, ...) owns the screen — keys are commands to that program, not input to a shell, and `text` is its frame rather than scrollback. `text` is the rendered screen; `json` (the structured cell/cursor model) is included only when as_json=true. `hash` covers text content only — use it as the wait_change baseline; `visual_hash` also covers styling, selection and cursor state — use it as the wait_visual_change baseline. Don't mix the two. This is the 'perceive' step — always snapshot after acting rather than assuming an action landed.

NameTypeReqDescription
as_jsonboolean––
sidstringyes–

No output schema declared.

No examples provided.

start ~383

Spawn a program in a new detached, persistent session and return its id. The session survives across tool calls (a localhost-only daemon owns the live PtySession). `cmd` is the command line to spawn, e.g. "python3" or "lazygit". `cwd` and `env` configure only the controlled child process. Returns {"ok", "sid"} on success. Use the returned sid for every other tool. Server-side limits (violations return an error): at most 8 concurrent sessions by default (tunable via SMARTCLI_MAX_SESSIONS); `sid` must be 1-64 chars matching [A-Za-z0-9][A-Za-z0-9_.-]*; `env` keys must be valid identifiers and may not start with SMARTCLI_TUI_; `cwd` must be an existing directory; terminal size is capped at 1000 cols x 500 rows (100000 cells). Note: `env` values pass through the process command line briefly (visible in `ps`) — avoid secrets. `detect_child_exit` (default false) makes this session's waits END when the child dies instead of sitting out the remaining timeout: a program that crashes on your first input costs one poll cycle instead of the whole ceiling. Off is exactly the previous behaviour. On, every wait tool also reports `exited` (true only when the wait ended that way), and `wait_ready` reports `reason: "EXITED"` alongside the usual MARKER/STABLE/TIMEOUT.

NameTypeReqDescription
cmdstringyes–
colsinteger––
cwdstring––
detect_child_exitboolean––
env–––
rowsinteger––
sidstring––

No output schema declared.

No examples provided.

wait_any ~242

Wait for ANY of `patterns` to appear on screen (pexpect expect([...]) style). Race several possible outcomes at once — e.g. patterns=[">>> ", "Error", "Password:"] — and learn WHICH happened. Patterns are scanned in list order each poll, so the earliest in the list wins a same-poll tie (put the most specific first). Screen lines are right-padded with spaces — end-anchored patterns never match; use unanchored markers. Returns {"ok", "index", "matched", "alive", "exited", "text", "json"} where `index` is the 0-based position of the matched pattern. Timeout is not an error: the call returns ok=true with index=-1 and matched=false plus the final screen snapshot. On a `detect_child_exit` session whose child died first, `index` is -1, `matched` is false and `exited` is true — the wait returned at once rather than running to `timeout_ms`.

NameTypeReqDescription
patternsarrayyes–
sidstringyes–
timeout_msinteger––

No output schema declared.

No examples provided.

wait_change ~186

Block until the screen content changes, then snapshot. The precise "did my action land?" primitive: call it right after send_line/ send_keys to wait for ANY change from the baseline (default: the screen at call time; or pass a prior `hash` to change away from). Returns {"ok", "changed", "hash", "alive", "exited", "text", "json"} — `hash` is the new screen hash, reusable as the next baseline. Timeout is not an error: the call returns ok=true with changed=false plus the final screen snapshot. `exited` is true only on a `detect_child_exit` session whose child died first. Can't false-positive on text that was already on screen, unlike wait_regex.

NameTypeReqDescription
baseline_hash–––
sidstringyes–
timeout_msinteger––

No output schema declared.

No examples provided.

wait_ready ~197

Wait for a regex `marker` OR for the screen to go quiet (stable), then snapshot. Use marker="" to wait purely for stability. Returns a snapshot plus `reason`: "MARKER" (the regex appeared), "STABLE" (the screen went quiet), "TIMEOUT", or — only on a session started with `detect_child_exit` — "EXITED" (the child died; the wait returned at once rather than running to `max_wait_ms`). `exited` reports the same fact as a boolean on every wait tool. Timeout is not an error: the call still returns ok=true with the final screen snapshot. Screen lines are right-padded with spaces — end-anchored markers never match; use unanchored markers.

NameTypeReqDescription
markerstring––
max_wait_msinteger––
quiet_msinteger––
sidstringyes–

No output schema declared.

No examples provided.

wait_regex ~177

Block until `pattern` (a regex) appears on screen, then snapshot. Returns {"ok", "matched", "alive", "exited", "text", "json"}. Timeout is not an error: the call returns ok=true with matched=false plus the final screen snapshot. `exited` is true only when the session was started with `detect_child_exit` AND the child died before the pattern appeared, in which case the wait returned at once instead of running to `timeout_ms`. Screen lines are right-padded with spaces — end-anchored patterns never match; use unanchored markers. This is the readiness sync — prefer it over a blind delay after send_line/send_keys.

NameTypeReqDescription
patternstringyes–
sidstringyes–
timeout_msinteger––

No output schema declared.

No examples provided.

wait_visual_change ~118

Wait for text, selection styling, or cursor position to change. Prefer this after arrow/navigation keys in full-screen TUIs. Pass a prior `visual_hash`, or omit it to use the current rendered state as the baseline. Timeout is not an error: the call returns ok=true with changed=false plus the final screen snapshot, with `exited` true only on a `detect_child_exit` session whose child died first.

NameTypeReqDescription
baseline_hash–––
sidstringyes–
timeout_msinteger––

No output schema declared.

No examples provided.

Install

How do I install the SmartCLI — drive terminal TUIs MCP server?

SmartCLI — drive terminal TUIs runs locally as a PyPI package, launched with uvx smartcli-toolkit. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · smartcli-toolkit

# add to Claude Code
claude mcp add dwgx-smartcli -- uvx smartcli-toolkit
Common questions

What is the SmartCLI — drive terminal TUIs MCP server?

SmartCLI — drive terminal TUIs is an MCP server listed in the public MCP registry as io.github.dwgx/smartcli. Let agents drive vim, htop, lazygit: send keys, wait on screen state, read the rendered cell grid. This page covers its PyPI package (smartcli-toolkit).

Is the SmartCLI — drive terminal TUIs MCP server safe to use?

SmartCLI — drive terminal TUIs scores 87 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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 SmartCLI — drive terminal TUIs MCP server expose?

SmartCLI — drive terminal TUIs exposes 14 tools: start, list_sessions, snapshot, close, send_text, and 9 more. Their descriptions and schemas cost roughly 1,904 tokens of context every time the server is loaded.

Is the SmartCLI — drive terminal TUIs MCP server still maintained?

SmartCLI — drive terminal TUIs 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 SmartCLI — drive terminal TUIs MCP server under?

SmartCLI — drive terminal TUIs declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the SmartCLI — drive terminal TUIs MCP server?

VerifyMCP ran 16 checks on SmartCLI — drive terminal TUIs, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.