io.github.Lmeng486/nano-mcp-termux
PYPI · NANO-MCP-TERMUX
Zero-dependency single-file MCP server for Termux/Android, Raspberry Pi and Linux
Available components
Last scanned (46 minutes ago)
Scores higher than 63% of PyPI servers
Category IoT and Hardware
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 Security50
- Malware scan not yet available for this package.Unverified
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency48
- 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 20 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management67
- Stability observed for 20 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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 +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.
- 3 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- 1 Nov 26 +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.
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 +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.
- 29 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 28 Oct 26 +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.
- 26 Oct 26 +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.
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/nano-mcp-termux@1.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
device_status Device status (read-only) ~119
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}.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
path_adapter Path environment adapter (read-only) ~126
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}.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
resolve_path Resolve filesystem path (read-only) ~228
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | 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. |
No output schema declared.
No examples provided.
server_health Server health (read-only) ~107
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}.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
pypi · nano-mcp-termux
claude mcp add lmeng486-nano-mcp-termux -- uvx nano-mcp-termux
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.