# io.github.Lmeng486/nano-mcp-termux (pypi · nano-mcp-termux)

Zero-dependency single-file MCP server for Termux/Android, Raspberry Pi and Linux

- Trust score: 67/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- pypi · `nano-mcp-termux`: 67/100 (this document), [markdown](https://verifymcp.io/servers/lmeng486-nano-mcp-termux/nano-mcp-termux.md), [page](https://verifymcp.io/servers/lmeng486-nano-mcp-termux/nano-mcp-termux)

## Channel facts

- Registry: `pypi`
- Package: `nano-mcp-termux`
- Version: `1.1.1`
- 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**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 20 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 580 tokens (~145/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.Lmeng486/nano-mcp-termux server?

io.github.Lmeng486/nano-mcp-termux runs locally as a PyPI package, launched with uvx nano-mcp-termux. 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 lmeng486-nano-mcp-termux -- uvx nano-mcp-termux
```

### Cursor

```json
{
  "mcpServers": {
    "lmeng486-nano-mcp-termux": {
      "command": "uvx",
      "args": [
        "nano-mcp-termux"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "lmeng486-nano-mcp-termux": {
      "command": "uvx",
      "args": [
        "nano-mcp-termux"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add lmeng486-nano-mcp-termux -- uvx nano-mcp-termux
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add lmeng486-nano-mcp-termux --command uvx --arg nano-mcp-termux
```

### Hermes

```yaml
mcp_servers:
  lmeng486-nano-mcp-termux:
    command: "uvx"
    args: ["nano-mcp-termux"]
```

### Netclaw

```json
{
  "McpServers": {
    "lmeng486-nano-mcp-termux": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "nano-mcp-termux"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add lmeng486-nano-mcp-termux -t stdio -c uvx -a nano-mcp-termux
```

### Other

```json
{
  "mcpServers": {
    "lmeng486-nano-mcp-termux": {
      "command": "uvx",
      "args": [
        "nano-mcp-termux"
      ]
    }
  }
}
```

## 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-05 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 66, −14)

- [security regression] Malware scan: pass → unverified

### 2026-11-01 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 79, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-30 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 63, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-28 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (4)

### `device_status` (~119 tokens)

Device status (read-only)

Read-only snapshot of the host device: battery level, storage usage, CPU architecture and memory. Call it first when you need to know what hardware or runtime you are on, or to check whether battery/storage is low before starting a long task. Safe to call repeatedly and in parallel. Side effects: none — it only reads local system interfaces, never writes and never touches the network. It never raises: any field that cannot be read comes back with source "unavailable" instead of failing the call. Returns {battery, storage, arch, memory}.

### `server_health` (~107 tokens)

Server health (read-only)

Read-only self-diagnostics for this MCP server process: pid/ppid, runtime class, uptime, request and tool-call counters, tracked live child processes, RSS, and the Android Phantom Process Killer risk assessment. Use it to verify the server is alive, to debug client-side disconnects, or to check whether orphaned children are accumulating on Android. Side effects: none — it never spawns long-lived work and never modifies state. Returns {server, children, memory, phantom_process}.

### `resolve_path` (~228 tokens)

Resolve filesystem path (read-only)

Resolve and validate one filesystem path in the runtime this server runs in: expands ~/$HOME/$PREFIX/$TMPDIR, follows symlinks, reports the mount actually backing the path, and lists every Android-equivalent spelling (/sdcard <-> /storage/emulated/0 <-> $HOME/storage/shared). Call it before handing a path to a shell command or to another tool, especially on Termux/PRoot where one file has several spellings. Skip it for paths already known-good inside a plain Linux runtime. Read-only: it stats the path but never reads or writes file contents. Requires a non-empty `path`; an empty or missing value returns {error} rather than raising. Returns {input, expanded, resolved, env, exists, is_dir, is_file, is_symlink, readable, writable, executable, mount, alternatives, warnings}.

Input parameters:

- `path` (string, required): Path to resolve. May be absolute or relative and may contain ~, $HOME, $PREFIX or $TMPDIR. Required and non-empty; an empty string returns an error object instead of raising.

### `path_adapter` (~126 tokens)

Path environment adapter (read-only)

Report the runtime's path environment so you can translate host paths correctly: detected env class (termux/proot/android/linux), HOME/PREFIX/TMPDIR, each Android shared-storage root with its real mount, all noexec mounts that block in-place script execution, and runtime-specific notes. Call it once when starting work on an unfamiliar device, before constructing paths for other tools. Takes no arguments. Side effects: none; read-only and idempotent. Returns {env, home, prefix, tmpdir, python, platform, android_roots, noexec_mounts, notes}.

## Diagnostics

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

## Score history

- 2026-11-05: 67
- 2026-11-04: 66
- 2026-11-03: 66
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 79
- 2026-10-30: 64
- 2026-10-29: 63
- 2026-10-28: 78
- 2026-10-27: 77
- 2026-10-26: 77
- 2026-10-25: 76
- 2026-10-24: 76
- 2026-10-23: 75
- 2026-10-22: 72
- 2026-10-21: 72
- 2026-10-20: 72
- 2026-10-19: 72
- 2026-10-18: 72
- 2026-10-17: 72
- 2026-10-16: 72

## Common questions

### What is the io.github.Lmeng486/nano-mcp-termux server?

io.github.Lmeng486/nano-mcp-termux is listed in the public MCP registry as io.github.Lmeng486/nano-mcp-termux. Zero-dependency single-file MCP server for Termux/Android, Raspberry Pi and Linux. This page covers its PyPI package (nano-mcp-termux).

### Is the io.github.Lmeng486/nano-mcp-termux server safe to use?

io.github.Lmeng486/nano-mcp-termux scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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.Lmeng486/nano-mcp-termux server expose?

io.github.Lmeng486/nano-mcp-termux exposes 4 tools: device_status, server_health, resolve_path, path_adapter. Their descriptions and schemas cost roughly 580 tokens of context every time the server is loaded.

### Is the io.github.Lmeng486/nano-mcp-termux server still maintained?

io.github.Lmeng486/nano-mcp-termux 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 io.github.Lmeng486/nano-mcp-termux server under?

io.github.Lmeng486/nano-mcp-termux 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 io.github.Lmeng486/nano-mcp-termux server?

VerifyMCP ran 15 checks on io.github.Lmeng486/nano-mcp-termux, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.Lmeng486/nano-mcp-termux: Malware scan. 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/nano-mcp-termux/
- Socket report: https://socket.dev/pypi/package/nano-mcp-termux
- Repository: https://github.com/Lmeng486/nano-mcp-termux
- Changelog RSS feed: https://verifymcp.io/servers/lmeng486-nano-mcp-termux/nano-mcp-termux.xml
- Changelog JSON feed: https://verifymcp.io/servers/lmeng486-nano-mcp-termux/nano-mcp-termux/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/lmeng486-nano-mcp-termux/nano-mcp-termux.json
- HTML version of this page: https://verifymcp.io/servers/lmeng486-nano-mcp-termux/nano-mcp-termux