# Termix (pypi · termix-mcp)

Manage hosts, snippets, dashboard, metrics and audit of a self-hosted Termix (SSH/RDP/VNC manager)

- Trust score: 33/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- oci · `ghcr.io/sujirodev/termix-mcp:0.1.0`: 10/100, [markdown](https://verifymcp.io/servers/sujirodev-termix-mcp/ghcr-io-sujirodev-termix-mcp-0-1-0.md), [page](https://verifymcp.io/servers/sujirodev-termix-mcp/ghcr-io-sujirodev-termix-mcp-0-1-0)
- pypi · `termix-mcp`: 33/100 (this document), [markdown](https://verifymcp.io/servers/sujirodev-termix-mcp/termix-mcp.md), [page](https://verifymcp.io/servers/sujirodev-termix-mcp/termix-mcp)

## Channel facts

- Registry: `pypi`
- Package: `termix-mcp`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 44/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Declares code that runs automatically (build-time code we could not rule out (a Hatch, PDM or setuptools build hook, a dynamic version we could not read statically, shipped VCS metadata or a stray root module)) and that we could not recognise. It may be perfectly ordinary, but we have not established what it does.
  - 1 of 23 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to sujirodev/termix-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 42 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.

**Unverified: 5 categories.** Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you.

## Install

### How do I install the Termix MCP server?

Termix runs locally as a PyPI package, launched with uvx termix-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add sujirodev-termix-mcp -- uvx termix-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "sujirodev-termix-mcp": {
      "command": "uvx",
      "args": [
        "termix-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "sujirodev-termix-mcp": {
      "command": "uvx",
      "args": [
        "termix-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add sujirodev-termix-mcp -- uvx termix-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sujirodev-termix-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "termix-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add sujirodev-termix-mcp --command uvx --arg termix-mcp
```

### Hermes

```yaml
mcp_servers:
  sujirodev-termix-mcp:
    command: "uvx"
    args: ["termix-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "sujirodev-termix-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "termix-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add sujirodev-termix-mcp -t stdio -c uvx -a termix-mcp
```

### Other

```json
{
  "mcpServers": {
    "sujirodev-termix-mcp": {
      "command": "uvx",
      "args": [
        "termix-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 33, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-03 (score 48, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-26 (score 33, −15)

- [security regression] Malware scan: pass → unverified

### 2026-09-28 (score 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-25 (score 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 0)

First indexed and scored.

## MCP tools (0)

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/sujirodev-termix-mcp/termix-mcp#diagnostics

## Score history

- 2026-11-05: 33
- 2026-11-04: 33
- 2026-11-03: 48
- 2026-11-02: 33
- 2026-11-01: 33
- 2026-10-31: 33
- 2026-10-30: 33
- 2026-10-29: 33
- 2026-10-28: 33
- 2026-10-27: 33
- 2026-10-26: 33
- 2026-10-25: 48
- 2026-10-24: 48
- 2026-10-23: 48
- 2026-10-22: 48
- 2026-10-21: 48
- 2026-10-20: 48
- 2026-10-19: 48
- 2026-10-18: 48
- 2026-10-17: 48
- 2026-10-16: 48
- 2026-10-15: 48
- 2026-10-14: 48
- 2026-10-13: 48
- 2026-10-12: 48
- 2026-10-05: 48
- 2026-10-04: 48
- 2026-10-03: 48
- 2026-10-02: 48
- 2026-10-01: 48

## Common questions

### What is the Termix MCP server?

Termix is an MCP server listed in the public MCP registry as io.github.sujirodev/termix-mcp. Manage hosts, snippets, dashboard, metrics and audit of a self-hosted Termix (SSH/RDP/VNC manager). This page covers its PyPI package (termix-mcp).

### Is the Termix MCP server safe to use?

Termix scores 33 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.

### Is the Termix MCP server still maintained?

Termix 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 Termix MCP server under?

Termix 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 Termix MCP server?

VerifyMCP ran 8 checks on Termix, covering Known CVEs, Install scripts, Dependency health, Source repository and 4 more. 6 items could not be completed, a gap on our side rather than a finding about Termix: Malware scan, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.

## Links

- PyPI project: https://pypi.org/project/termix-mcp/
- Socket report: https://socket.dev/pypi/package/termix-mcp
- Repository: https://github.com/sujirodev/termix-mcp
- Changelog RSS feed: https://verifymcp.io/servers/sujirodev-termix-mcp/termix-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/sujirodev-termix-mcp/termix-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/sujirodev-termix-mcp/termix-mcp.json
- HTML version of this page: https://verifymcp.io/servers/sujirodev-termix-mcp/termix-mcp