io.github.iTophua/iterminal
NPM · ITERMINAL-MCP-SERVER · SCANNED SEP 24
MCP Server for iTerminal SSH Connection Manager - Control SSH servers through Claude.
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 39 of 122 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 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- 80% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1717 tokens (~63/item across 27 items; 27 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "iter_exec" implies "exec" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 27 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.iTophua/iterminal MCP server?
io.github.iTophua/iterminal runs locally as an npm package, launched with npx -y iterminal-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · iterminal-mcp-server
claude mcp add itophua-iterminal -- npx -y iterminal-mcp-server
{
"mcpServers": {
"itophua-iterminal": {
"command": "npx",
"args": [
"-y",
"iterminal-mcp-server"
]
}
}
} {
"servers": {
"itophua-iterminal": {
"command": "npx",
"args": [
"-y",
"iterminal-mcp-server"
]
}
}
} codex mcp add itophua-iterminal -- npx -y iterminal-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"itophua-iterminal": {
"type": "local",
"command": [
"npx",
"-y",
"iterminal-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add itophua-iterminal --command npx --arg -y --arg iterminal-mcp-server
mcp_servers:
itophua-iterminal:
command: "npx"
args: ["-y", "iterminal-mcp-server"] {
"McpServers": {
"itophua-iterminal": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"iterminal-mcp-server"
]
}
}
} assistant mcp add itophua-iterminal -t stdio -c npx -a -y iterminal-mcp-server
{
"mcpServers": {
"itophua-iterminal": {
"command": "npx",
"args": [
"-y",
"iterminal-mcp-server"
]
}
}
} 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.
- 24 Sept 26 −3
- Stability: pass → 0.83 functional
- 23 Sept 26 +1
- Stability: 0.97 → pass security
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 19 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +2
- CVE-2026-82562 no longer affects this package ▲ security
- CVE-2026-82417 no longer affects this package ▲ security
- Known CVEs: fail → pass ▲ security
- 15 Sept 26 0
- Stability: 0.97 → pass security
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 24 Sept 2026 · Analysed npm/iterminal-mcp-server@2.1.0
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 →
Dependencies 122 packages
| Packages resolved | 122 |
|---|---|
| Stale | 39 |
| 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 →
iter_compress ~89
压缩远程服务器上的文件或目录。参数: id(连接标识), source_path(源路径), target_path(目标压缩文件路径)
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 连接标识符 |
| source_path | string | yes | 要压缩的文件或目录路径 |
| target_path | string | yes | 压缩后的目标文件路径(.tar.gz) |
No output schema declared.
No examples provided.
iter_connect ~97
创建 SSH 连接。参数: id(唯一标识), host(主机地址), port(端口,默认22), username(用户名), password(密码)
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | 服务器地址 |
| id | string | yes | 连接唯一标识符 |
| password | string | yes | 密码 |
| port | number | – | SSH端口,默认22 |
| username | string | yes | 用户名 |
No output schema declared.
No examples provided.
iter_create_file ~54
在远程服务器创建空文件。参数: id(连接标识), path(文件路径)
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 连接标识符 |
| path | string | yes | 要创建的文件路径 |
No output schema declared.
No examples provided.
iter_delete_directory ~53
删除远程服务器上的目录。参数: id(连接标识), path(目录路径)
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 连接标识符 |
| path | string | yes | 要删除的目录路径 |
No output schema declared.
No examples provided.
iter_disconnect ~35
断开 SSH 连接。参数: id(连接标识)
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 连接标识符 |
No output schema declared.
No examples provided.
iter_download_file ~80
从远程服务器下载文件到本地。参数: id(连接标识), remote_path(远程文件路径), local_path(本地保存路径)
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 连接标识符 |
| local_path | string | yes | 本地保存路径 |
| remote_path | string | yes | 远程文件路径 |
No output schema declared.
No examples provided.
iter_exec ~56
在远程服务器执行命令。参数: id(连接标识), command(要执行的命令)
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | 要执行的命令 |
| id | string | yes | 连接标识符 |
No output schema declared.
No examples provided.
iter_extract ~77
解压远程服务器上的压缩文件。参数: id(连接标识), file_path(压缩文件路径), target_dir(目标目录)
| Name | Type | Req | Description |
|---|---|---|---|
| file_path | string | yes | 压缩文件路径 |
| id | string | yes | 连接标识符 |
| target_dir | string | yes | 解压目标目录 |
No output schema declared.
No examples provided.
iter_kill_process ~60
终止远程服务器上的进程。参数: id(连接标识), pid(进程ID)
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 连接标识符 |
| pid | number | yes | 要终止的进程ID |
No output schema declared.
No examples provided.
iter_list_connections ~21
列出当前所有活跃的 SSH 连接
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
iter_list_dir ~54
列出远程目录内容。参数: id(连接标识), path(目录路径,默认/)
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 连接标识符 |
| path | string | – | 目录路径 |
No output schema declared.
No examples provided.
iter_list_processes ~43
获取远程服务器进程列表（按内存排序）。参数: id(连接标识)
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 连接标识符 |
No output schema declared.
No examples provided.
iter_list_saved_connections ~27
列出数据库中保存的所有 SSH 连接配置（不包含密码）
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
iter_mkdir ~53
在远程服务器创建目录。参数: id(连接标识), path(目录路径)
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 连接标识符 |
| path | string | yes | 要创建的目录路径 |
No output schema declared.
No examples provided.
iter_monitor ~45
获取远程服务器系统监控数据(CPU/内存/磁盘)。参数: id(连接标识)
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 连接标识符 |
No output schema declared.
No examples provided.
iter_network_stats ~38
获取远程服务器网络接口统计信息。参数: id(连接标识)
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 连接标识符 |
No output schema declared.
No examples provided.
iter_quick_connect ~41
使用保存的连接配置快速建立 SSH 连接。参数: id(保存的连接ID)
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 保存的连接ID |
No output schema declared.
No examples provided.
iter_read_file ~83
读取远程文件内容。参数: id(连接标识), path(文件路径), max_size(最大字节数,默认1MB)
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 连接标识符 |
| max_size | number | – | 最大读取字节数,默认1048576(1MB) |
| path | string | yes | 文件路径 |
No output schema declared.
No examples provided.
iter_rename ~70
重命名远程文件或目录。参数: id(连接标识), old_path(原路径), new_path(新路径)
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 连接标识符 |
| new_path | string | yes | 新路径 |
| old_path | string | yes | 原路径 |
No output schema declared.
No examples provided.
iter_rm ~50
删除远程文件。参数: id(连接标识), path(文件路径)
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 连接标识符 |
| path | string | yes | 要删除的文件路径 |
No output schema declared.
No examples provided.
iter_save_connection ~174
新建并保存一个 SSH 连接，可选自动连接。保存后可通过 iter_list_saved_connections 查看。参数: name(名称), host(主机), port(端口,默认22), username(用户名), password(密码), keyFile(私钥路径), autoConnect(是否立即连接,默认false)
| Name | Type | Req | Description |
|---|---|---|---|
| autoConnect | boolean | – | 是否保存后自动连接，默认 false |
| host | string | yes | 主机地址 |
| keyFile | string | – | 私钥文件路径（与 password 二选一） |
| name | string | yes | 连接名称（如 web-server） |
| password | string | – | 密码（与 keyFile 二选一） |
| port | number | – | SSH 端口，默认 22 |
| username | string | yes | 登录用户名 |
No output schema declared.
No examples provided.
iter_search_files ~101
在远程服务器上搜索文件。参数: id(连接标识), path(搜索起始路径), pattern(搜索模式), max_results(最大结果数,默认100)
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 连接标识符 |
| max_results | number | – | 最大返回结果数,默认100 |
| path | string | yes | 搜索起始路径 |
| pattern | string | yes | 搜索模式(支持通配符) |
No output schema declared.
No examples provided.
iter_status ~17
检查 iTerminal API 服务状态
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
iter_test_connection ~74
测试 SSH 连接是否可用(不保持连接)。参数: host, port, username, password
| Name | Type | Req | Description |
|---|---|---|---|
| host | string | yes | 服务器地址 |
| password | string | yes | 密码 |
| port | number | – | SSH端口,默认22 |
| username | string | yes | 用户名 |
No output schema declared.
No examples provided.
iter_upload_file ~79
上传本地文件到远程服务器。参数: id(连接标识), local_path(本地文件路径), remote_path(远程目标路径)
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 连接标识符 |
| local_path | string | yes | 本地文件路径 |
| remote_path | string | yes | 远程目标路径 |
No output schema declared.
No examples provided.
iter_upload_folder ~82
上传本地文件夹到远程服务器。参数: id(连接标识), local_path(本地文件夹路径), remote_path(远程目标路径)
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 连接标识符 |
| local_path | string | yes | 本地文件夹路径 |
| remote_path | string | yes | 远程目标路径 |
No output schema declared.
No examples provided.
iter_write_file ~64
写入远程文件内容。参数: id(连接标识), path(文件路径), content(文件内容)
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | 文件内容 |
| id | string | yes | 连接标识符 |
| path | string | yes | 文件路径 |
No output schema declared.
No examples provided.
What is the io.github.iTophua/iterminal MCP server?
io.github.iTophua/iterminal is an MCP server listed in the public MCP registry as io.github.iTophua/iterminal. MCP Server for iTerminal SSH Connection Manager - Control SSH servers through Claude. This page covers its npm package (iterminal-mcp-server).
Is the io.github.iTophua/iterminal MCP server safe to use?
io.github.iTophua/iterminal scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. 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.iTophua/iterminal MCP server expose?
io.github.iTophua/iterminal exposes 27 tools: iter_status, iter_connect, iter_disconnect, iter_test_connection, iter_list_connections, and 22 more. Their descriptions and schemas cost roughly 1,717 tokens of context every time the server is loaded.
Is the io.github.iTophua/iterminal MCP server still maintained?
io.github.iTophua/iterminal is still listed as active in the MCP registry. We last reached this channel on 24 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.iTophua/iterminal MCP server under?
io.github.iTophua/iterminal declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.